Re: [cross-project-issues-dev] Is there a reason to have org.apache.comm

[Thomas Hallgren <thomas@xxxxxxx>]

+1 for a freeze but why as early as M4? I would vote for M6. Before that 
milestone there's no API freeze so all projects must expect a certain 
amount of changes anyway.

- thomas

On 05/20/2010 08:18 PM, Scott Lewis wrote:
> Hi Ed,
>
> Ed Willink wrote:
> > Hi
> >
> > Perhaps we should introduce a third party dependencies freeze at M4, 
> > encouraging transition to the latest stable version up until then, 
> > and giving time to align or fall back as necessary.
>
> I would be +1 for such a freeze.
> I think simple cross-project communication/interaction over shared 
> dependencies would be helpful also.  For example, if we/ECF knew in 
> the summer/fall of 2009 that this 2nd-order dependency was causing a 
> problem for other projects we very well could/would have done 
> something about it (e.g. did testing with httpclient 3.1 over commons 
> logging version of choice).
> As well, if other projects knew that our reason for staying with 3.1 
> (and commons 1.0.4) was that we don't/didn't have enough resources to 
> complete work on the httpclient 4.0-based provider (i.e. the 
> bug/enhancement) in 3.6 cycle, then perhaps they would have been 
> willing to contribute resources to eliminate this problem once and for 
> all (by helping to move to httpclient 4.0 and/or some other).
>
> Scott
>
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev