One additional thought.
There are incompatibilities between the 3.2.x branch and 3.3 that should not
be overlooked. Both the Drools 3 to 4 upgrade and the CXF 2.0 to 2.1 upgrade
are prime examples. So, it may not be a seamless upgrade for users to move
from one to the other.
Since 3.3 has not even been officially released yet, it seems premature to
completely freeze the 3.2.x branch. You might consider preparing for one
more 3.2.4 release that would include only show-stopper fixes. This would
give users a month or two to migrate to 3.3 before the 3.2.x branch is
completely frozen. Once they have a chance to report their issues with 3.3
and if necessary upgrade to a 3.3.1 release, then 3.2.x might be officially
frozen. Just my two cents.
/Ron
bsnyder wrote:
>
> On Fri, Oct 24, 2008 at 7:56 AM, Gert Vanthienen
> <[EMAIL PROTECTED]> wrote:
>> L.S.,
>>
>>
>> With ServiceMix 3.2.3 and 3.3 almost out, it's time to start thinking
>> about
>> what we want to do with the ServiceMix 3.x line in the near future.
>> We should probably plan for a 3.3.1 bugfix release, but do we want to
>> consider doing a 3.4 release or will 4.0 be the next big release for
>> ServiceMix? Right now, in the Subversion repository, we have a
>> branches/servicemix-3.2, branches/servicemix-3.3 and trunk.
>>
>> If we don't plan for a 3.4 release, we can probably just keep trunk for
>> working on 3.3.x and maintain the current 3.2 branch to support our 3.2.x
>> user base a bit longer. But if we do want a 3.4 release, do we also want
>> to
>> keep maintaining the current 3.2.x branch -- backporting fixes two
>> versions
>> back seems a bit too much overhead?
>>
>>
>> Thoughts?
>
> We should retire the 3.2.x branch and make it clear that there will
> not be another release on that branch. Development should continue on
> the trunk which is currently 3.3. If, over time, there are enough new
> features to warrant a 3.4 release, only then should we consider it. I
> don't think that we can make a decision now about a 3.4 release. This
> can only be determined over time and, more importantly, based on what
> users want. There will be a lot of folks who don't want to/cannot move
> away from 3.x so I imagine that bug fixes and new features will
> continue to happen there.
>
> Bruce
> --
> perl -e 'print
> unpack("u30","D0G)[EMAIL PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
> );'
>
> Apache ActiveMQ - http://activemq.org/
> Apache Camel - http://activemq.org/camel/
> Apache ServiceMix - http://servicemix.org/
>
> Blog: http://bruceblog.org/
>
>
--
View this message in context:
http://www.nabble.com/-DISCUSS--Next-versions-in-3.x-line-tp20150681p20154524.html
Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
