How far along is 5.3? A release is needed for geronimo 2.2

[David Jencks <da...@yahoo.com>]

Over at Geronimo we've finally upgraded to activemq 5, only 2 or so  
years late.... however we've found some tck problems in 5.2 that I've  
been fixing in trunk.  I think I'm getting close to getting all the  
problems fixed.

Geronimo would like to  release 2.2 including amq 5 pretty soon,  
hopefully by the end of January.  Activemq is not the only boulder in  
the way of this plan but is definitely significant.  I can think of  
several ways forward here, listed in order of my decreasing preference:

1. Actually release AMQ 5.3 with the planned 5.3 features complete.   
I'm not sure what these features are or how complete they are but this  
definitely seems best to me.

2. Release something like the current trunk perhaps by merging all the  
changes into the 5.2 branch.  Having half implemented features would  
not be too good... I don't know if there are any such.  This seems  
also to violate the typical policy of "bug fixes only" in a branch.

3. Try to backport tck fixes back to the 5.2 branch.  This could be  
difficult because some of the fixes are to other fixes since 5.2 --  
fixing serious bugs.  Also this doesn't sound like fun to me :-D

4. Geronimo could publish a "private" snapshot of something like trunk  
for its 2.2.  This seems like (2) except much worse as it wouldn't get  
scrutiny from the amq community.

So I'm wondering if (1) is plausible or if anyone has any other  
suggestions.

many thanks
david jencks

Re: How far along is 5.3? A release is needed for geronimo 2.2

[Gary Tully <ga...@gmail.com>]

David, what did ye do for 2.2? Are there any known issues with the tck that
still need to be resolved for a 5.3?

2009/1/9 David Jencks <da...@yahoo.com>

> Over at Geronimo we've finally upgraded to activemq 5, only 2 or so years
> late.... however we've found some tck problems in 5.2 that I've been fixing
> in trunk.  I think I'm getting close to getting all the problems fixed.
>
> Geronimo would like to  release 2.2 including amq 5 pretty soon, hopefully
> by the end of January.  Activemq is not the only boulder in the way of this
> plan but is definitely significant.  I can think of several ways forward
> here, listed in order of my decreasing preference:
>
> 1. Actually release AMQ 5.3 with the planned 5.3 features complete.  I'm
> not sure what these features are or how complete they are but this
> definitely seems best to me.
>
> 2. Release something like the current trunk perhaps by merging all the
> changes into the 5.2 branch.  Having half implemented features would not be
> too good... I don't know if there are any such.  This seems also to violate
> the typical policy of "bug fixes only" in a branch.
>
> 3. Try to backport tck fixes back to the 5.2 branch.  This could be
> difficult because some of the fixes are to other fixes since 5.2 -- fixing
> serious bugs.  Also this doesn't sound like fun to me :-D
>
> 4. Geronimo could publish a "private" snapshot of something like trunk for
> its 2.2.  This seems like (2) except much worse as it wouldn't get scrutiny
> from the amq community.
>
> So I'm wondering if (1) is plausible or if anyone has any other
> suggestions.
>
> many thanks
> david jencks
>
>


-- 
http://blog.garytully.com

Open Source SOA
http://FUSESource.com