Thank you for your quick answer.
Thank you for asking. I would say it's better if you don't have to maintain and release 2 versions in parallel like this month's SR1 3.0.2 and 3.1. It is a time consuming burden and from a personal point of view, I'd like better you spend it on new features, bug fixes, etc.. ;)
Some people may want a 3.0.3 because they are implementing your APIs and don't want to be broken in SR2. But then, they should listen to this ML and will raise their hand (especially by announcing it this early!). If nobody does, I suggest you go for Kepler SR2 = 3.2.
I would also suggest to stick to this policy for later releases and make Luna SR1 = 4.1
Regards, Mikael good question, according to [1] we can ship a minor release with a SR if the minor release was released 1 month before the RC1 of the SR, for Kepler SR2 this means we would have to release before Christmas (Dec 24), this means we could ship 3.2.0.
So we have the option to either ship 3.2.0 or 3.0.3 with Kepler SR2. Opinions ?
--
|
