I'm liking this idea w/ one exception: I think adding another # would be confusing. How about we adopt a practice were we ship:
cordova-1.8.x.zip ..wherein the individual platforms could be a particular PATCH release within that particular MINOR. Saves the other platforms from having to tag. On Mon, Jun 11, 2012 at 2:30 PM, Jesse <[email protected]> wrote: > Before I tip my hand on a vote ... > Is there any chance of a middle ground here? > Updating all platforms to 1.8.1 for the benefit of one platform seems like > a lot of overhead to address a change in one. > > Could we adopt packaging a 1.8.0.1.zip which would include the updated iOS > code, and iOS code tags, but no changes to the other platforms? or > something similar? > > Of course this would require adding a little documentation to the release, > to say what was addressed, and what platforms were changed, but still > considerably easier than the tag->domino effect we have now. IMO > > On Mon, Jun 11, 2012 at 2:18 PM, Filip Maj <[email protected]> wrote: > >> +1 release 1.8.1 >> >> On 6/11/12 2:15 PM, "Brian LeRoux" <[email protected]> wrote: >> >> >So we have a fairly big issue in iOS 1.8 wherein a PhoneGap app is >> >crashing if the user swipes down the notification centre while in-app. >> >The question is whether this is a bug big enough to cut an 1.8.1 >> >official release for all platforms or if pointing users to the minor >> >tag is enough. >> > >> >[+1] release 1.8.1 >> >[ -1] do not release 1.8.1 >> > >> >I think a tag should suffice but if implementors have no trouble >> >tagging a release then we might as well save Shaz/Becky the >> >email/twitter complaint! >> >> > > > -- > @purplecabbage > risingj.com
