My preference would be to get people to move to the 3.3.x or 4.x versions and not to do many more on the 3.2.x branch as the components will be common for both the 3.3.x and smx4 versions otherwise we will end up having to maintain two sets of components.
my 2 cents, Edell. On Fri, Oct 24, 2008 at 2: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 > > >
