I'd really like to get rid of the 3.2.x branch maintenance asap so that we only need to support the new components. And I don't really see a 3.4 (unless maybe if we add more components ?). Imho we would use trunk for 3.3.x for now, and let our users know that we don't plan on doing a 3.2.4 release.
On Fri, Oct 24, 2008 at 3:56 PM, 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? > > Gert > > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
