On Wed, 2019-02-20 at 14:54 +0000, Marcel Reutegger wrote: > Hi, > > On 20.02.19, 13:21, "Robert Munteanu" <[email protected]> wrote: > > On Wed, 2019-02-20 at 10:45 +0000, Davide Giannella wrote: > > > - Any previous oak release will be automatically deprecated. What > > > has > > > been already branched and released still stays there. This > > > applies > > > only > > > to future releases. > > > > So say we release 1.12 from trunk and then 1.12.1 from trunk. Does > > that > > mean that 1.12 becomes instantly deprecated? > > I wouldn't call it deprecated, but 1.12.1 will be the new recommended > version. This specific situation is very similar to how we do > maintenance > releases. The most recent release from a maintenance branch is the > one > we recommend. > > > Do we even plan to make minor releases such as 1.12.1 or will 1.13 > > immediately follow after 1.12? > > That's a good question. In my view we could make micro releases based > on what has changed since the last minor release. If it's just bug > fixes, > release as 1.12.1 otherwise move to 1.14. > > Note the even minor version. To avoid confusion, we could still say > only > even minor versions are considered stable release. Even though we > wouldn't create releases anymore with uneven minor version numbers.
Ack, it all makes sense. There is an argument to be made for also making unstable releases now that we're changing things anyway, but it's not something that I view as terribly important. In Sling we always release even versions for technical reasons and I don't remember anyone complaining about it. Thanks, Robert
