You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by Andrew Grieve <ag...@chromium.org> on 2013/09/18 04:47:51 UTC
Testing RCs in a 3.0 world
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?
Re: Testing RCs in a 3.0 world
Posted by Braden Shepherdson <br...@chromium.org>.
That is indeed what I did. You can't stop npm from moving the latest tag
when you publish (so far as I could find out, anyway) but then you can
change it back right away with npm tag. I have done this and it's confirmed
by the fact that npmjs.org and npm info both show the previous
3.0.0-targeting versions as current.
Braden
On Sun, Sep 22, 2013 at 7:50 AM, Andrew Grieve <ag...@chromium.org> wrote:
> 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 <ag...@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?
> > >
> >
>
Re: Testing RCs in a 3.0 world
Posted by Andrew Grieve <ag...@chromium.org>.
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 <ag...@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?
> >
>
Re: Testing RCs in a 3.0 world
Posted by Brian LeRoux <b...@brian.io>.
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 <ag...@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?
>