porting fixes to v 3.2.X
Can bug fixes from version 4.0 be ported to v 3.2.X ? and also, when is the next 3.2.X version coming out ? The fix I'm looking at in particular is : https://issues.apache.org/jira/browse/COLLECTIONS-294 Which is only fixed in 4.0 apparently.
Re: porting fixes to v 3.2.X
On 06/19/2015 05:41 PM, Marc-André Chartrand wrote: > Can bug fixes from version 4.0 be ported to v 3.2.X ? and also, when is > the next 3.2.X version coming out ? > > The fix I'm looking at in particular is : > > https://issues.apache.org/jira/browse/COLLECTIONS-294 > > Which is only fixed in 4.0 apparently. > Currently, there are no plans to release another 3.x version. Imho, a 3.2.2 release would only make sense if we really fix a considerable amount of known bugs present in the 3.2.1 release, but this would mean a lot of work. If a *big corp* would sponsor a few working days, I could imagine that a new release is feasible, otherwise try switching to collections 4 which has fixed all known bugs in the 3.x branch. btw. collections 3 and 4 can be used at the same time as they use different package names. Thomas - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: porting fixes to v 3.2.X
Thanks. I was wondering why the package names changed. I guess you just gave 1 reason. Marc > On Jun 21, 2015, at 4:55 AM, Thomas Neidhart > wrote: > >> On 06/19/2015 05:41 PM, Marc-André Chartrand wrote: >> Can bug fixes from version 4.0 be ported to v 3.2.X ? and also, when is >> the next 3.2.X version coming out ? >> >> The fix I'm looking at in particular is : >> >> https://issues.apache.org/jira/browse/COLLECTIONS-294 >> >> Which is only fixed in 4.0 apparently. > > Currently, there are no plans to release another 3.x version. > > Imho, a 3.2.2 release would only make sense if we really fix a > considerable amount of known bugs present in the 3.2.1 release, but this > would mean a lot of work. > > If a *big corp* would sponsor a few working days, I could imagine that a > new release is feasible, otherwise try switching to collections 4 which > has fixed all known bugs in the 3.x branch. > > btw. collections 3 and 4 can be used at the same time as they use > different package names. > > Thomas > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
