Yup, started the process thinking it will be 4.0.1, changing to 4.1.0 and restarting.
For the release process in general, it looks like it would be useful to decide on the intended version names very early in the process and send out the intended version names as part of the DISCUSS email, so that this can also be discussed. What do you think? On Fri, Nov 7, 2014 at 1:12 PM, Shazron <shaz...@gmail.com> wrote: > There were definitely changes to cordova-lib to support cordova-ios 3.7.0 > (new icons/splashscreen size support). If I'm reading the rule correctly, > the cli should be at 4.1.0 > > On Fri, Nov 7, 2014 at 10:06 AM, Marcel Kinard <cmarc...@gmail.com> wrote: > > > From > > > https://github.com/apache/cordova-coho/blob/master/docs/versioning-and-release-strategy.md > > : > > > > "...when a new platform is released, and the platform pin in the CLI is > > correspondingly updated, the CLI receives a bump to its third digit, no > > matter the size of the version bump to those platform(s). If the CLI > > requires a change (beyond updating the pin) to handle the new platform, > or > > if the CLI has other changes, then the second or even first digit of the > > CLI version may get bumped - the SemVer semantics still apply for the > CLI." > > > > On Nov 7, 2014, at 1:02 PM, Shazron <shaz...@gmail.com> wrote: > > > > > What's our rule for incrementing cordova-cli version when a platform > gets > > > updated? I can't find it in the docs. > > > > >
