Shoot! I just fixed this right now.
In regards to branching policy, I think the easiest way to fix this, which I should have done originally for the revert, is to checkout the 3.3.1-0.4.1 tag, make the modification, commit, tag 3.3.1-0.4.2 and npm publish. Master stays ready for 3.4 release and bb fix is back out there as it should have been in the first place (sorry about that). I just tried this out and it works. Let me know if you see anything wrong with it. npm install cordova should get 3.3.1-0.4.2 now. On Tue, Feb 11, 2014 at 12:26 PM, Bryan Higgins <[email protected]>wrote: > The 3.3.1 version of bb10 was inadvertently reverted to 3.3.0 [1][2] > > I'd like to clean this up before 3.4 hits as 3.3.1 fixed a critical bug on > Windows machines. > > I think this means I'll need to revert the 3.4.0 version changes, fix > platforms.js, tag, publish, then put the 3.4.0 version changes back in. I > will do so tomorrow unless there are objections... > > Perhaps this is a reason to revisit the branching policy? Even a small > branch just for publishing the RC would have avoided this. > > [1] > > https://git-wip-us.apache.org/repos/asf?p=cordova-cli.git;a=blobdiff;f=platforms.js;h=2e23480 > [2] > > https://git-wip-us.apache.org/repos/asf?p=cordova-cli.git;a=blobdiff;f=platforms.js;h=be7f2cb >
