Blog post is live for it http://cordova.apache.org/blog/releases/2013/11/13/cordova-320rc1.html
On Tue, Nov 12, 2013 at 2:30 PM, Steven Gill <stevengil...@gmail.com> wrote: > Shaz, you are correct! > > semver wants you to do rc versions that way. > > I meant to say npm install -g cordova@3.2.0-rc.1 > > > On Tue, Nov 12, 2013 at 2:22 PM, Shazron <shaz...@gmail.com> wrote: > >> Steve, you published the version as: 3.2.0-rc.1 >> >> so the correct line is: >> npm install -g cordova@3.2.0-rc.1 >> >> >> On Tue, Nov 12, 2013 at 2:15 PM, Steven Gill <stevengil...@gmail.com> >> wrote: >> >> > Hey all, >> > >> > I am going to put up a blog post for review shortly for the RC. >> > >> > If you are interested in helping test the RC (DO IT), you can install >> it by >> > going npm install -g cordova@3.2.0-rc1. >> > >> > Let me know if their are any issues blocking the final release. I know >> that >> > the Firefox update script is not quite working, but this is a firefoxos >> > platform issue, not a cli one. I am working on it. :) >> > >> > Plugman 0.15.0 has also been published and set to latest. >> > >> > >> > On Wed, Nov 6, 2013 at 5:25 PM, Steven Gill <stevengil...@gmail.com> >> > wrote: >> > >> > > Update for everyone >> > > >> > > I chatted with the platform leads and we are hoping to tag 3.2.0rc1 >> > > tomorrow. >> > > >> > > >> > > >> > > On Wed, Nov 6, 2013 at 2:27 PM, Joe Bowser <bows...@gmail.com> wrote: >> > > >> > >> On Wed, Nov 6, 2013 at 2:14 PM, Joe Bowser <bows...@gmail.com> >> wrote: >> > >> > On Wed, Nov 6, 2013 at 2:04 PM, Marcel Kinard <cmarc...@gmail.com> >> > >> wrote: >> > >> >> BTW, I also found a couple failures in the Android native tests on >> > >> 4.2.2 on a Nexus 7 with 3.2.0-rc1: >> > >> >> >> > >> >> junit.framework.AssertionFailedError >> > >> >> at >> > >> >> > >> org.apache.cordova.test.BackButtonMultiPageTest.testViaHref(BackButtonMultiPageTest.java:63) >> > >> >> >> > >> > >> > >> > I actually think it's the test. It passes when I run it by itself >> > >> > sometimes. I'm thinking that this should probably be deleted >> because >> > >> > it's not the most reliable. >> > >> > >> > >> >> > >> Yup! The JS is broken on the tests, therefore this would break >> > >> window.location working! Please disregard this test until we've >> > >> upgraded the test project to be a proper 3.x set of tests. >> > >> >> > > >> > > >> > >> > >