cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Grieve <agri...@chromium.org>
Subject Re: Testing RCs in a 3.0 world
Date Sun, 22 Sep 2013 11:50:46 GMT
Yep! That's exactly what Braden did I think.

3.0.10 is rc1, and 3.0.9 is latest.


On Sun, Sep 22, 2013 at 4:14 AM, Brian LeRoux <b@brian.io> wrote:

> According to the twitternets we can publish cordova@3.1.0-rc1 but then
> `npm
> tag cordova@3.0.123 latest` to allow for this use case w/ npm.
>
>
>
> On Wed, Sep 18, 2013 at 4:47 AM, Andrew Grieve <agrieve@chromium.org>
> wrote:
>
> > We used to post an announcement to the list announcing when an RC is
> > available, and having a download link for it.
> >
> > A download link doesn't make sense for CLI.
> >
> > I'm wondering if instead we could have:
> >
> > cordova platform add android --version=3.1.0-rc1
> > cordova platform update android --version=3.1.0-rc1
> >
> > Or maybe upload a version of CLI to with a "rc" tag?
> >
> > e.g.:
> > npm install -g cordova@3.1.0-rc1
> > cordova platform add android
> > cordova platform update android
> >
> >
> > I'm thinking the --version flag would be useful to have either way, and
> > that we should do the custom npm tag for the RC.
> >
> > Thoughts?
> >
> > The other part of this is how long we let the RC bake. If we stick to
> > releasing on Monday, then that's not much time at all (but makes it in
> time
> > for PGD EU). Maybe from next release onward we have a longer RC time?
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message