I expect that if it is going out to users it should have a vote. Since we need to roll CLI to actually surface this to users, we can probably vote for both at that time.
-Michal On Fri, Mar 28, 2014 at 8:14 PM, Steven Gill <stevengil...@gmail.com> wrote: > I think we can vote on it when we vote on the tools. > On Mar 28, 2014 4:43 PM, "Shazron" <shaz...@gmail.com> wrote: > > > I assume this does not need a vote since it doesn't go in the dist > folder, > > and only downloaded by the CLI tool? > > > > > > On Fri, Mar 28, 2014 at 4:37 PM, Shazron <shaz...@gmail.com> wrote: > > > > > iOS: Changes are in the 3.4.x branch, and 3.4.1 is tagged. I'll do more > > > testing over the weekend. > > > > > > > > > > > > On Fri, Mar 28, 2014 at 12:09 PM, Shazron <shaz...@gmail.com> wrote: > > > > > >> Yeah lets do a 3.4.1 iOS, simpler for now until we figure out any new > > way > > >> regarding independent releases. > > >> > > >> Plan: > > >> - branch off 3.4.0 release > > >> - cherry-pick commits for template changes, script changes, callback > id > > >> change (to allow callback ids with periods in them) > > >> - version it 3.4.1 in VERSION in this branch only > > >> - version it 3.4.1 in CDVAvailability.h (copy back to master as well). > > >> > > >> > > >> > > >> On Fri, Mar 28, 2014 at 9:20 AM, Steven Gill <stevengil...@gmail.com > > >wrote: > > >> > > >>> I don't have any problem with going the 3.4.1 route. It would be > > simpler > > >>> in > > >>> terms of docs + js. > > >>> > > >>> Shazron, would that work for you? > > >>> On Mar 28, 2014 8:27 AM, "Andrew Grieve" <agri...@chromium.org> > wrote: > > >>> > > >>> > From what I understand of the changes, it should work fine to do a > > >>> 3.4.1 > > >>> > and just leave the JS as is. > > >>> > > > >>> > > > >>> > On Thu, Mar 27, 2014 at 8:00 PM, Marcel Kinard <cmarc...@gmail.com > > > > >>> wrote: > > >>> > > > >>> > > It feels like trying to tag only iOS as 3.5.0 before the other > > >>> platforms > > >>> > > is going to create a mess when it comes time to release the other > > >>> > > platforms, especially if there are subsequent changes to > cordova-js > > >>> > and/or > > >>> > > cordova-ios. I don't like moving tags. So +1 to Michal's > question. > > >>> > > > > >>> > > On Mar 27, 2014, at 9:56 PM, Michal Mocny <mmo...@google.com> > > wrote: > > >>> > > > > >>> > > > Before I even try to grok the other questions, why can't we > just > > >>> tag > > >>> > iOS > > >>> > > as > > >>> > > > 3.4.1? > > >>> > > > > >>> > > Perhaps the long-term answer for doing away with the cadence > > release > > >>> is > > >>> > to > > >>> > > version all the platforms separately, like how we do for the > > plugins > > >>> now. > > >>> > > > > >>> > > > On Thu, Mar 27, 2014 at 8:23 PM, Steven Gill < > > >>> stevengil...@gmail.com> > > >>> > > wrote: > > >>> > > > > > >>> > > >> The best course of action for the future is to set the build > > >>> label in > > >>> > > >> cordovajs to be just the sha. > > >>> > > > > >>> > > Maybe in the future, the build label in cordova-js also floats > > >>> separate > > >>> > > from the versions of all the platforms. Yeah, perhaps it's just > the > > >>> sha. > > >>> > > Every git repo has its own master and own independent versioning > > >>> > sequence. > > >>> > > > > >>> > > That does beg the question if there is some kind of overall > > snapshot > > >>> id > > >>> > to > > >>> > > replace the cadver, and when do we do Apache releases to dist. > > >>> > > > > >>> > > > > >>> > > > >>> > > >> > > >> > > > > > >
