This is really a hard question. My developer heart is telling me to stop development for 3.2 branch and go for the 3.3 and even better for version 4...but also knowing the other side of the force I can understand people to go with reliable and prooved to work software :)
I would say let the 3.2 branch open for one more version but announce it early (maybe right after releasing 3.2.3) that this version branch will end with the 3.2.4 version. This will set a clear and easy to understand time frame for people to get their projects updated to work with newer version. I personally don't see a 3.4 version. What should that be good for? We are developing version 4, so why startup another big release? Keeping 3.3 and 4 together sounds fine to me. Because of the sharing between both versions it is also much easier to maintain. Regards Lars ---- http://lhein.blogspot.com Gert Vanthienen 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 > > > > > ----- > --- > Gert Vanthienen > http://gertvanthienen.blogspot.com > -- View this message in context: http://www.nabble.com/-DISCUSS--Next-versions-in-3.x-line-tp20150681p20167737.html Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
