You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by Steven Gill <st...@gmail.com> on 2014/08/30 03:34:54 UTC
[Vote] 3.6.0 Cadence Release
Please review and vote on this 3.6.0 Cadence Release.
Release issue: https://issues.apache.org/jira/browse/CB-7383
Repos ready to be released have been published to
dist/dev:https://dist.apache.org/repos/dist/dev/cordova/CB-7383
The packages were published from their corresponding git tags:
cordova-android: 3.6.0 (014327c59a)
cordova-ios: 3.6.0 (3a92b2dbf0)
cordova-blackberry: 3.6.0 (ed435bfc9e)
cordova-windows: 3.6.0 (cdb292f4a3)
cordova-wp8: 3.6.0 (a879f5258b)
cordova-firefoxos: 3.6.0 (9ab176f855)
cordova-ubuntu: 3.6.0 (bff472e4c2)
cordova-amazon-fireos: 3.6.0 (4e94c6d198)
cordova-js: 3.6.0 (906b34c0a4)
cordova-mobile-spec: 3.6.0 (27053f7dd8)
cordova-app-hello-world: 3.6.0 (65a2171a19)
cordova-cli: 3.6.0-0.2.8 (01cb09f2d1)
cordova-lib: 0.21.8 (14670ec9b5)
cordova-plugman: 0.22.5 (29488fce7e)
Upon a successful vote I will upload the archives to dist/, publish
them to NPM, and post the corresponding blog post.
Voting guidelines:
https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md
Voting will go on for a minimum of 72 hours.
I vote +1:
* Ran coho audit-license-headers over the relevant repos
* Used `license-checker` to ensure all dependencies have
Apache-compatible licenses
* Ensured continuous build was green when repos were tagged
Re: [Vote] 3.6.0 Cadence Release
Posted by Marcel Kinard <cm...@gmail.com>.
This won't be an issue until a plugins release, but in the plugins should the version of the test plugin (cordova-plugin-*/tests/plugin.xml) also be incremented at the same time and to the same value as the plugin itself?
On Sep 2, 2014, at 1:57 PM, Steven Gill <st...@gmail.com> wrote:
> Another mistake I found, wp8's package.json was set to 3.6.0-dev on the
> 3.6.x branch. I had to update that to publish to npm under rc tag.
>
> This vote is going to need to get restarted, but I suggest we continue to
> test what is uploaded to see if any more fixes are needed.
Re: [Vote] 3.6.0 Cadence Release
Posted by Jesse <pu...@gmail.com>.
Restarting the vote will not allow us to complete it before Steve is on
vacation, but assuming the vote passes, we can still release it regardless.
If the only issues that come up today are administrative, I would like to
recommend that we do a quick vote, on the assumption that the
platforms/projects themselves are all okay, and it is just issues with
tags+versionnumbers and whatnot.
@purplecabbage
risingj.com
On Tue, Sep 2, 2014 at 11:58 AM, Sergey Grebnov (Akvelon) <
v-segreb@microsoft.com> wrote:
> If we restart the thread, will we be able to complete it before Steven
> gone on vacation or someone else will be able to accomplish this?
>
> Thx!
> Sergey
> -----Original Message-----
> From: Steven Gill [mailto:stevengill97@gmail.com]
> Sent: Tuesday, September 2, 2014 9:57 PM
> To: dev@cordova.apache.org
> Cc: Michal Mocny
> Subject: Re: [Vote] 3.6.0 Cadence Release
>
> Another mistake I found, wp8's package.json was set to 3.6.0-dev on the
> 3.6.x branch. I had to update that to publish to npm under rc tag.
>
> This vote is going to need to get restarted, but I suggest we continue to
> test what is uploaded to see if any more fixes are needed.
>
>
> On Tue, Sep 2, 2014 at 10:54 AM, Steven Gill <st...@gmail.com>
> wrote:
>
> > Looks like CLI VERSION file is incorrect :( Didn't get updated. Also
> > looks like the zip i uploaded for the CLI got generated incorrectly.
> > Need to take a deeper look.
> >
> > I don't see cordova-js 3.6.0-dev Version file anywhere.
> >
> > I'm also running into an issue with firefoxos testing. Looks like it
> > can't find shelljs module.
> >
> >
> >
> > On Tue, Sep 2, 2014 at 10:47 AM, Michal Mocny <mm...@chromium.org>
> wrote:
> >
> >> .. Looks like cordova-cli still has a VERSION file set to
> >> 3.5.0-0.2.4. Is it even used?
> >>
> >> .. and cordova-cli deps on cordova-lib which deps on cordova-js which
> >> has VERSION file set to 3.6.0-dev.
> >>
> >>
> >> On Tue, Sep 2, 2014 at 1:42 PM, Michal Mocny <mm...@chromium.org>
> wrote:
> >>
> >> > We could ask Apache folk for clarification, but if I understand the
> >> > requirements for release process correct, I think publishing an rc
> >> > and voting on it would be totally acceptable provided that:
> >> >
> >> > (a) *exactly* the tarball that went up to RC is used as the final
> >> release,
> >> > so that signatures match. At the very least I think that would
> >> > mean to leaving the "-rc#" portion out of all the "version" key
> >> > (and any VERSION files).
> >> > (b) We don't advertise to users that this is a release they should
> >> consume.
> >> >
> >> > It looks like Steven has done this.
> >> >
> >> > -Michal
> >> >
> >> >
> >> > On Tue, Sep 2, 2014 at 1:26 PM, Steven Gill
> >> > <st...@gmail.com>
> >> > wrote:
> >> >
> >> >> Actually, I like Carlos suggestion.
> >> >>
> >> >> We have already been publishing to npm under the RC tag for
> >> >> testing
> >> (not
> >> >> releasing to public but just for dev testing).
> >> >>
> >> >> The last few releases you could go npm install cordova@rc and that
> >> would
> >> >> download the RC version of cordova that we were voting on.
> >> >>
> >> >> I went ahead and published all of the platforms + lib + plugman +
> >> >> js (everything we are voting on) to npm under an rc tag. So npm
> >> >> install cordova-android@rc would grab version 3.6.0.
> >> >>
> >> >> The easiest way to test is to now go npm install cordova@rc. No
> >> >> need
> >> to
> >> >> --usegit anymore.
> >> >>
> >> >> The --usegit method would require you to checkout the tags in
> >> cordova-lib,
> >> >> cordova-js, npm link them, go to cli, npm link them, etc.
> >> >>
> >> >> -Steve
> >> >>
> >> >>
> >> >> On Tue, Sep 2, 2014 at 10:23 AM, Parashuram Narasimhan (MS OPEN
> >> >> TECH) < panarasi@microsoft.com> wrote:
> >> >>
> >> >> > Agree with Jesse. If you still want to test it, I tried doing it
> >> with a
> >> >> > private npm registry, and changed my npm to pick up from that
> >> registry.
> >> >> I
> >> >> > did not see a lot of value added though. I did this when I was
> >> playing
> >> >> with
> >> >> > the idea of using npm to use plugins.
> >> >> >
> >> >> > -----Original Message-----
> >> >> > From: Jesse [mailto:purplecabbage@gmail.com]
> >> >> > Sent: Tuesday, September 2, 2014 10:21 AM
> >> >> > To: dev@cordova.apache.org
> >> >> > Subject: Re: [Vote] 3.6.0 Cadence Release
> >> >> >
> >> >> > We cannot post to npm without the vote passing. There is a bunch
> >> >> > of
> >> >> crazy
> >> >> > overhead tag bs we could do, but then we would not be voting on
> >> >> > the
> >> >> final
> >> >> > released binaries.
> >> >> >
> >> >> > Just test with --usegit
> >> >> >
> >> >> >
> >> >> >
> >> >> > @purplecabbage
> >> >> > risingj.com
> >> >> >
> >> >> >
> >> >> > On Tue, Sep 2, 2014 at 6:47 AM, Carlos Santana
> >> >> > <csantana23@gmail.com
> >> >
> >> >> > wrote:
> >> >> >
> >> >> > > I see cordova cli rc on npm, I want to test it using npm but I
> >> >> > > get
> >> >> > errors.
> >> >> > > Maybe cordova-lib should be also posted to npm but not make it
> >> latest
> >> >> > > until we release.
> >> >> > >
> >> >> > > I get this errors:
> >> >> > >
> >> >> > > $ npm install cordova@rc
> >> >> > >
> >> >> > > npm ERR! Error: version not found: cordova-lib@0.21.8
> >> >> > >
> >> >> > >
> >> >> > > On Tue, Sep 2, 2014 at 9:29 AM, Bryan Higgins <
> >> bryan@bryanhiggins.net
> >> >> >
> >> >> > > wrote:
> >> >> > >
> >> >> > > > +1
> >> >> > > >
> >> >> > > > - Verified signatures and hashes for cordova-blackberry
> >> >> > > > - Verified sha1 match tag 3.6.0
> >> >> > > > - Ran mobile spec on various BB10 devices and OS versions
> >> >> > > >
> >> >> > > > Steve - I added you as an owner for cordova-blackberry10 on
> npm.
> >> The
> >> >> > > > cordova-blackberry package should probably be unpublished.
> >> >> > > >
> >> >> > > >
> >> >> > > > On Tue, Sep 2, 2014 at 1:15 AM, Archana Naik
> >> >> > > > <na...@gmail.com>
> >> >> > > > wrote:
> >> >> > > >
> >> >> > > > > vote +1
> >> >> > > > > Verified amazon-fireos bundle, signatures and hashes.
> >> >> > > > >
> >> >> > > > > When are we planning to publish it to npm?
> >> >> > > > >
> >> >> > > > >
> >> >> > > > > On Mon, Sep 1, 2014 at 2:40 PM, Sergey Grebnov (Akvelon) <
> >> >> > > > > v-segreb@microsoft.com> wrote:
> >> >> > > > >
> >> >> > > > > > I vote +1:
> >> >> > > > > > * Verified signatures and hashes for cordova-cli,
> >> cordova-lib,
> >> >> > > > > > cordova-plugman, cordova-windows, cordova-wp8
> >> >> > > > > > * Verified sha1s match tags for cordova-cli,
> >> >> > > > > > cordova-lib,
> >> >> > > > > cordova-plugman,
> >> >> > > > > > cordova-windows, cordova-wp8
> >> >> > > > > > * Run Medic tests for Windows and Windows Phone 8
> >> >> > > > > > * Tested Android build on Windows
> >> >> > > > > > * Tested Windows platform manually
> >> >> > > > > > building and running app with VS2012 (msbuild
> >> >> > > > > > 4.0)/VS2013(msbuild
> >> >> > > > > 12.0)
> >> >> > > > > > -win and -phone switches
> >> >> > > > > > support of target platform settings (config.xml)
> >> >> > > > > > support of custom icons and splash screen images
> >> >> > > > > >
> >> >> > > > > > Thx!
> >> >> > > > > > Sergey
> >> >> > > > > > -----Original Message-----
> >> >> > > > > > From: Steven Gill [mailto:stevengill97@gmail.com]
> >> >> > > > > > Sent: Saturday, August 30, 2014 5:35 AM
> >> >> > > > > > To: dev@cordova.apache.org
> >> >> > > > > > Subject: [Vote] 3.6.0 Cadence Release
> >> >> > > > > >
> >> >> > > > > > Please review and vote on this 3.6.0 Cadence Release.
> >> >> > > > > >
> >> >> > > > > > Release issue:
> >> >> > > > > > https://issues.apache.org/jira/browse/CB-7383
> >> >> > > > > >
> >> >> > > > > > Repos ready to be released have been published to
> >> >> > > > > > dist/dev:
> >> https://dist.apache.org/repos/dist/dev/cordova/CB-7383
> >> >> > > > > >
> >> >> > > > > > The packages were published from their corresponding git
> >> tags:
> >> >> > > > > > cordova-android: 3.6.0 (014327c59a)
> >> >> > > > > > cordova-ios: 3.6.0 (3a92b2dbf0)
> >> >> > > > > > cordova-blackberry: 3.6.0 (ed435bfc9e)
> >> >> > > > > > cordova-windows: 3.6.0 (cdb292f4a3)
> >> >> > > > > > cordova-wp8: 3.6.0 (a879f5258b)
> >> >> > > > > > cordova-firefoxos: 3.6.0 (9ab176f855)
> >> >> > > > > >
> >> >> > > > > > cordova-ubuntu: 3.6.0 (bff472e4c2)
> >> >> > > > > > cordova-amazon-fireos: 3.6.0 (4e94c6d198)
> >> >> > > > > > cordova-js: 3.6.0 (906b34c0a4)
> >> >> > > > > > cordova-mobile-spec: 3.6.0 (27053f7dd8)
> >> >> > > > > > cordova-app-hello-world: 3.6.0 (65a2171a19)
> >> >> > > > > >
> >> >> > > > > > cordova-cli: 3.6.0-0.2.8 (01cb09f2d1)
> >> >> > > > > > cordova-lib: 0.21.8 (14670ec9b5)
> >> >> > > > > > cordova-plugman: 0.22.5 (29488fce7e)
> >> >> > > > > >
> >> >> > > > > >
> >> >> > > > > > Upon a successful vote I will upload the archives to
> >> >> > > > > > dist/, publish
> >> >> > > > them
> >> >> > > > > > to NPM, and post the corresponding blog post.
> >> >> > > > > >
> >> >> > > > > > Voting guidelines:
> >> >> > > > > >
> >> >> > > > >
> >> >> > > >
> >> >> > >
> >> >> https://github.com/apache/cordova-coho/blob/master/docs/release-vo
> >> >> ting
> >> >> > > .md
> >> >> > > > > >
> >> >> > > > > > Voting will go on for a minimum of 72 hours.
> >> >> > > > > >
> >> >> > > > > > I vote +1:
> >> >> > > > > > * Ran coho audit-license-headers over the relevant repos
> >> >> > > > > > * Used `license-checker` to ensure all dependencies have
> >> >> > > > > Apache-compatible
> >> >> > > > > > licenses
> >> >> > > > > > * Ensured continuous build was green when repos were
> >> >> > > > > > tagged
> >> >> > > > > >
> >> >> > > > >
> >> >> > > >
> >> >> > >
> >> >> > >
> >> >> > >
> >> >> > > --
> >> >> > > Carlos Santana
> >> >> > > <cs...@gmail.com>
> >> >> > >
> >> >> >
> >> >>
> >> >
> >> >
> >>
> >
> >
>
Re: [Vote] 3.6.0 Cadence Release
Posted by Joe Bowser <bo...@gmail.com>.
I looked at BigTop, and it's using C-style comment syntax. I'm adding the
headers now.
On Thu, Sep 4, 2014 at 10:41 AM, Josh Soref <js...@blackberry.com> wrote:
> Joe Bowser wrote:
>
> >So, should we also fix this before the release? I'm thinking we probably
> >should:
> >
> >https://issues.apache.org/jira/browse/CB-7463
> >
> >I've fixed it on master, so we could just cherry-pick it into Android.
>
> I'm assuming that you aren't shipping the tests.
>
> $ find . -name '*gradle*'
> ./platforms/android/build.gradle
> ./platforms/android/CordovaLib/build.gradle
> ./platforms/android/settings.gradle
>
> It looks like you need to license both settings and build..
>
> http://www.gradle.org/docs/current/userguide/working_with_files.html
>
> Seems to indicate `//` is a comment.
>
>
Re: [Vote] 3.6.0 Cadence Release
Posted by Marcel Kinard <cm...@gmail.com>.
I updated the archive in dist-dev with this new content and tag.
On Sep 4, 2014, at 2:19 PM, Joe Bowser <bo...@gmail.com> wrote:
> I did the re-tag of the release with the licences added. We should be able
> to get this going again, assuming we don't find more issues with Android.
>
>
> On Thu, Sep 4, 2014 at 10:53 AM, Josh Soref <js...@blackberry.com> wrote:
>
>> Joe Bowser wrote:
>>> I think we do ship the native tests.
>>
>> You do. They just don't end up in cordova projects.
>>
>>> The problem with the native tests is that they're unique to Android and
>>> don't have a home elsewhere. I would prefer not shipping them, but that
>>> means we have to create a new repository.
>>
>> You should be able to work through this (by reorganizing your git
>> repository).
>>
>> consider:
>> https://registry.npmjs.org/cordova-lib/-/cordova-lib-0.21.9.tgz
>> From cordova-lib it doesn't have things in the spec-* directories
>>
>>
Re: [Vote] 3.6.0 Cadence Release
Posted by Joe Bowser <bo...@gmail.com>.
I did the re-tag of the release with the licences added. We should be able
to get this going again, assuming we don't find more issues with Android.
On Thu, Sep 4, 2014 at 10:53 AM, Josh Soref <js...@blackberry.com> wrote:
> Joe Bowser wrote:
> >I think we do ship the native tests.
>
> You do. They just don't end up in cordova projects.
>
> > The problem with the native tests is that they're unique to Android and
> > don't have a home elsewhere. I would prefer not shipping them, but that
> > means we have to create a new repository.
>
> You should be able to work through this (by reorganizing your git
> repository).
>
> consider:
> https://registry.npmjs.org/cordova-lib/-/cordova-lib-0.21.9.tgz
> From cordova-lib it doesn't have things in the spec-* directories
>
>
Re: [Vote] 3.6.0 Cadence Release
Posted by Josh Soref <js...@blackberry.com>.
Joe Bowser wrote:
>I think we do ship the native tests.
You do. They just don't end up in cordova projects.
> The problem with the native tests is that they're unique to Android and
> don't have a home elsewhere. I would prefer not shipping them, but that
> means we have to create a new repository.
You should be able to work through this (by reorganizing your git
repository).
consider:
https://registry.npmjs.org/cordova-lib/-/cordova-lib-0.21.9.tgz
From cordova-lib it doesn't have things in the spec-* directories
Re: [Vote] 3.6.0 Cadence Release
Posted by Joe Bowser <bo...@gmail.com>.
I think we do ship the native tests. The problem with the native tests is
that they're unique to Android and don't have a home elsewhere. I would
prefer not shipping them, but that means we have to create a new repository.
On Thu, Sep 4, 2014 at 10:41 AM, Josh Soref <js...@blackberry.com> wrote:
> Joe Bowser wrote:
>
> >So, should we also fix this before the release? I'm thinking we probably
> >should:
> >
> >https://issues.apache.org/jira/browse/CB-7463
> >
> >I've fixed it on master, so we could just cherry-pick it into Android.
>
> I'm assuming that you aren't shipping the tests.
>
> $ find . -name '*gradle*'
> ./platforms/android/build.gradle
> ./platforms/android/CordovaLib/build.gradle
> ./platforms/android/settings.gradle
>
> It looks like you need to license both settings and build..
>
> http://www.gradle.org/docs/current/userguide/working_with_files.html
>
> Seems to indicate `//` is a comment.
>
>
Re: [Vote] 3.6.0 Cadence Release
Posted by Marcel Kinard <cm...@gmail.com>.
If you want to, now is the time.
On Sep 4, 2014, at 1:33 PM, Joe Bowser <bo...@gmail.com> wrote:
> So, should we also fix this before the release? I'm thinking we probably
> should:
>
> https://issues.apache.org/jira/browse/CB-7463
Re: [Vote] 3.6.0 Cadence Release
Posted by Josh Soref <js...@blackberry.com>.
Joe Bowser wrote:
>So, should we also fix this before the release? I'm thinking we probably
>should:
>
>https://issues.apache.org/jira/browse/CB-7463
>
>I've fixed it on master, so we could just cherry-pick it into Android.
I'm assuming that you aren't shipping the tests.
$ find . -name '*gradle*'
./platforms/android/build.gradle
./platforms/android/CordovaLib/build.gradle
./platforms/android/settings.gradle
It looks like you need to license both settings and build..
http://www.gradle.org/docs/current/userguide/working_with_files.html
Seems to indicate `//` is a comment.
Re: [Vote] 3.6.0 Cadence Release
Posted by Joe Bowser <bo...@gmail.com>.
So, should we also fix this before the release? I'm thinking we probably
should:
https://issues.apache.org/jira/browse/CB-7463
I've fixed it on master, so we could just cherry-pick it into Android.
On Thu, Sep 4, 2014 at 10:31 AM, Jason Proctor <ja...@redfish.net> wrote:
> On Thu, Sep 4, 2014 at 10:26 AM, Josh Soref <js...@blackberry.com> wrote:
>
> > Jason Proctor wrote:
> > >i upgraded to what looked like 3.6.0 earlier this week and ran into some
> > >firefoxos build issues - no module called shelljs or similar.
> fortunately
> > >the downgrade worked so i'm back in business.
> > >
> > >has this issue been fixed in the current 3.6.0 candidate?
> > >
> > >(i'd like to upgrade to see whether a couple of other firefoxos issues
> > >have
> > >been sorted.)
> >
> > Seems to work. Otoh, if I try:
> >
> > cordova platform add firefoxos@3.6.0
> >
> >
> > I get an error about shelljs, so yes, this appears fixed.
> >
> >
> wonderful. thanks for the response.
>
Re: [Vote] 3.6.0 Cadence Release
Posted by Jason Proctor <ja...@redfish.net>.
On Thu, Sep 4, 2014 at 10:26 AM, Josh Soref <js...@blackberry.com> wrote:
> Jason Proctor wrote:
> >i upgraded to what looked like 3.6.0 earlier this week and ran into some
> >firefoxos build issues - no module called shelljs or similar. fortunately
> >the downgrade worked so i'm back in business.
> >
> >has this issue been fixed in the current 3.6.0 candidate?
> >
> >(i'd like to upgrade to see whether a couple of other firefoxos issues
> >have
> >been sorted.)
>
> Seems to work. Otoh, if I try:
>
> cordova platform add firefoxos@3.6.0
>
>
> I get an error about shelljs, so yes, this appears fixed.
>
>
wonderful. thanks for the response.
Re: [Vote] 3.6.0 Cadence Release
Posted by Josh Soref <js...@blackberry.com>.
Jason Proctor wrote:
>i upgraded to what looked like 3.6.0 earlier this week and ran into some
>firefoxos build issues - no module called shelljs or similar. fortunately
>the downgrade worked so i'm back in business.
>
>has this issue been fixed in the current 3.6.0 candidate?
>
>(i'd like to upgrade to see whether a couple of other firefoxos issues
>have
>been sorted.)
$ cordova create ss
Creating a new cordova project with name "HelloCordova" and id
"io.cordova.hellocordova" at location "/private/tmp/ss"
Downloading cordova library for www...
Download complete
$ cd ss
$ cordova platform add firefoxos@rc
npm http GET https://registry.npmjs.org/cordova-firefoxos
npm http 200 https://registry.npmjs.org/cordova-firefoxos
npm http GET
https://registry.npmjs.org/cordova-firefoxos/-/cordova-firefoxos-3.6.1.tgz
npm http 200
https://registry.npmjs.org/cordova-firefoxos/-/cordova-firefoxos-3.6.1.tgz
Creating firefoxos project...
Project Path ../../../tmp/ss/platforms/firefoxos
Package Name io.cordova.hellocordova
Project Name HelloCordova
$ cordova build
Running command: /tmp/ss/platforms/firefoxos/cordova/build
Cleaning Firefoxos project
Firefox OS packaged app built in platforms/firefoxos/build/package.zip
Seems to work. Otoh, if I try:
cordova platform add firefoxos@3.6.0
I get an error about shelljs, so yes, this appears fixed.
Re: [Vote] 3.6.0 Cadence Release
Posted by Jason Proctor <ja...@redfish.net>.
newbie chiming in...
i upgraded to what looked like 3.6.0 earlier this week and ran into some
firefoxos build issues - no module called shelljs or similar. fortunately
the downgrade worked so i'm back in business.
has this issue been fixed in the current 3.6.0 candidate?
(i'd like to upgrade to see whether a couple of other firefoxos issues have
been sorted.)
thanks for all the effort
J
On Thu, Sep 4, 2014 at 9:13 AM, Marcel Kinard <cm...@gmail.com> wrote:
> That looks better. Thanks!
>
> On Sep 4, 2014, at 12:05 PM, Jesse <pu...@gmail.com> wrote:
>
> > Okay, I think it's all cleaned up now ... sorry for the mess.
> >
> > @purplecabbage
> > risingj.com
> >
> >
> > On Thu, Sep 4, 2014 at 8:48 AM, Jesse <pu...@gmail.com> wrote:
> >
> >> Oops, I'll sort this mess out now.
> >>
> >> @purplecabbage
> >> risingj.com
> >>
> >>
> >> On Thu, Sep 4, 2014 at 8:23 AM, Marcel Kinard <cm...@gmail.com>
> wrote:
> >>
> >>> I'm looking at the 3.6.x branch of the wp8 repo, and seeing some
> strange
> >>> things:
> >>>
> >>> - the 3.6.0 tag is not at the head of the 3.6.x branch. It's not at the
> >>> head of master either. It looks to be on a branch that has no head.
> Doesn't
> >>> make sense to me.
> >>> - the addition of "bundledDependencies" to the package.json [f5453b9]
> is
> >>> not in the 3.6.x branch. But it is on that unnamed branch with the
> 3.6.0
> >>> tag.
> >>> - the removal of "-dev" from package.json [f6690f1] is not fully in the
> >>> 3.6.x branch. It still says "-dev" in the description property. But it
> is
> >>> on that unnamed branch with the 3.6.0 tag.
> >>>
> >>> I'm thinking this should get cleaned up before packaging. I could
> >>> cherry-pick the 2 commits from the unnamed branch to the 3.6.x branch
> and
> >>> visually inspect the resulting package.json, and move the 3.6.0 tag,
> or is
> >>> there a different approach that should be used here?
> >>>
> >>> I'll package up windows and android in the meantime.
>
Re: [Vote] 3.6.0 Cadence Release
Posted by Marcel Kinard <cm...@gmail.com>.
That looks better. Thanks!
On Sep 4, 2014, at 12:05 PM, Jesse <pu...@gmail.com> wrote:
> Okay, I think it's all cleaned up now ... sorry for the mess.
>
> @purplecabbage
> risingj.com
>
>
> On Thu, Sep 4, 2014 at 8:48 AM, Jesse <pu...@gmail.com> wrote:
>
>> Oops, I'll sort this mess out now.
>>
>> @purplecabbage
>> risingj.com
>>
>>
>> On Thu, Sep 4, 2014 at 8:23 AM, Marcel Kinard <cm...@gmail.com> wrote:
>>
>>> I'm looking at the 3.6.x branch of the wp8 repo, and seeing some strange
>>> things:
>>>
>>> - the 3.6.0 tag is not at the head of the 3.6.x branch. It's not at the
>>> head of master either. It looks to be on a branch that has no head. Doesn't
>>> make sense to me.
>>> - the addition of "bundledDependencies" to the package.json [f5453b9] is
>>> not in the 3.6.x branch. But it is on that unnamed branch with the 3.6.0
>>> tag.
>>> - the removal of "-dev" from package.json [f6690f1] is not fully in the
>>> 3.6.x branch. It still says "-dev" in the description property. But it is
>>> on that unnamed branch with the 3.6.0 tag.
>>>
>>> I'm thinking this should get cleaned up before packaging. I could
>>> cherry-pick the 2 commits from the unnamed branch to the 3.6.x branch and
>>> visually inspect the resulting package.json, and move the 3.6.0 tag, or is
>>> there a different approach that should be used here?
>>>
>>> I'll package up windows and android in the meantime.
Re: [Vote] 3.6.0 Cadence Release
Posted by Jesse <pu...@gmail.com>.
Okay, I think it's all cleaned up now ... sorry for the mess.
@purplecabbage
risingj.com
On Thu, Sep 4, 2014 at 8:48 AM, Jesse <pu...@gmail.com> wrote:
> Oops, I'll sort this mess out now.
>
> @purplecabbage
> risingj.com
>
>
> On Thu, Sep 4, 2014 at 8:23 AM, Marcel Kinard <cm...@gmail.com> wrote:
>
>> I'm looking at the 3.6.x branch of the wp8 repo, and seeing some strange
>> things:
>>
>> - the 3.6.0 tag is not at the head of the 3.6.x branch. It's not at the
>> head of master either. It looks to be on a branch that has no head. Doesn't
>> make sense to me.
>> - the addition of "bundledDependencies" to the package.json [f5453b9] is
>> not in the 3.6.x branch. But it is on that unnamed branch with the 3.6.0
>> tag.
>> - the removal of "-dev" from package.json [f6690f1] is not fully in the
>> 3.6.x branch. It still says "-dev" in the description property. But it is
>> on that unnamed branch with the 3.6.0 tag.
>>
>> I'm thinking this should get cleaned up before packaging. I could
>> cherry-pick the 2 commits from the unnamed branch to the 3.6.x branch and
>> visually inspect the resulting package.json, and move the 3.6.0 tag, or is
>> there a different approach that should be used here?
>>
>> I'll package up windows and android in the meantime.
>>
>> On Sep 4, 2014, at 9:39 AM, Marcel Kinard <cm...@gmail.com> wrote:
>>
>> > I will get to this today.
>> >
>> > On Sep 3, 2014, at 7:42 PM, Jesse <pu...@gmail.com> wrote:
>> >
>> >> I believe we are good to go for packaging, uploading and starting a new
>> >> vote thread.
>> >> Marcel, do you want to do the honors?
>> >>
>> >> We need to add Android to the command as it was retagged also :
>> >>
>> >> coho create-archive -r wp8 -r windows -r android --dest
>> >> cordova-dist-dev/$JIRA --tag 3.6.0
>> >
>>
>>
>
Re: [Vote] 3.6.0 Cadence Release
Posted by Jesse <pu...@gmail.com>.
Oops, I'll sort this mess out now.
@purplecabbage
risingj.com
On Thu, Sep 4, 2014 at 8:23 AM, Marcel Kinard <cm...@gmail.com> wrote:
> I'm looking at the 3.6.x branch of the wp8 repo, and seeing some strange
> things:
>
> - the 3.6.0 tag is not at the head of the 3.6.x branch. It's not at the
> head of master either. It looks to be on a branch that has no head. Doesn't
> make sense to me.
> - the addition of "bundledDependencies" to the package.json [f5453b9] is
> not in the 3.6.x branch. But it is on that unnamed branch with the 3.6.0
> tag.
> - the removal of "-dev" from package.json [f6690f1] is not fully in the
> 3.6.x branch. It still says "-dev" in the description property. But it is
> on that unnamed branch with the 3.6.0 tag.
>
> I'm thinking this should get cleaned up before packaging. I could
> cherry-pick the 2 commits from the unnamed branch to the 3.6.x branch and
> visually inspect the resulting package.json, and move the 3.6.0 tag, or is
> there a different approach that should be used here?
>
> I'll package up windows and android in the meantime.
>
> On Sep 4, 2014, at 9:39 AM, Marcel Kinard <cm...@gmail.com> wrote:
>
> > I will get to this today.
> >
> > On Sep 3, 2014, at 7:42 PM, Jesse <pu...@gmail.com> wrote:
> >
> >> I believe we are good to go for packaging, uploading and starting a new
> >> vote thread.
> >> Marcel, do you want to do the honors?
> >>
> >> We need to add Android to the command as it was retagged also :
> >>
> >> coho create-archive -r wp8 -r windows -r android --dest
> >> cordova-dist-dev/$JIRA --tag 3.6.0
> >
>
>
Re: [Vote] 3.6.0 Cadence Release
Posted by Marcel Kinard <cm...@gmail.com>.
I'm looking at the 3.6.x branch of the wp8 repo, and seeing some strange things:
- the 3.6.0 tag is not at the head of the 3.6.x branch. It's not at the head of master either. It looks to be on a branch that has no head. Doesn't make sense to me.
- the addition of "bundledDependencies" to the package.json [f5453b9] is not in the 3.6.x branch. But it is on that unnamed branch with the 3.6.0 tag.
- the removal of "-dev" from package.json [f6690f1] is not fully in the 3.6.x branch. It still says "-dev" in the description property. But it is on that unnamed branch with the 3.6.0 tag.
I'm thinking this should get cleaned up before packaging. I could cherry-pick the 2 commits from the unnamed branch to the 3.6.x branch and visually inspect the resulting package.json, and move the 3.6.0 tag, or is there a different approach that should be used here?
I'll package up windows and android in the meantime.
On Sep 4, 2014, at 9:39 AM, Marcel Kinard <cm...@gmail.com> wrote:
> I will get to this today.
>
> On Sep 3, 2014, at 7:42 PM, Jesse <pu...@gmail.com> wrote:
>
>> I believe we are good to go for packaging, uploading and starting a new
>> vote thread.
>> Marcel, do you want to do the honors?
>>
>> We need to add Android to the command as it was retagged also :
>>
>> coho create-archive -r wp8 -r windows -r android --dest
>> cordova-dist-dev/$JIRA --tag 3.6.0
>
Re: [Vote] 3.6.0 Cadence Release
Posted by Marcel Kinard <cm...@gmail.com>.
I will get to this today.
On Sep 3, 2014, at 7:42 PM, Jesse <pu...@gmail.com> wrote:
> I believe we are good to go for packaging, uploading and starting a new
> vote thread.
> Marcel, do you want to do the honors?
>
> We need to add Android to the command as it was retagged also :
>
> coho create-archive -r wp8 -r windows -r android --dest
> cordova-dist-dev/$JIRA --tag 3.6.0
Re: [Vote] 3.6.0 Cadence Release
Posted by Jesse <pu...@gmail.com>.
I believe we are good to go for packaging, uploading and starting a new
vote thread.
Marcel, do you want to do the honors?
We need to add Android to the command as it was retagged also :
coho create-archive -r wp8 -r windows -r android --dest
cordova-dist-dev/$JIRA --tag 3.6.0
@purplecabbage
risingj.com
On Wed, Sep 3, 2014 at 3:36 PM, Jesse <pu...@gmail.com> wrote:
> I am on this stuff now, will inform.
>
> @purplecabbage
> risingj.com
>
>
> On Wed, Sep 3, 2014 at 2:36 PM, Parashuram Narasimhan (MS OPEN TECH) <
> panarasi@microsoft.com> wrote:
>
>> Sergey should be able to help, but he is in a different time zone. Do we
>> know a list of things remaining ?
>>
>> -----Original Message-----
>> From: Marcel Kinard [mailto:cmarcelk@gmail.com]
>> Sent: Wednesday, September 3, 2014 2:16 PM
>> To: dev@cordova.apache.org
>> Subject: Re: [Vote] 3.6.0 Cadence Release
>>
>> Could Sergey or Staci help out? If your time runs out, what specifically
>> is left?
>>
>> On Sep 3, 2014, at 1:42 PM, Jesse <pu...@gmail.com> wrote:
>>
>> > I believe so, I am working through this today. I am also in the
>> > process of moving from Canada to the US, so I may not be able to do
>> > much past mid-late afternoon.
>> >
>> > On Wed, Sep 3, 2014 at 10:20 AM, Marcel Kinard <cm...@gmail.com>
>> wrote:
>> >
>> >> So the last thing holding back a new vote thread is a new rc for wp8
>> >> and windows which depends on CB-7455?
>>
>>
>
Re: [Vote] 3.6.0 Cadence Release
Posted by Jesse <pu...@gmail.com>.
I am on this stuff now, will inform.
@purplecabbage
risingj.com
On Wed, Sep 3, 2014 at 2:36 PM, Parashuram Narasimhan (MS OPEN TECH) <
panarasi@microsoft.com> wrote:
> Sergey should be able to help, but he is in a different time zone. Do we
> know a list of things remaining ?
>
> -----Original Message-----
> From: Marcel Kinard [mailto:cmarcelk@gmail.com]
> Sent: Wednesday, September 3, 2014 2:16 PM
> To: dev@cordova.apache.org
> Subject: Re: [Vote] 3.6.0 Cadence Release
>
> Could Sergey or Staci help out? If your time runs out, what specifically
> is left?
>
> On Sep 3, 2014, at 1:42 PM, Jesse <pu...@gmail.com> wrote:
>
> > I believe so, I am working through this today. I am also in the
> > process of moving from Canada to the US, so I may not be able to do
> > much past mid-late afternoon.
> >
> > On Wed, Sep 3, 2014 at 10:20 AM, Marcel Kinard <cm...@gmail.com>
> wrote:
> >
> >> So the last thing holding back a new vote thread is a new rc for wp8
> >> and windows which depends on CB-7455?
>
>
RE: [Vote] 3.6.0 Cadence Release
Posted by "Parashuram Narasimhan (MS OPEN TECH)" <pa...@microsoft.com>.
Sergey should be able to help, but he is in a different time zone. Do we know a list of things remaining ?
-----Original Message-----
From: Marcel Kinard [mailto:cmarcelk@gmail.com]
Sent: Wednesday, September 3, 2014 2:16 PM
To: dev@cordova.apache.org
Subject: Re: [Vote] 3.6.0 Cadence Release
Could Sergey or Staci help out? If your time runs out, what specifically is left?
On Sep 3, 2014, at 1:42 PM, Jesse <pu...@gmail.com> wrote:
> I believe so, I am working through this today. I am also in the
> process of moving from Canada to the US, so I may not be able to do
> much past mid-late afternoon.
>
> On Wed, Sep 3, 2014 at 10:20 AM, Marcel Kinard <cm...@gmail.com> wrote:
>
>> So the last thing holding back a new vote thread is a new rc for wp8
>> and windows which depends on CB-7455?
Re: [Vote] 3.6.0 Cadence Release
Posted by Marcel Kinard <cm...@gmail.com>.
Could Sergey or Staci help out? If your time runs out, what specifically is left?
On Sep 3, 2014, at 1:42 PM, Jesse <pu...@gmail.com> wrote:
> I believe so, I am working through this today. I am also in the process of
> moving from Canada to the US, so I may not be able to do much past mid-late
> afternoon.
>
> On Wed, Sep 3, 2014 at 10:20 AM, Marcel Kinard <cm...@gmail.com> wrote:
>
>> So the last thing holding back a new vote thread is a new rc for wp8 and
>> windows which depends on CB-7455?
Re: [Vote] 3.6.0 Cadence Release
Posted by Jesse <pu...@gmail.com>.
I believe so, I am working through this today. I am also in the process of
moving from Canada to the US, so I may not be able to do much past mid-late
afternoon.
On Wed, Sep 3, 2014 at 10:20 AM, Marcel Kinard <cm...@gmail.com> wrote:
> So the last thing holding back a new vote thread is a new rc for wp8 and
> windows which depends on CB-7455?
>
> On Sep 2, 2014, at 6:04 PM, Steven Gill <st...@gmail.com> wrote:
>
> > I'm officially closing this vote thread, new one will be up shortly.
> >
> > Thanks Marcel :). I'll make sure to add you to the repos just in case
> too.
>
>
Re: [Vote] 3.6.0 Cadence Release
Posted by Marcel Kinard <cm...@gmail.com>.
So the last thing holding back a new vote thread is a new rc for wp8 and windows which depends on CB-7455?
On Sep 2, 2014, at 6:04 PM, Steven Gill <st...@gmail.com> wrote:
> I'm officially closing this vote thread, new one will be up shortly.
>
> Thanks Marcel :). I'll make sure to add you to the repos just in case too.
Re: [Vote] 3.6.0 Cadence Release
Posted by Steven Gill <st...@gmail.com>.
I'm officially closing this vote thread, new one will be up shortly.
Thanks Marcel :). I'll make sure to add you to the repos just in case too.
On Tue, Sep 2, 2014 at 2:46 PM, Marcel Kinard <cm...@gmail.com> wrote:
> I would also be willing to do it, so feel free to use me now or in the
> future.
>
> On Sep 2, 2014, at 3:46 PM, Jesse <pu...@gmail.com> wrote:
>
> > Yes. I can do that.
> >
> > @purplecabbage
> > risingj.com
> >
> >
> > On Tue, Sep 2, 2014 at 12:44 PM, Steven Gill <st...@gmail.com>
> wrote:
> >
> >> I will get the blog post + updated dists ready and start the vote
> thread.
> >> Someone else will have to close the vote thread + publish packages &
> blog
> >> post.
> >>
> >> Any volunteers for that? Jesse? I need to add whoever it is to all of
> the
> >> npm repos.
>
>
Re: [Vote] 3.6.0 Cadence Release
Posted by Marcel Kinard <cm...@gmail.com>.
I would also be willing to do it, so feel free to use me now or in the future.
On Sep 2, 2014, at 3:46 PM, Jesse <pu...@gmail.com> wrote:
> Yes. I can do that.
>
> @purplecabbage
> risingj.com
>
>
> On Tue, Sep 2, 2014 at 12:44 PM, Steven Gill <st...@gmail.com> wrote:
>
>> I will get the blog post + updated dists ready and start the vote thread.
>> Someone else will have to close the vote thread + publish packages & blog
>> post.
>>
>> Any volunteers for that? Jesse? I need to add whoever it is to all of the
>> npm repos.
Re: [Vote] 3.6.0 Cadence Release
Posted by Jesse <pu...@gmail.com>.
Yes. I can do that.
@purplecabbage
risingj.com
On Tue, Sep 2, 2014 at 12:44 PM, Steven Gill <st...@gmail.com> wrote:
> I will get the blog post + updated dists ready and start the vote thread.
> Someone else will have to close the vote thread + publish packages & blog
> post.
>
> Any volunteers for that? Jesse? I need to add whoever it is to all of the
> npm repos.
>
>
> On Tue, Sep 2, 2014 at 11:58 AM, Sergey Grebnov (Akvelon) <
> v-segreb@microsoft.com> wrote:
>
> > If we restart the thread, will we be able to complete it before Steven
> > gone on vacation or someone else will be able to accomplish this?
> >
> > Thx!
> > Sergey
> > -----Original Message-----
> > From: Steven Gill [mailto:stevengill97@gmail.com]
> > Sent: Tuesday, September 2, 2014 9:57 PM
> > To: dev@cordova.apache.org
> > Cc: Michal Mocny
> > Subject: Re: [Vote] 3.6.0 Cadence Release
> >
> > Another mistake I found, wp8's package.json was set to 3.6.0-dev on the
> > 3.6.x branch. I had to update that to publish to npm under rc tag.
> >
> > This vote is going to need to get restarted, but I suggest we continue to
> > test what is uploaded to see if any more fixes are needed.
> >
> >
> > On Tue, Sep 2, 2014 at 10:54 AM, Steven Gill <st...@gmail.com>
> > wrote:
> >
> > > Looks like CLI VERSION file is incorrect :( Didn't get updated. Also
> > > looks like the zip i uploaded for the CLI got generated incorrectly.
> > > Need to take a deeper look.
> > >
> > > I don't see cordova-js 3.6.0-dev Version file anywhere.
> > >
> > > I'm also running into an issue with firefoxos testing. Looks like it
> > > can't find shelljs module.
> > >
> > >
> > >
> > > On Tue, Sep 2, 2014 at 10:47 AM, Michal Mocny <mm...@chromium.org>
> > wrote:
> > >
> > >> .. Looks like cordova-cli still has a VERSION file set to
> > >> 3.5.0-0.2.4. Is it even used?
> > >>
> > >> .. and cordova-cli deps on cordova-lib which deps on cordova-js which
> > >> has VERSION file set to 3.6.0-dev.
> > >>
> > >>
> > >> On Tue, Sep 2, 2014 at 1:42 PM, Michal Mocny <mm...@chromium.org>
> > wrote:
> > >>
> > >> > We could ask Apache folk for clarification, but if I understand the
> > >> > requirements for release process correct, I think publishing an rc
> > >> > and voting on it would be totally acceptable provided that:
> > >> >
> > >> > (a) *exactly* the tarball that went up to RC is used as the final
> > >> release,
> > >> > so that signatures match. At the very least I think that would
> > >> > mean to leaving the "-rc#" portion out of all the "version" key
> > >> > (and any VERSION files).
> > >> > (b) We don't advertise to users that this is a release they should
> > >> consume.
> > >> >
> > >> > It looks like Steven has done this.
> > >> >
> > >> > -Michal
> > >> >
> > >> >
> > >> > On Tue, Sep 2, 2014 at 1:26 PM, Steven Gill
> > >> > <st...@gmail.com>
> > >> > wrote:
> > >> >
> > >> >> Actually, I like Carlos suggestion.
> > >> >>
> > >> >> We have already been publishing to npm under the RC tag for
> > >> >> testing
> > >> (not
> > >> >> releasing to public but just for dev testing).
> > >> >>
> > >> >> The last few releases you could go npm install cordova@rc and that
> > >> would
> > >> >> download the RC version of cordova that we were voting on.
> > >> >>
> > >> >> I went ahead and published all of the platforms + lib + plugman +
> > >> >> js (everything we are voting on) to npm under an rc tag. So npm
> > >> >> install cordova-android@rc would grab version 3.6.0.
> > >> >>
> > >> >> The easiest way to test is to now go npm install cordova@rc. No
> > >> >> need
> > >> to
> > >> >> --usegit anymore.
> > >> >>
> > >> >> The --usegit method would require you to checkout the tags in
> > >> cordova-lib,
> > >> >> cordova-js, npm link them, go to cli, npm link them, etc.
> > >> >>
> > >> >> -Steve
> > >> >>
> > >> >>
> > >> >> On Tue, Sep 2, 2014 at 10:23 AM, Parashuram Narasimhan (MS OPEN
> > >> >> TECH) < panarasi@microsoft.com> wrote:
> > >> >>
> > >> >> > Agree with Jesse. If you still want to test it, I tried doing it
> > >> with a
> > >> >> > private npm registry, and changed my npm to pick up from that
> > >> registry.
> > >> >> I
> > >> >> > did not see a lot of value added though. I did this when I was
> > >> playing
> > >> >> with
> > >> >> > the idea of using npm to use plugins.
> > >> >> >
> > >> >> > -----Original Message-----
> > >> >> > From: Jesse [mailto:purplecabbage@gmail.com]
> > >> >> > Sent: Tuesday, September 2, 2014 10:21 AM
> > >> >> > To: dev@cordova.apache.org
> > >> >> > Subject: Re: [Vote] 3.6.0 Cadence Release
> > >> >> >
> > >> >> > We cannot post to npm without the vote passing. There is a bunch
> > >> >> > of
> > >> >> crazy
> > >> >> > overhead tag bs we could do, but then we would not be voting on
> > >> >> > the
> > >> >> final
> > >> >> > released binaries.
> > >> >> >
> > >> >> > Just test with --usegit
> > >> >> >
> > >> >> >
> > >> >> >
> > >> >> > @purplecabbage
> > >> >> > risingj.com
> > >> >> >
> > >> >> >
> > >> >> > On Tue, Sep 2, 2014 at 6:47 AM, Carlos Santana
> > >> >> > <csantana23@gmail.com
> > >> >
> > >> >> > wrote:
> > >> >> >
> > >> >> > > I see cordova cli rc on npm, I want to test it using npm but I
> > >> >> > > get
> > >> >> > errors.
> > >> >> > > Maybe cordova-lib should be also posted to npm but not make it
> > >> latest
> > >> >> > > until we release.
> > >> >> > >
> > >> >> > > I get this errors:
> > >> >> > >
> > >> >> > > $ npm install cordova@rc
> > >> >> > >
> > >> >> > > npm ERR! Error: version not found: cordova-lib@0.21.8
> > >> >> > >
> > >> >> > >
> > >> >> > > On Tue, Sep 2, 2014 at 9:29 AM, Bryan Higgins <
> > >> bryan@bryanhiggins.net
> > >> >> >
> > >> >> > > wrote:
> > >> >> > >
> > >> >> > > > +1
> > >> >> > > >
> > >> >> > > > - Verified signatures and hashes for cordova-blackberry
> > >> >> > > > - Verified sha1 match tag 3.6.0
> > >> >> > > > - Ran mobile spec on various BB10 devices and OS versions
> > >> >> > > >
> > >> >> > > > Steve - I added you as an owner for cordova-blackberry10 on
> > npm.
> > >> The
> > >> >> > > > cordova-blackberry package should probably be unpublished.
> > >> >> > > >
> > >> >> > > >
> > >> >> > > > On Tue, Sep 2, 2014 at 1:15 AM, Archana Naik
> > >> >> > > > <na...@gmail.com>
> > >> >> > > > wrote:
> > >> >> > > >
> > >> >> > > > > vote +1
> > >> >> > > > > Verified amazon-fireos bundle, signatures and hashes.
> > >> >> > > > >
> > >> >> > > > > When are we planning to publish it to npm?
> > >> >> > > > >
> > >> >> > > > >
> > >> >> > > > > On Mon, Sep 1, 2014 at 2:40 PM, Sergey Grebnov (Akvelon) <
> > >> >> > > > > v-segreb@microsoft.com> wrote:
> > >> >> > > > >
> > >> >> > > > > > I vote +1:
> > >> >> > > > > > * Verified signatures and hashes for cordova-cli,
> > >> cordova-lib,
> > >> >> > > > > > cordova-plugman, cordova-windows, cordova-wp8
> > >> >> > > > > > * Verified sha1s match tags for cordova-cli,
> > >> >> > > > > > cordova-lib,
> > >> >> > > > > cordova-plugman,
> > >> >> > > > > > cordova-windows, cordova-wp8
> > >> >> > > > > > * Run Medic tests for Windows and Windows Phone 8
> > >> >> > > > > > * Tested Android build on Windows
> > >> >> > > > > > * Tested Windows platform manually
> > >> >> > > > > > building and running app with VS2012 (msbuild
> > >> >> > > > > > 4.0)/VS2013(msbuild
> > >> >> > > > > 12.0)
> > >> >> > > > > > -win and -phone switches
> > >> >> > > > > > support of target platform settings (config.xml)
> > >> >> > > > > > support of custom icons and splash screen images
> > >> >> > > > > >
> > >> >> > > > > > Thx!
> > >> >> > > > > > Sergey
> > >> >> > > > > > -----Original Message-----
> > >> >> > > > > > From: Steven Gill [mailto:stevengill97@gmail.com]
> > >> >> > > > > > Sent: Saturday, August 30, 2014 5:35 AM
> > >> >> > > > > > To: dev@cordova.apache.org
> > >> >> > > > > > Subject: [Vote] 3.6.0 Cadence Release
> > >> >> > > > > >
> > >> >> > > > > > Please review and vote on this 3.6.0 Cadence Release.
> > >> >> > > > > >
> > >> >> > > > > > Release issue:
> > >> >> > > > > > https://issues.apache.org/jira/browse/CB-7383
> > >> >> > > > > >
> > >> >> > > > > > Repos ready to be released have been published to
> > >> >> > > > > > dist/dev:
> > >> https://dist.apache.org/repos/dist/dev/cordova/CB-7383
> > >> >> > > > > >
> > >> >> > > > > > The packages were published from their corresponding git
> > >> tags:
> > >> >> > > > > > cordova-android: 3.6.0 (014327c59a)
> > >> >> > > > > > cordova-ios: 3.6.0 (3a92b2dbf0)
> > >> >> > > > > > cordova-blackberry: 3.6.0 (ed435bfc9e)
> > >> >> > > > > > cordova-windows: 3.6.0 (cdb292f4a3)
> > >> >> > > > > > cordova-wp8: 3.6.0 (a879f5258b)
> > >> >> > > > > > cordova-firefoxos: 3.6.0 (9ab176f855)
> > >> >> > > > > >
> > >> >> > > > > > cordova-ubuntu: 3.6.0 (bff472e4c2)
> > >> >> > > > > > cordova-amazon-fireos: 3.6.0 (4e94c6d198)
> > >> >> > > > > > cordova-js: 3.6.0 (906b34c0a4)
> > >> >> > > > > > cordova-mobile-spec: 3.6.0 (27053f7dd8)
> > >> >> > > > > > cordova-app-hello-world: 3.6.0 (65a2171a19)
> > >> >> > > > > >
> > >> >> > > > > > cordova-cli: 3.6.0-0.2.8 (01cb09f2d1)
> > >> >> > > > > > cordova-lib: 0.21.8 (14670ec9b5)
> > >> >> > > > > > cordova-plugman: 0.22.5 (29488fce7e)
> > >> >> > > > > >
> > >> >> > > > > >
> > >> >> > > > > > Upon a successful vote I will upload the archives to
> > >> >> > > > > > dist/, publish
> > >> >> > > > them
> > >> >> > > > > > to NPM, and post the corresponding blog post.
> > >> >> > > > > >
> > >> >> > > > > > Voting guidelines:
> > >> >> > > > > >
> > >> >> > > > >
> > >> >> > > >
> > >> >> > >
> > >> >> https://github.com/apache/cordova-coho/blob/master/docs/release-vo
> > >> >> ting
> > >> >> > > .md
> > >> >> > > > > >
> > >> >> > > > > > Voting will go on for a minimum of 72 hours.
> > >> >> > > > > >
> > >> >> > > > > > I vote +1:
> > >> >> > > > > > * Ran coho audit-license-headers over the relevant repos
> > >> >> > > > > > * Used `license-checker` to ensure all dependencies have
> > >> >> > > > > Apache-compatible
> > >> >> > > > > > licenses
> > >> >> > > > > > * Ensured continuous build was green when repos were
> > >> >> > > > > > tagged
> > >> >> > > > > >
> > >> >> > > > >
> > >> >> > > >
> > >> >> > >
> > >> >> > >
> > >> >> > >
> > >> >> > > --
> > >> >> > > Carlos Santana
> > >> >> > > <cs...@gmail.com>
> > >> >> > >
> > >> >> >
> > >> >>
> > >> >
> > >> >
> > >>
> > >
> > >
> >
>
Re: [Vote] 3.6.0 Cadence Release
Posted by Steven Gill <st...@gmail.com>.
I will get the blog post + updated dists ready and start the vote thread.
Someone else will have to close the vote thread + publish packages & blog
post.
Any volunteers for that? Jesse? I need to add whoever it is to all of the
npm repos.
On Tue, Sep 2, 2014 at 11:58 AM, Sergey Grebnov (Akvelon) <
v-segreb@microsoft.com> wrote:
> If we restart the thread, will we be able to complete it before Steven
> gone on vacation or someone else will be able to accomplish this?
>
> Thx!
> Sergey
> -----Original Message-----
> From: Steven Gill [mailto:stevengill97@gmail.com]
> Sent: Tuesday, September 2, 2014 9:57 PM
> To: dev@cordova.apache.org
> Cc: Michal Mocny
> Subject: Re: [Vote] 3.6.0 Cadence Release
>
> Another mistake I found, wp8's package.json was set to 3.6.0-dev on the
> 3.6.x branch. I had to update that to publish to npm under rc tag.
>
> This vote is going to need to get restarted, but I suggest we continue to
> test what is uploaded to see if any more fixes are needed.
>
>
> On Tue, Sep 2, 2014 at 10:54 AM, Steven Gill <st...@gmail.com>
> wrote:
>
> > Looks like CLI VERSION file is incorrect :( Didn't get updated. Also
> > looks like the zip i uploaded for the CLI got generated incorrectly.
> > Need to take a deeper look.
> >
> > I don't see cordova-js 3.6.0-dev Version file anywhere.
> >
> > I'm also running into an issue with firefoxos testing. Looks like it
> > can't find shelljs module.
> >
> >
> >
> > On Tue, Sep 2, 2014 at 10:47 AM, Michal Mocny <mm...@chromium.org>
> wrote:
> >
> >> .. Looks like cordova-cli still has a VERSION file set to
> >> 3.5.0-0.2.4. Is it even used?
> >>
> >> .. and cordova-cli deps on cordova-lib which deps on cordova-js which
> >> has VERSION file set to 3.6.0-dev.
> >>
> >>
> >> On Tue, Sep 2, 2014 at 1:42 PM, Michal Mocny <mm...@chromium.org>
> wrote:
> >>
> >> > We could ask Apache folk for clarification, but if I understand the
> >> > requirements for release process correct, I think publishing an rc
> >> > and voting on it would be totally acceptable provided that:
> >> >
> >> > (a) *exactly* the tarball that went up to RC is used as the final
> >> release,
> >> > so that signatures match. At the very least I think that would
> >> > mean to leaving the "-rc#" portion out of all the "version" key
> >> > (and any VERSION files).
> >> > (b) We don't advertise to users that this is a release they should
> >> consume.
> >> >
> >> > It looks like Steven has done this.
> >> >
> >> > -Michal
> >> >
> >> >
> >> > On Tue, Sep 2, 2014 at 1:26 PM, Steven Gill
> >> > <st...@gmail.com>
> >> > wrote:
> >> >
> >> >> Actually, I like Carlos suggestion.
> >> >>
> >> >> We have already been publishing to npm under the RC tag for
> >> >> testing
> >> (not
> >> >> releasing to public but just for dev testing).
> >> >>
> >> >> The last few releases you could go npm install cordova@rc and that
> >> would
> >> >> download the RC version of cordova that we were voting on.
> >> >>
> >> >> I went ahead and published all of the platforms + lib + plugman +
> >> >> js (everything we are voting on) to npm under an rc tag. So npm
> >> >> install cordova-android@rc would grab version 3.6.0.
> >> >>
> >> >> The easiest way to test is to now go npm install cordova@rc. No
> >> >> need
> >> to
> >> >> --usegit anymore.
> >> >>
> >> >> The --usegit method would require you to checkout the tags in
> >> cordova-lib,
> >> >> cordova-js, npm link them, go to cli, npm link them, etc.
> >> >>
> >> >> -Steve
> >> >>
> >> >>
> >> >> On Tue, Sep 2, 2014 at 10:23 AM, Parashuram Narasimhan (MS OPEN
> >> >> TECH) < panarasi@microsoft.com> wrote:
> >> >>
> >> >> > Agree with Jesse. If you still want to test it, I tried doing it
> >> with a
> >> >> > private npm registry, and changed my npm to pick up from that
> >> registry.
> >> >> I
> >> >> > did not see a lot of value added though. I did this when I was
> >> playing
> >> >> with
> >> >> > the idea of using npm to use plugins.
> >> >> >
> >> >> > -----Original Message-----
> >> >> > From: Jesse [mailto:purplecabbage@gmail.com]
> >> >> > Sent: Tuesday, September 2, 2014 10:21 AM
> >> >> > To: dev@cordova.apache.org
> >> >> > Subject: Re: [Vote] 3.6.0 Cadence Release
> >> >> >
> >> >> > We cannot post to npm without the vote passing. There is a bunch
> >> >> > of
> >> >> crazy
> >> >> > overhead tag bs we could do, but then we would not be voting on
> >> >> > the
> >> >> final
> >> >> > released binaries.
> >> >> >
> >> >> > Just test with --usegit
> >> >> >
> >> >> >
> >> >> >
> >> >> > @purplecabbage
> >> >> > risingj.com
> >> >> >
> >> >> >
> >> >> > On Tue, Sep 2, 2014 at 6:47 AM, Carlos Santana
> >> >> > <csantana23@gmail.com
> >> >
> >> >> > wrote:
> >> >> >
> >> >> > > I see cordova cli rc on npm, I want to test it using npm but I
> >> >> > > get
> >> >> > errors.
> >> >> > > Maybe cordova-lib should be also posted to npm but not make it
> >> latest
> >> >> > > until we release.
> >> >> > >
> >> >> > > I get this errors:
> >> >> > >
> >> >> > > $ npm install cordova@rc
> >> >> > >
> >> >> > > npm ERR! Error: version not found: cordova-lib@0.21.8
> >> >> > >
> >> >> > >
> >> >> > > On Tue, Sep 2, 2014 at 9:29 AM, Bryan Higgins <
> >> bryan@bryanhiggins.net
> >> >> >
> >> >> > > wrote:
> >> >> > >
> >> >> > > > +1
> >> >> > > >
> >> >> > > > - Verified signatures and hashes for cordova-blackberry
> >> >> > > > - Verified sha1 match tag 3.6.0
> >> >> > > > - Ran mobile spec on various BB10 devices and OS versions
> >> >> > > >
> >> >> > > > Steve - I added you as an owner for cordova-blackberry10 on
> npm.
> >> The
> >> >> > > > cordova-blackberry package should probably be unpublished.
> >> >> > > >
> >> >> > > >
> >> >> > > > On Tue, Sep 2, 2014 at 1:15 AM, Archana Naik
> >> >> > > > <na...@gmail.com>
> >> >> > > > wrote:
> >> >> > > >
> >> >> > > > > vote +1
> >> >> > > > > Verified amazon-fireos bundle, signatures and hashes.
> >> >> > > > >
> >> >> > > > > When are we planning to publish it to npm?
> >> >> > > > >
> >> >> > > > >
> >> >> > > > > On Mon, Sep 1, 2014 at 2:40 PM, Sergey Grebnov (Akvelon) <
> >> >> > > > > v-segreb@microsoft.com> wrote:
> >> >> > > > >
> >> >> > > > > > I vote +1:
> >> >> > > > > > * Verified signatures and hashes for cordova-cli,
> >> cordova-lib,
> >> >> > > > > > cordova-plugman, cordova-windows, cordova-wp8
> >> >> > > > > > * Verified sha1s match tags for cordova-cli,
> >> >> > > > > > cordova-lib,
> >> >> > > > > cordova-plugman,
> >> >> > > > > > cordova-windows, cordova-wp8
> >> >> > > > > > * Run Medic tests for Windows and Windows Phone 8
> >> >> > > > > > * Tested Android build on Windows
> >> >> > > > > > * Tested Windows platform manually
> >> >> > > > > > building and running app with VS2012 (msbuild
> >> >> > > > > > 4.0)/VS2013(msbuild
> >> >> > > > > 12.0)
> >> >> > > > > > -win and -phone switches
> >> >> > > > > > support of target platform settings (config.xml)
> >> >> > > > > > support of custom icons and splash screen images
> >> >> > > > > >
> >> >> > > > > > Thx!
> >> >> > > > > > Sergey
> >> >> > > > > > -----Original Message-----
> >> >> > > > > > From: Steven Gill [mailto:stevengill97@gmail.com]
> >> >> > > > > > Sent: Saturday, August 30, 2014 5:35 AM
> >> >> > > > > > To: dev@cordova.apache.org
> >> >> > > > > > Subject: [Vote] 3.6.0 Cadence Release
> >> >> > > > > >
> >> >> > > > > > Please review and vote on this 3.6.0 Cadence Release.
> >> >> > > > > >
> >> >> > > > > > Release issue:
> >> >> > > > > > https://issues.apache.org/jira/browse/CB-7383
> >> >> > > > > >
> >> >> > > > > > Repos ready to be released have been published to
> >> >> > > > > > dist/dev:
> >> https://dist.apache.org/repos/dist/dev/cordova/CB-7383
> >> >> > > > > >
> >> >> > > > > > The packages were published from their corresponding git
> >> tags:
> >> >> > > > > > cordova-android: 3.6.0 (014327c59a)
> >> >> > > > > > cordova-ios: 3.6.0 (3a92b2dbf0)
> >> >> > > > > > cordova-blackberry: 3.6.0 (ed435bfc9e)
> >> >> > > > > > cordova-windows: 3.6.0 (cdb292f4a3)
> >> >> > > > > > cordova-wp8: 3.6.0 (a879f5258b)
> >> >> > > > > > cordova-firefoxos: 3.6.0 (9ab176f855)
> >> >> > > > > >
> >> >> > > > > > cordova-ubuntu: 3.6.0 (bff472e4c2)
> >> >> > > > > > cordova-amazon-fireos: 3.6.0 (4e94c6d198)
> >> >> > > > > > cordova-js: 3.6.0 (906b34c0a4)
> >> >> > > > > > cordova-mobile-spec: 3.6.0 (27053f7dd8)
> >> >> > > > > > cordova-app-hello-world: 3.6.0 (65a2171a19)
> >> >> > > > > >
> >> >> > > > > > cordova-cli: 3.6.0-0.2.8 (01cb09f2d1)
> >> >> > > > > > cordova-lib: 0.21.8 (14670ec9b5)
> >> >> > > > > > cordova-plugman: 0.22.5 (29488fce7e)
> >> >> > > > > >
> >> >> > > > > >
> >> >> > > > > > Upon a successful vote I will upload the archives to
> >> >> > > > > > dist/, publish
> >> >> > > > them
> >> >> > > > > > to NPM, and post the corresponding blog post.
> >> >> > > > > >
> >> >> > > > > > Voting guidelines:
> >> >> > > > > >
> >> >> > > > >
> >> >> > > >
> >> >> > >
> >> >> https://github.com/apache/cordova-coho/blob/master/docs/release-vo
> >> >> ting
> >> >> > > .md
> >> >> > > > > >
> >> >> > > > > > Voting will go on for a minimum of 72 hours.
> >> >> > > > > >
> >> >> > > > > > I vote +1:
> >> >> > > > > > * Ran coho audit-license-headers over the relevant repos
> >> >> > > > > > * Used `license-checker` to ensure all dependencies have
> >> >> > > > > Apache-compatible
> >> >> > > > > > licenses
> >> >> > > > > > * Ensured continuous build was green when repos were
> >> >> > > > > > tagged
> >> >> > > > > >
> >> >> > > > >
> >> >> > > >
> >> >> > >
> >> >> > >
> >> >> > >
> >> >> > > --
> >> >> > > Carlos Santana
> >> >> > > <cs...@gmail.com>
> >> >> > >
> >> >> >
> >> >>
> >> >
> >> >
> >>
> >
> >
>
RE: [Vote] 3.6.0 Cadence Release
Posted by "Sergey Grebnov (Akvelon)" <v-...@microsoft.com>.
If we restart the thread, will we be able to complete it before Steven gone on vacation or someone else will be able to accomplish this?
Thx!
Sergey
-----Original Message-----
From: Steven Gill [mailto:stevengill97@gmail.com]
Sent: Tuesday, September 2, 2014 9:57 PM
To: dev@cordova.apache.org
Cc: Michal Mocny
Subject: Re: [Vote] 3.6.0 Cadence Release
Another mistake I found, wp8's package.json was set to 3.6.0-dev on the 3.6.x branch. I had to update that to publish to npm under rc tag.
This vote is going to need to get restarted, but I suggest we continue to test what is uploaded to see if any more fixes are needed.
On Tue, Sep 2, 2014 at 10:54 AM, Steven Gill <st...@gmail.com> wrote:
> Looks like CLI VERSION file is incorrect :( Didn't get updated. Also
> looks like the zip i uploaded for the CLI got generated incorrectly.
> Need to take a deeper look.
>
> I don't see cordova-js 3.6.0-dev Version file anywhere.
>
> I'm also running into an issue with firefoxos testing. Looks like it
> can't find shelljs module.
>
>
>
> On Tue, Sep 2, 2014 at 10:47 AM, Michal Mocny <mm...@chromium.org> wrote:
>
>> .. Looks like cordova-cli still has a VERSION file set to
>> 3.5.0-0.2.4. Is it even used?
>>
>> .. and cordova-cli deps on cordova-lib which deps on cordova-js which
>> has VERSION file set to 3.6.0-dev.
>>
>>
>> On Tue, Sep 2, 2014 at 1:42 PM, Michal Mocny <mm...@chromium.org> wrote:
>>
>> > We could ask Apache folk for clarification, but if I understand the
>> > requirements for release process correct, I think publishing an rc
>> > and voting on it would be totally acceptable provided that:
>> >
>> > (a) *exactly* the tarball that went up to RC is used as the final
>> release,
>> > so that signatures match. At the very least I think that would
>> > mean to leaving the "-rc#" portion out of all the "version" key
>> > (and any VERSION files).
>> > (b) We don't advertise to users that this is a release they should
>> consume.
>> >
>> > It looks like Steven has done this.
>> >
>> > -Michal
>> >
>> >
>> > On Tue, Sep 2, 2014 at 1:26 PM, Steven Gill
>> > <st...@gmail.com>
>> > wrote:
>> >
>> >> Actually, I like Carlos suggestion.
>> >>
>> >> We have already been publishing to npm under the RC tag for
>> >> testing
>> (not
>> >> releasing to public but just for dev testing).
>> >>
>> >> The last few releases you could go npm install cordova@rc and that
>> would
>> >> download the RC version of cordova that we were voting on.
>> >>
>> >> I went ahead and published all of the platforms + lib + plugman +
>> >> js (everything we are voting on) to npm under an rc tag. So npm
>> >> install cordova-android@rc would grab version 3.6.0.
>> >>
>> >> The easiest way to test is to now go npm install cordova@rc. No
>> >> need
>> to
>> >> --usegit anymore.
>> >>
>> >> The --usegit method would require you to checkout the tags in
>> cordova-lib,
>> >> cordova-js, npm link them, go to cli, npm link them, etc.
>> >>
>> >> -Steve
>> >>
>> >>
>> >> On Tue, Sep 2, 2014 at 10:23 AM, Parashuram Narasimhan (MS OPEN
>> >> TECH) < panarasi@microsoft.com> wrote:
>> >>
>> >> > Agree with Jesse. If you still want to test it, I tried doing it
>> with a
>> >> > private npm registry, and changed my npm to pick up from that
>> registry.
>> >> I
>> >> > did not see a lot of value added though. I did this when I was
>> playing
>> >> with
>> >> > the idea of using npm to use plugins.
>> >> >
>> >> > -----Original Message-----
>> >> > From: Jesse [mailto:purplecabbage@gmail.com]
>> >> > Sent: Tuesday, September 2, 2014 10:21 AM
>> >> > To: dev@cordova.apache.org
>> >> > Subject: Re: [Vote] 3.6.0 Cadence Release
>> >> >
>> >> > We cannot post to npm without the vote passing. There is a bunch
>> >> > of
>> >> crazy
>> >> > overhead tag bs we could do, but then we would not be voting on
>> >> > the
>> >> final
>> >> > released binaries.
>> >> >
>> >> > Just test with --usegit
>> >> >
>> >> >
>> >> >
>> >> > @purplecabbage
>> >> > risingj.com
>> >> >
>> >> >
>> >> > On Tue, Sep 2, 2014 at 6:47 AM, Carlos Santana
>> >> > <csantana23@gmail.com
>> >
>> >> > wrote:
>> >> >
>> >> > > I see cordova cli rc on npm, I want to test it using npm but I
>> >> > > get
>> >> > errors.
>> >> > > Maybe cordova-lib should be also posted to npm but not make it
>> latest
>> >> > > until we release.
>> >> > >
>> >> > > I get this errors:
>> >> > >
>> >> > > $ npm install cordova@rc
>> >> > >
>> >> > > npm ERR! Error: version not found: cordova-lib@0.21.8
>> >> > >
>> >> > >
>> >> > > On Tue, Sep 2, 2014 at 9:29 AM, Bryan Higgins <
>> bryan@bryanhiggins.net
>> >> >
>> >> > > wrote:
>> >> > >
>> >> > > > +1
>> >> > > >
>> >> > > > - Verified signatures and hashes for cordova-blackberry
>> >> > > > - Verified sha1 match tag 3.6.0
>> >> > > > - Ran mobile spec on various BB10 devices and OS versions
>> >> > > >
>> >> > > > Steve - I added you as an owner for cordova-blackberry10 on npm.
>> The
>> >> > > > cordova-blackberry package should probably be unpublished.
>> >> > > >
>> >> > > >
>> >> > > > On Tue, Sep 2, 2014 at 1:15 AM, Archana Naik
>> >> > > > <na...@gmail.com>
>> >> > > > wrote:
>> >> > > >
>> >> > > > > vote +1
>> >> > > > > Verified amazon-fireos bundle, signatures and hashes.
>> >> > > > >
>> >> > > > > When are we planning to publish it to npm?
>> >> > > > >
>> >> > > > >
>> >> > > > > On Mon, Sep 1, 2014 at 2:40 PM, Sergey Grebnov (Akvelon) <
>> >> > > > > v-segreb@microsoft.com> wrote:
>> >> > > > >
>> >> > > > > > I vote +1:
>> >> > > > > > * Verified signatures and hashes for cordova-cli,
>> cordova-lib,
>> >> > > > > > cordova-plugman, cordova-windows, cordova-wp8
>> >> > > > > > * Verified sha1s match tags for cordova-cli,
>> >> > > > > > cordova-lib,
>> >> > > > > cordova-plugman,
>> >> > > > > > cordova-windows, cordova-wp8
>> >> > > > > > * Run Medic tests for Windows and Windows Phone 8
>> >> > > > > > * Tested Android build on Windows
>> >> > > > > > * Tested Windows platform manually
>> >> > > > > > building and running app with VS2012 (msbuild
>> >> > > > > > 4.0)/VS2013(msbuild
>> >> > > > > 12.0)
>> >> > > > > > -win and -phone switches
>> >> > > > > > support of target platform settings (config.xml)
>> >> > > > > > support of custom icons and splash screen images
>> >> > > > > >
>> >> > > > > > Thx!
>> >> > > > > > Sergey
>> >> > > > > > -----Original Message-----
>> >> > > > > > From: Steven Gill [mailto:stevengill97@gmail.com]
>> >> > > > > > Sent: Saturday, August 30, 2014 5:35 AM
>> >> > > > > > To: dev@cordova.apache.org
>> >> > > > > > Subject: [Vote] 3.6.0 Cadence Release
>> >> > > > > >
>> >> > > > > > Please review and vote on this 3.6.0 Cadence Release.
>> >> > > > > >
>> >> > > > > > Release issue:
>> >> > > > > > https://issues.apache.org/jira/browse/CB-7383
>> >> > > > > >
>> >> > > > > > Repos ready to be released have been published to
>> >> > > > > > dist/dev:
>> https://dist.apache.org/repos/dist/dev/cordova/CB-7383
>> >> > > > > >
>> >> > > > > > The packages were published from their corresponding git
>> tags:
>> >> > > > > > cordova-android: 3.6.0 (014327c59a)
>> >> > > > > > cordova-ios: 3.6.0 (3a92b2dbf0)
>> >> > > > > > cordova-blackberry: 3.6.0 (ed435bfc9e)
>> >> > > > > > cordova-windows: 3.6.0 (cdb292f4a3)
>> >> > > > > > cordova-wp8: 3.6.0 (a879f5258b)
>> >> > > > > > cordova-firefoxos: 3.6.0 (9ab176f855)
>> >> > > > > >
>> >> > > > > > cordova-ubuntu: 3.6.0 (bff472e4c2)
>> >> > > > > > cordova-amazon-fireos: 3.6.0 (4e94c6d198)
>> >> > > > > > cordova-js: 3.6.0 (906b34c0a4)
>> >> > > > > > cordova-mobile-spec: 3.6.0 (27053f7dd8)
>> >> > > > > > cordova-app-hello-world: 3.6.0 (65a2171a19)
>> >> > > > > >
>> >> > > > > > cordova-cli: 3.6.0-0.2.8 (01cb09f2d1)
>> >> > > > > > cordova-lib: 0.21.8 (14670ec9b5)
>> >> > > > > > cordova-plugman: 0.22.5 (29488fce7e)
>> >> > > > > >
>> >> > > > > >
>> >> > > > > > Upon a successful vote I will upload the archives to
>> >> > > > > > dist/, publish
>> >> > > > them
>> >> > > > > > to NPM, and post the corresponding blog post.
>> >> > > > > >
>> >> > > > > > Voting guidelines:
>> >> > > > > >
>> >> > > > >
>> >> > > >
>> >> > >
>> >> https://github.com/apache/cordova-coho/blob/master/docs/release-vo
>> >> ting
>> >> > > .md
>> >> > > > > >
>> >> > > > > > Voting will go on for a minimum of 72 hours.
>> >> > > > > >
>> >> > > > > > I vote +1:
>> >> > > > > > * Ran coho audit-license-headers over the relevant repos
>> >> > > > > > * Used `license-checker` to ensure all dependencies have
>> >> > > > > Apache-compatible
>> >> > > > > > licenses
>> >> > > > > > * Ensured continuous build was green when repos were
>> >> > > > > > tagged
>> >> > > > > >
>> >> > > > >
>> >> > > >
>> >> > >
>> >> > >
>> >> > >
>> >> > > --
>> >> > > Carlos Santana
>> >> > > <cs...@gmail.com>
>> >> > >
>> >> >
>> >>
>> >
>> >
>>
>
>
Re: [Vote] 3.6.0 Cadence Release
Posted by Steven Gill <st...@gmail.com>.
Another mistake I found, wp8's package.json was set to 3.6.0-dev on the
3.6.x branch. I had to update that to publish to npm under rc tag.
This vote is going to need to get restarted, but I suggest we continue to
test what is uploaded to see if any more fixes are needed.
On Tue, Sep 2, 2014 at 10:54 AM, Steven Gill <st...@gmail.com> wrote:
> Looks like CLI VERSION file is incorrect :( Didn't get updated. Also looks
> like the zip i uploaded for the CLI got generated incorrectly. Need to take
> a deeper look.
>
> I don't see cordova-js 3.6.0-dev Version file anywhere.
>
> I'm also running into an issue with firefoxos testing. Looks like it can't
> find shelljs module.
>
>
>
> On Tue, Sep 2, 2014 at 10:47 AM, Michal Mocny <mm...@chromium.org> wrote:
>
>> .. Looks like cordova-cli still has a VERSION file set to 3.5.0-0.2.4. Is
>> it even used?
>>
>> .. and cordova-cli deps on cordova-lib which deps on cordova-js which has
>> VERSION file set to 3.6.0-dev.
>>
>>
>> On Tue, Sep 2, 2014 at 1:42 PM, Michal Mocny <mm...@chromium.org> wrote:
>>
>> > We could ask Apache folk for clarification, but if I understand the
>> > requirements for release process correct, I think publishing an rc and
>> > voting on it would be totally acceptable provided that:
>> >
>> > (a) *exactly* the tarball that went up to RC is used as the final
>> release,
>> > so that signatures match. At the very least I think that would mean to
>> > leaving the "-rc#" portion out of all the "version" key (and any VERSION
>> > files).
>> > (b) We don't advertise to users that this is a release they should
>> consume.
>> >
>> > It looks like Steven has done this.
>> >
>> > -Michal
>> >
>> >
>> > On Tue, Sep 2, 2014 at 1:26 PM, Steven Gill <st...@gmail.com>
>> > wrote:
>> >
>> >> Actually, I like Carlos suggestion.
>> >>
>> >> We have already been publishing to npm under the RC tag for testing
>> (not
>> >> releasing to public but just for dev testing).
>> >>
>> >> The last few releases you could go npm install cordova@rc and that
>> would
>> >> download the RC version of cordova that we were voting on.
>> >>
>> >> I went ahead and published all of the platforms + lib + plugman + js
>> >> (everything we are voting on) to npm under an rc tag. So npm install
>> >> cordova-android@rc would grab version 3.6.0.
>> >>
>> >> The easiest way to test is to now go npm install cordova@rc. No need
>> to
>> >> --usegit anymore.
>> >>
>> >> The --usegit method would require you to checkout the tags in
>> cordova-lib,
>> >> cordova-js, npm link them, go to cli, npm link them, etc.
>> >>
>> >> -Steve
>> >>
>> >>
>> >> On Tue, Sep 2, 2014 at 10:23 AM, Parashuram Narasimhan (MS OPEN TECH) <
>> >> panarasi@microsoft.com> wrote:
>> >>
>> >> > Agree with Jesse. If you still want to test it, I tried doing it
>> with a
>> >> > private npm registry, and changed my npm to pick up from that
>> registry.
>> >> I
>> >> > did not see a lot of value added though. I did this when I was
>> playing
>> >> with
>> >> > the idea of using npm to use plugins.
>> >> >
>> >> > -----Original Message-----
>> >> > From: Jesse [mailto:purplecabbage@gmail.com]
>> >> > Sent: Tuesday, September 2, 2014 10:21 AM
>> >> > To: dev@cordova.apache.org
>> >> > Subject: Re: [Vote] 3.6.0 Cadence Release
>> >> >
>> >> > We cannot post to npm without the vote passing. There is a bunch of
>> >> crazy
>> >> > overhead tag bs we could do, but then we would not be voting on the
>> >> final
>> >> > released binaries.
>> >> >
>> >> > Just test with --usegit
>> >> >
>> >> >
>> >> >
>> >> > @purplecabbage
>> >> > risingj.com
>> >> >
>> >> >
>> >> > On Tue, Sep 2, 2014 at 6:47 AM, Carlos Santana <csantana23@gmail.com
>> >
>> >> > wrote:
>> >> >
>> >> > > I see cordova cli rc on npm, I want to test it using npm but I get
>> >> > errors.
>> >> > > Maybe cordova-lib should be also posted to npm but not make it
>> latest
>> >> > > until we release.
>> >> > >
>> >> > > I get this errors:
>> >> > >
>> >> > > $ npm install cordova@rc
>> >> > >
>> >> > > npm ERR! Error: version not found: cordova-lib@0.21.8
>> >> > >
>> >> > >
>> >> > > On Tue, Sep 2, 2014 at 9:29 AM, Bryan Higgins <
>> bryan@bryanhiggins.net
>> >> >
>> >> > > wrote:
>> >> > >
>> >> > > > +1
>> >> > > >
>> >> > > > - Verified signatures and hashes for cordova-blackberry
>> >> > > > - Verified sha1 match tag 3.6.0
>> >> > > > - Ran mobile spec on various BB10 devices and OS versions
>> >> > > >
>> >> > > > Steve - I added you as an owner for cordova-blackberry10 on npm.
>> The
>> >> > > > cordova-blackberry package should probably be unpublished.
>> >> > > >
>> >> > > >
>> >> > > > On Tue, Sep 2, 2014 at 1:15 AM, Archana Naik
>> >> > > > <na...@gmail.com>
>> >> > > > wrote:
>> >> > > >
>> >> > > > > vote +1
>> >> > > > > Verified amazon-fireos bundle, signatures and hashes.
>> >> > > > >
>> >> > > > > When are we planning to publish it to npm?
>> >> > > > >
>> >> > > > >
>> >> > > > > On Mon, Sep 1, 2014 at 2:40 PM, Sergey Grebnov (Akvelon) <
>> >> > > > > v-segreb@microsoft.com> wrote:
>> >> > > > >
>> >> > > > > > I vote +1:
>> >> > > > > > * Verified signatures and hashes for cordova-cli,
>> cordova-lib,
>> >> > > > > > cordova-plugman, cordova-windows, cordova-wp8
>> >> > > > > > * Verified sha1s match tags for cordova-cli, cordova-lib,
>> >> > > > > cordova-plugman,
>> >> > > > > > cordova-windows, cordova-wp8
>> >> > > > > > * Run Medic tests for Windows and Windows Phone 8
>> >> > > > > > * Tested Android build on Windows
>> >> > > > > > * Tested Windows platform manually
>> >> > > > > > building and running app with VS2012 (msbuild
>> >> > > > > > 4.0)/VS2013(msbuild
>> >> > > > > 12.0)
>> >> > > > > > -win and -phone switches
>> >> > > > > > support of target platform settings (config.xml)
>> >> > > > > > support of custom icons and splash screen images
>> >> > > > > >
>> >> > > > > > Thx!
>> >> > > > > > Sergey
>> >> > > > > > -----Original Message-----
>> >> > > > > > From: Steven Gill [mailto:stevengill97@gmail.com]
>> >> > > > > > Sent: Saturday, August 30, 2014 5:35 AM
>> >> > > > > > To: dev@cordova.apache.org
>> >> > > > > > Subject: [Vote] 3.6.0 Cadence Release
>> >> > > > > >
>> >> > > > > > Please review and vote on this 3.6.0 Cadence Release.
>> >> > > > > >
>> >> > > > > > Release issue: https://issues.apache.org/jira/browse/CB-7383
>> >> > > > > >
>> >> > > > > > Repos ready to be released have been published to
>> >> > > > > > dist/dev:
>> https://dist.apache.org/repos/dist/dev/cordova/CB-7383
>> >> > > > > >
>> >> > > > > > The packages were published from their corresponding git
>> tags:
>> >> > > > > > cordova-android: 3.6.0 (014327c59a)
>> >> > > > > > cordova-ios: 3.6.0 (3a92b2dbf0)
>> >> > > > > > cordova-blackberry: 3.6.0 (ed435bfc9e)
>> >> > > > > > cordova-windows: 3.6.0 (cdb292f4a3)
>> >> > > > > > cordova-wp8: 3.6.0 (a879f5258b)
>> >> > > > > > cordova-firefoxos: 3.6.0 (9ab176f855)
>> >> > > > > >
>> >> > > > > > cordova-ubuntu: 3.6.0 (bff472e4c2)
>> >> > > > > > cordova-amazon-fireos: 3.6.0 (4e94c6d198)
>> >> > > > > > cordova-js: 3.6.0 (906b34c0a4)
>> >> > > > > > cordova-mobile-spec: 3.6.0 (27053f7dd8)
>> >> > > > > > cordova-app-hello-world: 3.6.0 (65a2171a19)
>> >> > > > > >
>> >> > > > > > cordova-cli: 3.6.0-0.2.8 (01cb09f2d1)
>> >> > > > > > cordova-lib: 0.21.8 (14670ec9b5)
>> >> > > > > > cordova-plugman: 0.22.5 (29488fce7e)
>> >> > > > > >
>> >> > > > > >
>> >> > > > > > Upon a successful vote I will upload the archives to dist/,
>> >> > > > > > publish
>> >> > > > them
>> >> > > > > > to NPM, and post the corresponding blog post.
>> >> > > > > >
>> >> > > > > > Voting guidelines:
>> >> > > > > >
>> >> > > > >
>> >> > > >
>> >> > >
>> >> https://github.com/apache/cordova-coho/blob/master/docs/release-voting
>> >> > > .md
>> >> > > > > >
>> >> > > > > > Voting will go on for a minimum of 72 hours.
>> >> > > > > >
>> >> > > > > > I vote +1:
>> >> > > > > > * Ran coho audit-license-headers over the relevant repos
>> >> > > > > > * Used `license-checker` to ensure all dependencies have
>> >> > > > > Apache-compatible
>> >> > > > > > licenses
>> >> > > > > > * Ensured continuous build was green when repos were tagged
>> >> > > > > >
>> >> > > > >
>> >> > > >
>> >> > >
>> >> > >
>> >> > >
>> >> > > --
>> >> > > Carlos Santana
>> >> > > <cs...@gmail.com>
>> >> > >
>> >> >
>> >>
>> >
>> >
>>
>
>
Re: [Vote] 3.6.0 Cadence Release
Posted by Marcel Kinard <cm...@gmail.com>.
Anytime we have a mistake that can easily be avoided or validated by automation, it would seem to be a good thing to automate.
Today I had a thought about adding another option to createmobilespec.js to instantiate the test project from whatever is in cordova-dist-dev and the rest from npm / plugin registry. Any feedback on that being worthwhile?
On Sep 2, 2014, at 2:27 PM, Michal Mocny <mm...@chromium.org> wrote:
> We have a coho command that does verify-archive and I usually start testing
> with running that, perhaps now we need to add a coho verify-package, or
> something?
Re: [Vote] 3.6.0 Cadence Release
Posted by Michal Mocny <mm...@chromium.org>.
I think validation should be part of VOTE, actually as the first step to
testing a release. No sense testing a proposed release if its not known to
be the right thing.
We have a coho command that does verify-archive and I usually start testing
with running that, perhaps now we need to add a coho verify-package, or
something?
-Michal
On Tue, Sep 2, 2014 at 2:15 PM, Carlos Santana <cs...@gmail.com> wrote:
> I was just trying to validate what we put in npmjs.org matches what is
> located on [1]
>
> If both matches then it doesn't matter how you do your testing with npm or
> the content of [1].
>
> I'm guessing that everyone is testing using [1] and not apache git checkout
> hash from this email. But if they match to the same bits then who cares, we
> are all testing the same thing. Get the picture :-)
>
> Seriously now, On what step of the process do we validate npmjs.org
> against
> [1]? After vote has pass? or do it with with a "rc" and then make it
> "latest" on npm?
>
> [1]: https://dist.apache.org/repos/dist/dev/cordova/CB-7383/rc/
>
>
>
> On Tue, Sep 2, 2014 at 1:54 PM, Steven Gill <st...@gmail.com>
> wrote:
>
> > Looks like CLI VERSION file is incorrect :( Didn't get updated. Also
> looks
> > like the zip i uploaded for the CLI got generated incorrectly. Need to
> take
> > a deeper look.
> >
> > I don't see cordova-js 3.6.0-dev Version file anywhere.
> >
> > I'm also running into an issue with firefoxos testing. Looks like it
> can't
> > find shelljs module.
> >
> >
> >
> > On Tue, Sep 2, 2014 at 10:47 AM, Michal Mocny <mm...@chromium.org>
> wrote:
> >
> > > .. Looks like cordova-cli still has a VERSION file set to 3.5.0-0.2.4.
> > Is
> > > it even used?
> > >
> > > .. and cordova-cli deps on cordova-lib which deps on cordova-js which
> has
> > > VERSION file set to 3.6.0-dev.
> > >
> > >
> > > On Tue, Sep 2, 2014 at 1:42 PM, Michal Mocny <mm...@chromium.org>
> > wrote:
> > >
> > > > We could ask Apache folk for clarification, but if I understand the
> > > > requirements for release process correct, I think publishing an rc
> and
> > > > voting on it would be totally acceptable provided that:
> > > >
> > > > (a) *exactly* the tarball that went up to RC is used as the final
> > > release,
> > > > so that signatures match. At the very least I think that would mean
> to
> > > > leaving the "-rc#" portion out of all the "version" key (and any
> > VERSION
> > > > files).
> > > > (b) We don't advertise to users that this is a release they should
> > > consume.
> > > >
> > > > It looks like Steven has done this.
> > > >
> > > > -Michal
> > > >
> > > >
> > > > On Tue, Sep 2, 2014 at 1:26 PM, Steven Gill <st...@gmail.com>
> > > > wrote:
> > > >
> > > >> Actually, I like Carlos suggestion.
> > > >>
> > > >> We have already been publishing to npm under the RC tag for testing
> > (not
> > > >> releasing to public but just for dev testing).
> > > >>
> > > >> The last few releases you could go npm install cordova@rc and that
> > > would
> > > >> download the RC version of cordova that we were voting on.
> > > >>
> > > >> I went ahead and published all of the platforms + lib + plugman + js
> > > >> (everything we are voting on) to npm under an rc tag. So npm install
> > > >> cordova-android@rc would grab version 3.6.0.
> > > >>
> > > >> The easiest way to test is to now go npm install cordova@rc. No
> need
> > to
> > > >> --usegit anymore.
> > > >>
> > > >> The --usegit method would require you to checkout the tags in
> > > cordova-lib,
> > > >> cordova-js, npm link them, go to cli, npm link them, etc.
> > > >>
> > > >> -Steve
> > > >>
> > > >>
> > > >> On Tue, Sep 2, 2014 at 10:23 AM, Parashuram Narasimhan (MS OPEN
> TECH)
> > <
> > > >> panarasi@microsoft.com> wrote:
> > > >>
> > > >> > Agree with Jesse. If you still want to test it, I tried doing it
> > with
> > > a
> > > >> > private npm registry, and changed my npm to pick up from that
> > > registry.
> > > >> I
> > > >> > did not see a lot of value added though. I did this when I was
> > playing
> > > >> with
> > > >> > the idea of using npm to use plugins.
> > > >> >
> > > >> > -----Original Message-----
> > > >> > From: Jesse [mailto:purplecabbage@gmail.com]
> > > >> > Sent: Tuesday, September 2, 2014 10:21 AM
> > > >> > To: dev@cordova.apache.org
> > > >> > Subject: Re: [Vote] 3.6.0 Cadence Release
> > > >> >
> > > >> > We cannot post to npm without the vote passing. There is a bunch
> of
> > > >> crazy
> > > >> > overhead tag bs we could do, but then we would not be voting on
> the
> > > >> final
> > > >> > released binaries.
> > > >> >
> > > >> > Just test with --usegit
> > > >> >
> > > >> >
> > > >> >
> > > >> > @purplecabbage
> > > >> > risingj.com
> > > >> >
> > > >> >
> > > >> > On Tue, Sep 2, 2014 at 6:47 AM, Carlos Santana <
> > csantana23@gmail.com>
> > > >> > wrote:
> > > >> >
> > > >> > > I see cordova cli rc on npm, I want to test it using npm but I
> get
> > > >> > errors.
> > > >> > > Maybe cordova-lib should be also posted to npm but not make it
> > > latest
> > > >> > > until we release.
> > > >> > >
> > > >> > > I get this errors:
> > > >> > >
> > > >> > > $ npm install cordova@rc
> > > >> > >
> > > >> > > npm ERR! Error: version not found: cordova-lib@0.21.8
> > > >> > >
> > > >> > >
> > > >> > > On Tue, Sep 2, 2014 at 9:29 AM, Bryan Higgins <
> > > bryan@bryanhiggins.net
> > > >> >
> > > >> > > wrote:
> > > >> > >
> > > >> > > > +1
> > > >> > > >
> > > >> > > > - Verified signatures and hashes for cordova-blackberry
> > > >> > > > - Verified sha1 match tag 3.6.0
> > > >> > > > - Ran mobile spec on various BB10 devices and OS versions
> > > >> > > >
> > > >> > > > Steve - I added you as an owner for cordova-blackberry10 on
> npm.
> > > The
> > > >> > > > cordova-blackberry package should probably be unpublished.
> > > >> > > >
> > > >> > > >
> > > >> > > > On Tue, Sep 2, 2014 at 1:15 AM, Archana Naik
> > > >> > > > <na...@gmail.com>
> > > >> > > > wrote:
> > > >> > > >
> > > >> > > > > vote +1
> > > >> > > > > Verified amazon-fireos bundle, signatures and hashes.
> > > >> > > > >
> > > >> > > > > When are we planning to publish it to npm?
> > > >> > > > >
> > > >> > > > >
> > > >> > > > > On Mon, Sep 1, 2014 at 2:40 PM, Sergey Grebnov (Akvelon) <
> > > >> > > > > v-segreb@microsoft.com> wrote:
> > > >> > > > >
> > > >> > > > > > I vote +1:
> > > >> > > > > > * Verified signatures and hashes for cordova-cli,
> > cordova-lib,
> > > >> > > > > > cordova-plugman, cordova-windows, cordova-wp8
> > > >> > > > > > * Verified sha1s match tags for cordova-cli, cordova-lib,
> > > >> > > > > cordova-plugman,
> > > >> > > > > > cordova-windows, cordova-wp8
> > > >> > > > > > * Run Medic tests for Windows and Windows Phone 8
> > > >> > > > > > * Tested Android build on Windows
> > > >> > > > > > * Tested Windows platform manually
> > > >> > > > > > building and running app with VS2012 (msbuild
> > > >> > > > > > 4.0)/VS2013(msbuild
> > > >> > > > > 12.0)
> > > >> > > > > > -win and -phone switches
> > > >> > > > > > support of target platform settings (config.xml)
> > > >> > > > > > support of custom icons and splash screen images
> > > >> > > > > >
> > > >> > > > > > Thx!
> > > >> > > > > > Sergey
> > > >> > > > > > -----Original Message-----
> > > >> > > > > > From: Steven Gill [mailto:stevengill97@gmail.com]
> > > >> > > > > > Sent: Saturday, August 30, 2014 5:35 AM
> > > >> > > > > > To: dev@cordova.apache.org
> > > >> > > > > > Subject: [Vote] 3.6.0 Cadence Release
> > > >> > > > > >
> > > >> > > > > > Please review and vote on this 3.6.0 Cadence Release.
> > > >> > > > > >
> > > >> > > > > > Release issue:
> > https://issues.apache.org/jira/browse/CB-7383
> > > >> > > > > >
> > > >> > > > > > Repos ready to be released have been published to
> > > >> > > > > > dist/dev:
> > > https://dist.apache.org/repos/dist/dev/cordova/CB-7383
> > > >> > > > > >
> > > >> > > > > > The packages were published from their corresponding git
> > tags:
> > > >> > > > > > cordova-android: 3.6.0 (014327c59a)
> > > >> > > > > > cordova-ios: 3.6.0 (3a92b2dbf0)
> > > >> > > > > > cordova-blackberry: 3.6.0 (ed435bfc9e)
> > > >> > > > > > cordova-windows: 3.6.0 (cdb292f4a3)
> > > >> > > > > > cordova-wp8: 3.6.0 (a879f5258b)
> > > >> > > > > > cordova-firefoxos: 3.6.0 (9ab176f855)
> > > >> > > > > >
> > > >> > > > > > cordova-ubuntu: 3.6.0 (bff472e4c2)
> > > >> > > > > > cordova-amazon-fireos: 3.6.0 (4e94c6d198)
> > > >> > > > > > cordova-js: 3.6.0 (906b34c0a4)
> > > >> > > > > > cordova-mobile-spec: 3.6.0 (27053f7dd8)
> > > >> > > > > > cordova-app-hello-world: 3.6.0 (65a2171a19)
> > > >> > > > > >
> > > >> > > > > > cordova-cli: 3.6.0-0.2.8 (01cb09f2d1)
> > > >> > > > > > cordova-lib: 0.21.8 (14670ec9b5)
> > > >> > > > > > cordova-plugman: 0.22.5 (29488fce7e)
> > > >> > > > > >
> > > >> > > > > >
> > > >> > > > > > Upon a successful vote I will upload the archives to
> dist/,
> > > >> > > > > > publish
> > > >> > > > them
> > > >> > > > > > to NPM, and post the corresponding blog post.
> > > >> > > > > >
> > > >> > > > > > Voting guidelines:
> > > >> > > > > >
> > > >> > > > >
> > > >> > > >
> > > >> > >
> > > >>
> > https://github.com/apache/cordova-coho/blob/master/docs/release-voting
> > > >> > > .md
> > > >> > > > > >
> > > >> > > > > > Voting will go on for a minimum of 72 hours.
> > > >> > > > > >
> > > >> > > > > > I vote +1:
> > > >> > > > > > * Ran coho audit-license-headers over the relevant repos
> > > >> > > > > > * Used `license-checker` to ensure all dependencies have
> > > >> > > > > Apache-compatible
> > > >> > > > > > licenses
> > > >> > > > > > * Ensured continuous build was green when repos were
> tagged
> > > >> > > > > >
> > > >> > > > >
> > > >> > > >
> > > >> > >
> > > >> > >
> > > >> > >
> > > >> > > --
> > > >> > > Carlos Santana
> > > >> > > <cs...@gmail.com>
> > > >> > >
> > > >> >
> > > >>
> > > >
> > > >
> > >
> >
>
>
>
> --
> Carlos Santana
> <cs...@gmail.com>
>
Re: [Vote] 3.6.0 Cadence Release
Posted by Carlos Santana <cs...@gmail.com>.
I was just trying to validate what we put in npmjs.org matches what is
located on [1]
If both matches then it doesn't matter how you do your testing with npm or
the content of [1].
I'm guessing that everyone is testing using [1] and not apache git checkout
hash from this email. But if they match to the same bits then who cares, we
are all testing the same thing. Get the picture :-)
Seriously now, On what step of the process do we validate npmjs.org against
[1]? After vote has pass? or do it with with a "rc" and then make it
"latest" on npm?
[1]: https://dist.apache.org/repos/dist/dev/cordova/CB-7383/rc/
On Tue, Sep 2, 2014 at 1:54 PM, Steven Gill <st...@gmail.com> wrote:
> Looks like CLI VERSION file is incorrect :( Didn't get updated. Also looks
> like the zip i uploaded for the CLI got generated incorrectly. Need to take
> a deeper look.
>
> I don't see cordova-js 3.6.0-dev Version file anywhere.
>
> I'm also running into an issue with firefoxos testing. Looks like it can't
> find shelljs module.
>
>
>
> On Tue, Sep 2, 2014 at 10:47 AM, Michal Mocny <mm...@chromium.org> wrote:
>
> > .. Looks like cordova-cli still has a VERSION file set to 3.5.0-0.2.4.
> Is
> > it even used?
> >
> > .. and cordova-cli deps on cordova-lib which deps on cordova-js which has
> > VERSION file set to 3.6.0-dev.
> >
> >
> > On Tue, Sep 2, 2014 at 1:42 PM, Michal Mocny <mm...@chromium.org>
> wrote:
> >
> > > We could ask Apache folk for clarification, but if I understand the
> > > requirements for release process correct, I think publishing an rc and
> > > voting on it would be totally acceptable provided that:
> > >
> > > (a) *exactly* the tarball that went up to RC is used as the final
> > release,
> > > so that signatures match. At the very least I think that would mean to
> > > leaving the "-rc#" portion out of all the "version" key (and any
> VERSION
> > > files).
> > > (b) We don't advertise to users that this is a release they should
> > consume.
> > >
> > > It looks like Steven has done this.
> > >
> > > -Michal
> > >
> > >
> > > On Tue, Sep 2, 2014 at 1:26 PM, Steven Gill <st...@gmail.com>
> > > wrote:
> > >
> > >> Actually, I like Carlos suggestion.
> > >>
> > >> We have already been publishing to npm under the RC tag for testing
> (not
> > >> releasing to public but just for dev testing).
> > >>
> > >> The last few releases you could go npm install cordova@rc and that
> > would
> > >> download the RC version of cordova that we were voting on.
> > >>
> > >> I went ahead and published all of the platforms + lib + plugman + js
> > >> (everything we are voting on) to npm under an rc tag. So npm install
> > >> cordova-android@rc would grab version 3.6.0.
> > >>
> > >> The easiest way to test is to now go npm install cordova@rc. No need
> to
> > >> --usegit anymore.
> > >>
> > >> The --usegit method would require you to checkout the tags in
> > cordova-lib,
> > >> cordova-js, npm link them, go to cli, npm link them, etc.
> > >>
> > >> -Steve
> > >>
> > >>
> > >> On Tue, Sep 2, 2014 at 10:23 AM, Parashuram Narasimhan (MS OPEN TECH)
> <
> > >> panarasi@microsoft.com> wrote:
> > >>
> > >> > Agree with Jesse. If you still want to test it, I tried doing it
> with
> > a
> > >> > private npm registry, and changed my npm to pick up from that
> > registry.
> > >> I
> > >> > did not see a lot of value added though. I did this when I was
> playing
> > >> with
> > >> > the idea of using npm to use plugins.
> > >> >
> > >> > -----Original Message-----
> > >> > From: Jesse [mailto:purplecabbage@gmail.com]
> > >> > Sent: Tuesday, September 2, 2014 10:21 AM
> > >> > To: dev@cordova.apache.org
> > >> > Subject: Re: [Vote] 3.6.0 Cadence Release
> > >> >
> > >> > We cannot post to npm without the vote passing. There is a bunch of
> > >> crazy
> > >> > overhead tag bs we could do, but then we would not be voting on the
> > >> final
> > >> > released binaries.
> > >> >
> > >> > Just test with --usegit
> > >> >
> > >> >
> > >> >
> > >> > @purplecabbage
> > >> > risingj.com
> > >> >
> > >> >
> > >> > On Tue, Sep 2, 2014 at 6:47 AM, Carlos Santana <
> csantana23@gmail.com>
> > >> > wrote:
> > >> >
> > >> > > I see cordova cli rc on npm, I want to test it using npm but I get
> > >> > errors.
> > >> > > Maybe cordova-lib should be also posted to npm but not make it
> > latest
> > >> > > until we release.
> > >> > >
> > >> > > I get this errors:
> > >> > >
> > >> > > $ npm install cordova@rc
> > >> > >
> > >> > > npm ERR! Error: version not found: cordova-lib@0.21.8
> > >> > >
> > >> > >
> > >> > > On Tue, Sep 2, 2014 at 9:29 AM, Bryan Higgins <
> > bryan@bryanhiggins.net
> > >> >
> > >> > > wrote:
> > >> > >
> > >> > > > +1
> > >> > > >
> > >> > > > - Verified signatures and hashes for cordova-blackberry
> > >> > > > - Verified sha1 match tag 3.6.0
> > >> > > > - Ran mobile spec on various BB10 devices and OS versions
> > >> > > >
> > >> > > > Steve - I added you as an owner for cordova-blackberry10 on npm.
> > The
> > >> > > > cordova-blackberry package should probably be unpublished.
> > >> > > >
> > >> > > >
> > >> > > > On Tue, Sep 2, 2014 at 1:15 AM, Archana Naik
> > >> > > > <na...@gmail.com>
> > >> > > > wrote:
> > >> > > >
> > >> > > > > vote +1
> > >> > > > > Verified amazon-fireos bundle, signatures and hashes.
> > >> > > > >
> > >> > > > > When are we planning to publish it to npm?
> > >> > > > >
> > >> > > > >
> > >> > > > > On Mon, Sep 1, 2014 at 2:40 PM, Sergey Grebnov (Akvelon) <
> > >> > > > > v-segreb@microsoft.com> wrote:
> > >> > > > >
> > >> > > > > > I vote +1:
> > >> > > > > > * Verified signatures and hashes for cordova-cli,
> cordova-lib,
> > >> > > > > > cordova-plugman, cordova-windows, cordova-wp8
> > >> > > > > > * Verified sha1s match tags for cordova-cli, cordova-lib,
> > >> > > > > cordova-plugman,
> > >> > > > > > cordova-windows, cordova-wp8
> > >> > > > > > * Run Medic tests for Windows and Windows Phone 8
> > >> > > > > > * Tested Android build on Windows
> > >> > > > > > * Tested Windows platform manually
> > >> > > > > > building and running app with VS2012 (msbuild
> > >> > > > > > 4.0)/VS2013(msbuild
> > >> > > > > 12.0)
> > >> > > > > > -win and -phone switches
> > >> > > > > > support of target platform settings (config.xml)
> > >> > > > > > support of custom icons and splash screen images
> > >> > > > > >
> > >> > > > > > Thx!
> > >> > > > > > Sergey
> > >> > > > > > -----Original Message-----
> > >> > > > > > From: Steven Gill [mailto:stevengill97@gmail.com]
> > >> > > > > > Sent: Saturday, August 30, 2014 5:35 AM
> > >> > > > > > To: dev@cordova.apache.org
> > >> > > > > > Subject: [Vote] 3.6.0 Cadence Release
> > >> > > > > >
> > >> > > > > > Please review and vote on this 3.6.0 Cadence Release.
> > >> > > > > >
> > >> > > > > > Release issue:
> https://issues.apache.org/jira/browse/CB-7383
> > >> > > > > >
> > >> > > > > > Repos ready to be released have been published to
> > >> > > > > > dist/dev:
> > https://dist.apache.org/repos/dist/dev/cordova/CB-7383
> > >> > > > > >
> > >> > > > > > The packages were published from their corresponding git
> tags:
> > >> > > > > > cordova-android: 3.6.0 (014327c59a)
> > >> > > > > > cordova-ios: 3.6.0 (3a92b2dbf0)
> > >> > > > > > cordova-blackberry: 3.6.0 (ed435bfc9e)
> > >> > > > > > cordova-windows: 3.6.0 (cdb292f4a3)
> > >> > > > > > cordova-wp8: 3.6.0 (a879f5258b)
> > >> > > > > > cordova-firefoxos: 3.6.0 (9ab176f855)
> > >> > > > > >
> > >> > > > > > cordova-ubuntu: 3.6.0 (bff472e4c2)
> > >> > > > > > cordova-amazon-fireos: 3.6.0 (4e94c6d198)
> > >> > > > > > cordova-js: 3.6.0 (906b34c0a4)
> > >> > > > > > cordova-mobile-spec: 3.6.0 (27053f7dd8)
> > >> > > > > > cordova-app-hello-world: 3.6.0 (65a2171a19)
> > >> > > > > >
> > >> > > > > > cordova-cli: 3.6.0-0.2.8 (01cb09f2d1)
> > >> > > > > > cordova-lib: 0.21.8 (14670ec9b5)
> > >> > > > > > cordova-plugman: 0.22.5 (29488fce7e)
> > >> > > > > >
> > >> > > > > >
> > >> > > > > > Upon a successful vote I will upload the archives to dist/,
> > >> > > > > > publish
> > >> > > > them
> > >> > > > > > to NPM, and post the corresponding blog post.
> > >> > > > > >
> > >> > > > > > Voting guidelines:
> > >> > > > > >
> > >> > > > >
> > >> > > >
> > >> > >
> > >>
> https://github.com/apache/cordova-coho/blob/master/docs/release-voting
> > >> > > .md
> > >> > > > > >
> > >> > > > > > Voting will go on for a minimum of 72 hours.
> > >> > > > > >
> > >> > > > > > I vote +1:
> > >> > > > > > * Ran coho audit-license-headers over the relevant repos
> > >> > > > > > * Used `license-checker` to ensure all dependencies have
> > >> > > > > Apache-compatible
> > >> > > > > > licenses
> > >> > > > > > * Ensured continuous build was green when repos were tagged
> > >> > > > > >
> > >> > > > >
> > >> > > >
> > >> > >
> > >> > >
> > >> > >
> > >> > > --
> > >> > > Carlos Santana
> > >> > > <cs...@gmail.com>
> > >> > >
> > >> >
> > >>
> > >
> > >
> >
>
--
Carlos Santana
<cs...@gmail.com>
Re: [Vote] 3.6.0 Cadence Release
Posted by Steven Gill <st...@gmail.com>.
Looks like CLI VERSION file is incorrect :( Didn't get updated. Also looks
like the zip i uploaded for the CLI got generated incorrectly. Need to take
a deeper look.
I don't see cordova-js 3.6.0-dev Version file anywhere.
I'm also running into an issue with firefoxos testing. Looks like it can't
find shelljs module.
On Tue, Sep 2, 2014 at 10:47 AM, Michal Mocny <mm...@chromium.org> wrote:
> .. Looks like cordova-cli still has a VERSION file set to 3.5.0-0.2.4. Is
> it even used?
>
> .. and cordova-cli deps on cordova-lib which deps on cordova-js which has
> VERSION file set to 3.6.0-dev.
>
>
> On Tue, Sep 2, 2014 at 1:42 PM, Michal Mocny <mm...@chromium.org> wrote:
>
> > We could ask Apache folk for clarification, but if I understand the
> > requirements for release process correct, I think publishing an rc and
> > voting on it would be totally acceptable provided that:
> >
> > (a) *exactly* the tarball that went up to RC is used as the final
> release,
> > so that signatures match. At the very least I think that would mean to
> > leaving the "-rc#" portion out of all the "version" key (and any VERSION
> > files).
> > (b) We don't advertise to users that this is a release they should
> consume.
> >
> > It looks like Steven has done this.
> >
> > -Michal
> >
> >
> > On Tue, Sep 2, 2014 at 1:26 PM, Steven Gill <st...@gmail.com>
> > wrote:
> >
> >> Actually, I like Carlos suggestion.
> >>
> >> We have already been publishing to npm under the RC tag for testing (not
> >> releasing to public but just for dev testing).
> >>
> >> The last few releases you could go npm install cordova@rc and that
> would
> >> download the RC version of cordova that we were voting on.
> >>
> >> I went ahead and published all of the platforms + lib + plugman + js
> >> (everything we are voting on) to npm under an rc tag. So npm install
> >> cordova-android@rc would grab version 3.6.0.
> >>
> >> The easiest way to test is to now go npm install cordova@rc. No need to
> >> --usegit anymore.
> >>
> >> The --usegit method would require you to checkout the tags in
> cordova-lib,
> >> cordova-js, npm link them, go to cli, npm link them, etc.
> >>
> >> -Steve
> >>
> >>
> >> On Tue, Sep 2, 2014 at 10:23 AM, Parashuram Narasimhan (MS OPEN TECH) <
> >> panarasi@microsoft.com> wrote:
> >>
> >> > Agree with Jesse. If you still want to test it, I tried doing it with
> a
> >> > private npm registry, and changed my npm to pick up from that
> registry.
> >> I
> >> > did not see a lot of value added though. I did this when I was playing
> >> with
> >> > the idea of using npm to use plugins.
> >> >
> >> > -----Original Message-----
> >> > From: Jesse [mailto:purplecabbage@gmail.com]
> >> > Sent: Tuesday, September 2, 2014 10:21 AM
> >> > To: dev@cordova.apache.org
> >> > Subject: Re: [Vote] 3.6.0 Cadence Release
> >> >
> >> > We cannot post to npm without the vote passing. There is a bunch of
> >> crazy
> >> > overhead tag bs we could do, but then we would not be voting on the
> >> final
> >> > released binaries.
> >> >
> >> > Just test with --usegit
> >> >
> >> >
> >> >
> >> > @purplecabbage
> >> > risingj.com
> >> >
> >> >
> >> > On Tue, Sep 2, 2014 at 6:47 AM, Carlos Santana <cs...@gmail.com>
> >> > wrote:
> >> >
> >> > > I see cordova cli rc on npm, I want to test it using npm but I get
> >> > errors.
> >> > > Maybe cordova-lib should be also posted to npm but not make it
> latest
> >> > > until we release.
> >> > >
> >> > > I get this errors:
> >> > >
> >> > > $ npm install cordova@rc
> >> > >
> >> > > npm ERR! Error: version not found: cordova-lib@0.21.8
> >> > >
> >> > >
> >> > > On Tue, Sep 2, 2014 at 9:29 AM, Bryan Higgins <
> bryan@bryanhiggins.net
> >> >
> >> > > wrote:
> >> > >
> >> > > > +1
> >> > > >
> >> > > > - Verified signatures and hashes for cordova-blackberry
> >> > > > - Verified sha1 match tag 3.6.0
> >> > > > - Ran mobile spec on various BB10 devices and OS versions
> >> > > >
> >> > > > Steve - I added you as an owner for cordova-blackberry10 on npm.
> The
> >> > > > cordova-blackberry package should probably be unpublished.
> >> > > >
> >> > > >
> >> > > > On Tue, Sep 2, 2014 at 1:15 AM, Archana Naik
> >> > > > <na...@gmail.com>
> >> > > > wrote:
> >> > > >
> >> > > > > vote +1
> >> > > > > Verified amazon-fireos bundle, signatures and hashes.
> >> > > > >
> >> > > > > When are we planning to publish it to npm?
> >> > > > >
> >> > > > >
> >> > > > > On Mon, Sep 1, 2014 at 2:40 PM, Sergey Grebnov (Akvelon) <
> >> > > > > v-segreb@microsoft.com> wrote:
> >> > > > >
> >> > > > > > I vote +1:
> >> > > > > > * Verified signatures and hashes for cordova-cli, cordova-lib,
> >> > > > > > cordova-plugman, cordova-windows, cordova-wp8
> >> > > > > > * Verified sha1s match tags for cordova-cli, cordova-lib,
> >> > > > > cordova-plugman,
> >> > > > > > cordova-windows, cordova-wp8
> >> > > > > > * Run Medic tests for Windows and Windows Phone 8
> >> > > > > > * Tested Android build on Windows
> >> > > > > > * Tested Windows platform manually
> >> > > > > > building and running app with VS2012 (msbuild
> >> > > > > > 4.0)/VS2013(msbuild
> >> > > > > 12.0)
> >> > > > > > -win and -phone switches
> >> > > > > > support of target platform settings (config.xml)
> >> > > > > > support of custom icons and splash screen images
> >> > > > > >
> >> > > > > > Thx!
> >> > > > > > Sergey
> >> > > > > > -----Original Message-----
> >> > > > > > From: Steven Gill [mailto:stevengill97@gmail.com]
> >> > > > > > Sent: Saturday, August 30, 2014 5:35 AM
> >> > > > > > To: dev@cordova.apache.org
> >> > > > > > Subject: [Vote] 3.6.0 Cadence Release
> >> > > > > >
> >> > > > > > Please review and vote on this 3.6.0 Cadence Release.
> >> > > > > >
> >> > > > > > Release issue: https://issues.apache.org/jira/browse/CB-7383
> >> > > > > >
> >> > > > > > Repos ready to be released have been published to
> >> > > > > > dist/dev:
> https://dist.apache.org/repos/dist/dev/cordova/CB-7383
> >> > > > > >
> >> > > > > > The packages were published from their corresponding git tags:
> >> > > > > > cordova-android: 3.6.0 (014327c59a)
> >> > > > > > cordova-ios: 3.6.0 (3a92b2dbf0)
> >> > > > > > cordova-blackberry: 3.6.0 (ed435bfc9e)
> >> > > > > > cordova-windows: 3.6.0 (cdb292f4a3)
> >> > > > > > cordova-wp8: 3.6.0 (a879f5258b)
> >> > > > > > cordova-firefoxos: 3.6.0 (9ab176f855)
> >> > > > > >
> >> > > > > > cordova-ubuntu: 3.6.0 (bff472e4c2)
> >> > > > > > cordova-amazon-fireos: 3.6.0 (4e94c6d198)
> >> > > > > > cordova-js: 3.6.0 (906b34c0a4)
> >> > > > > > cordova-mobile-spec: 3.6.0 (27053f7dd8)
> >> > > > > > cordova-app-hello-world: 3.6.0 (65a2171a19)
> >> > > > > >
> >> > > > > > cordova-cli: 3.6.0-0.2.8 (01cb09f2d1)
> >> > > > > > cordova-lib: 0.21.8 (14670ec9b5)
> >> > > > > > cordova-plugman: 0.22.5 (29488fce7e)
> >> > > > > >
> >> > > > > >
> >> > > > > > Upon a successful vote I will upload the archives to dist/,
> >> > > > > > publish
> >> > > > them
> >> > > > > > to NPM, and post the corresponding blog post.
> >> > > > > >
> >> > > > > > Voting guidelines:
> >> > > > > >
> >> > > > >
> >> > > >
> >> > >
> >> https://github.com/apache/cordova-coho/blob/master/docs/release-voting
> >> > > .md
> >> > > > > >
> >> > > > > > Voting will go on for a minimum of 72 hours.
> >> > > > > >
> >> > > > > > I vote +1:
> >> > > > > > * Ran coho audit-license-headers over the relevant repos
> >> > > > > > * Used `license-checker` to ensure all dependencies have
> >> > > > > Apache-compatible
> >> > > > > > licenses
> >> > > > > > * Ensured continuous build was green when repos were tagged
> >> > > > > >
> >> > > > >
> >> > > >
> >> > >
> >> > >
> >> > >
> >> > > --
> >> > > Carlos Santana
> >> > > <cs...@gmail.com>
> >> > >
> >> >
> >>
> >
> >
>
Re: [Vote] 3.6.0 Cadence Release
Posted by Michal Mocny <mm...@chromium.org>.
.. Looks like cordova-cli still has a VERSION file set to 3.5.0-0.2.4. Is
it even used?
.. and cordova-cli deps on cordova-lib which deps on cordova-js which has
VERSION file set to 3.6.0-dev.
On Tue, Sep 2, 2014 at 1:42 PM, Michal Mocny <mm...@chromium.org> wrote:
> We could ask Apache folk for clarification, but if I understand the
> requirements for release process correct, I think publishing an rc and
> voting on it would be totally acceptable provided that:
>
> (a) *exactly* the tarball that went up to RC is used as the final release,
> so that signatures match. At the very least I think that would mean to
> leaving the "-rc#" portion out of all the "version" key (and any VERSION
> files).
> (b) We don't advertise to users that this is a release they should consume.
>
> It looks like Steven has done this.
>
> -Michal
>
>
> On Tue, Sep 2, 2014 at 1:26 PM, Steven Gill <st...@gmail.com>
> wrote:
>
>> Actually, I like Carlos suggestion.
>>
>> We have already been publishing to npm under the RC tag for testing (not
>> releasing to public but just for dev testing).
>>
>> The last few releases you could go npm install cordova@rc and that would
>> download the RC version of cordova that we were voting on.
>>
>> I went ahead and published all of the platforms + lib + plugman + js
>> (everything we are voting on) to npm under an rc tag. So npm install
>> cordova-android@rc would grab version 3.6.0.
>>
>> The easiest way to test is to now go npm install cordova@rc. No need to
>> --usegit anymore.
>>
>> The --usegit method would require you to checkout the tags in cordova-lib,
>> cordova-js, npm link them, go to cli, npm link them, etc.
>>
>> -Steve
>>
>>
>> On Tue, Sep 2, 2014 at 10:23 AM, Parashuram Narasimhan (MS OPEN TECH) <
>> panarasi@microsoft.com> wrote:
>>
>> > Agree with Jesse. If you still want to test it, I tried doing it with a
>> > private npm registry, and changed my npm to pick up from that registry.
>> I
>> > did not see a lot of value added though. I did this when I was playing
>> with
>> > the idea of using npm to use plugins.
>> >
>> > -----Original Message-----
>> > From: Jesse [mailto:purplecabbage@gmail.com]
>> > Sent: Tuesday, September 2, 2014 10:21 AM
>> > To: dev@cordova.apache.org
>> > Subject: Re: [Vote] 3.6.0 Cadence Release
>> >
>> > We cannot post to npm without the vote passing. There is a bunch of
>> crazy
>> > overhead tag bs we could do, but then we would not be voting on the
>> final
>> > released binaries.
>> >
>> > Just test with --usegit
>> >
>> >
>> >
>> > @purplecabbage
>> > risingj.com
>> >
>> >
>> > On Tue, Sep 2, 2014 at 6:47 AM, Carlos Santana <cs...@gmail.com>
>> > wrote:
>> >
>> > > I see cordova cli rc on npm, I want to test it using npm but I get
>> > errors.
>> > > Maybe cordova-lib should be also posted to npm but not make it latest
>> > > until we release.
>> > >
>> > > I get this errors:
>> > >
>> > > $ npm install cordova@rc
>> > >
>> > > npm ERR! Error: version not found: cordova-lib@0.21.8
>> > >
>> > >
>> > > On Tue, Sep 2, 2014 at 9:29 AM, Bryan Higgins <bryan@bryanhiggins.net
>> >
>> > > wrote:
>> > >
>> > > > +1
>> > > >
>> > > > - Verified signatures and hashes for cordova-blackberry
>> > > > - Verified sha1 match tag 3.6.0
>> > > > - Ran mobile spec on various BB10 devices and OS versions
>> > > >
>> > > > Steve - I added you as an owner for cordova-blackberry10 on npm. The
>> > > > cordova-blackberry package should probably be unpublished.
>> > > >
>> > > >
>> > > > On Tue, Sep 2, 2014 at 1:15 AM, Archana Naik
>> > > > <na...@gmail.com>
>> > > > wrote:
>> > > >
>> > > > > vote +1
>> > > > > Verified amazon-fireos bundle, signatures and hashes.
>> > > > >
>> > > > > When are we planning to publish it to npm?
>> > > > >
>> > > > >
>> > > > > On Mon, Sep 1, 2014 at 2:40 PM, Sergey Grebnov (Akvelon) <
>> > > > > v-segreb@microsoft.com> wrote:
>> > > > >
>> > > > > > I vote +1:
>> > > > > > * Verified signatures and hashes for cordova-cli, cordova-lib,
>> > > > > > cordova-plugman, cordova-windows, cordova-wp8
>> > > > > > * Verified sha1s match tags for cordova-cli, cordova-lib,
>> > > > > cordova-plugman,
>> > > > > > cordova-windows, cordova-wp8
>> > > > > > * Run Medic tests for Windows and Windows Phone 8
>> > > > > > * Tested Android build on Windows
>> > > > > > * Tested Windows platform manually
>> > > > > > building and running app with VS2012 (msbuild
>> > > > > > 4.0)/VS2013(msbuild
>> > > > > 12.0)
>> > > > > > -win and -phone switches
>> > > > > > support of target platform settings (config.xml)
>> > > > > > support of custom icons and splash screen images
>> > > > > >
>> > > > > > Thx!
>> > > > > > Sergey
>> > > > > > -----Original Message-----
>> > > > > > From: Steven Gill [mailto:stevengill97@gmail.com]
>> > > > > > Sent: Saturday, August 30, 2014 5:35 AM
>> > > > > > To: dev@cordova.apache.org
>> > > > > > Subject: [Vote] 3.6.0 Cadence Release
>> > > > > >
>> > > > > > Please review and vote on this 3.6.0 Cadence Release.
>> > > > > >
>> > > > > > Release issue: https://issues.apache.org/jira/browse/CB-7383
>> > > > > >
>> > > > > > Repos ready to be released have been published to
>> > > > > > dist/dev:https://dist.apache.org/repos/dist/dev/cordova/CB-7383
>> > > > > >
>> > > > > > The packages were published from their corresponding git tags:
>> > > > > > cordova-android: 3.6.0 (014327c59a)
>> > > > > > cordova-ios: 3.6.0 (3a92b2dbf0)
>> > > > > > cordova-blackberry: 3.6.0 (ed435bfc9e)
>> > > > > > cordova-windows: 3.6.0 (cdb292f4a3)
>> > > > > > cordova-wp8: 3.6.0 (a879f5258b)
>> > > > > > cordova-firefoxos: 3.6.0 (9ab176f855)
>> > > > > >
>> > > > > > cordova-ubuntu: 3.6.0 (bff472e4c2)
>> > > > > > cordova-amazon-fireos: 3.6.0 (4e94c6d198)
>> > > > > > cordova-js: 3.6.0 (906b34c0a4)
>> > > > > > cordova-mobile-spec: 3.6.0 (27053f7dd8)
>> > > > > > cordova-app-hello-world: 3.6.0 (65a2171a19)
>> > > > > >
>> > > > > > cordova-cli: 3.6.0-0.2.8 (01cb09f2d1)
>> > > > > > cordova-lib: 0.21.8 (14670ec9b5)
>> > > > > > cordova-plugman: 0.22.5 (29488fce7e)
>> > > > > >
>> > > > > >
>> > > > > > Upon a successful vote I will upload the archives to dist/,
>> > > > > > publish
>> > > > them
>> > > > > > to NPM, and post the corresponding blog post.
>> > > > > >
>> > > > > > Voting guidelines:
>> > > > > >
>> > > > >
>> > > >
>> > >
>> https://github.com/apache/cordova-coho/blob/master/docs/release-voting
>> > > .md
>> > > > > >
>> > > > > > Voting will go on for a minimum of 72 hours.
>> > > > > >
>> > > > > > I vote +1:
>> > > > > > * Ran coho audit-license-headers over the relevant repos
>> > > > > > * Used `license-checker` to ensure all dependencies have
>> > > > > Apache-compatible
>> > > > > > licenses
>> > > > > > * Ensured continuous build was green when repos were tagged
>> > > > > >
>> > > > >
>> > > >
>> > >
>> > >
>> > >
>> > > --
>> > > Carlos Santana
>> > > <cs...@gmail.com>
>> > >
>> >
>>
>
>
Re: [Vote] 3.6.0 Cadence Release
Posted by Michal Mocny <mm...@chromium.org>.
We could ask Apache folk for clarification, but if I understand the
requirements for release process correct, I think publishing an rc and
voting on it would be totally acceptable provided that:
(a) *exactly* the tarball that went up to RC is used as the final release,
so that signatures match. At the very least I think that would mean to
leaving the "-rc#" portion out of all the "version" key (and any VERSION
files).
(b) We don't advertise to users that this is a release they should consume.
It looks like Steven has done this.
-Michal
On Tue, Sep 2, 2014 at 1:26 PM, Steven Gill <st...@gmail.com> wrote:
> Actually, I like Carlos suggestion.
>
> We have already been publishing to npm under the RC tag for testing (not
> releasing to public but just for dev testing).
>
> The last few releases you could go npm install cordova@rc and that would
> download the RC version of cordova that we were voting on.
>
> I went ahead and published all of the platforms + lib + plugman + js
> (everything we are voting on) to npm under an rc tag. So npm install
> cordova-android@rc would grab version 3.6.0.
>
> The easiest way to test is to now go npm install cordova@rc. No need to
> --usegit anymore.
>
> The --usegit method would require you to checkout the tags in cordova-lib,
> cordova-js, npm link them, go to cli, npm link them, etc.
>
> -Steve
>
>
> On Tue, Sep 2, 2014 at 10:23 AM, Parashuram Narasimhan (MS OPEN TECH) <
> panarasi@microsoft.com> wrote:
>
> > Agree with Jesse. If you still want to test it, I tried doing it with a
> > private npm registry, and changed my npm to pick up from that registry. I
> > did not see a lot of value added though. I did this when I was playing
> with
> > the idea of using npm to use plugins.
> >
> > -----Original Message-----
> > From: Jesse [mailto:purplecabbage@gmail.com]
> > Sent: Tuesday, September 2, 2014 10:21 AM
> > To: dev@cordova.apache.org
> > Subject: Re: [Vote] 3.6.0 Cadence Release
> >
> > We cannot post to npm without the vote passing. There is a bunch of crazy
> > overhead tag bs we could do, but then we would not be voting on the final
> > released binaries.
> >
> > Just test with --usegit
> >
> >
> >
> > @purplecabbage
> > risingj.com
> >
> >
> > On Tue, Sep 2, 2014 at 6:47 AM, Carlos Santana <cs...@gmail.com>
> > wrote:
> >
> > > I see cordova cli rc on npm, I want to test it using npm but I get
> > errors.
> > > Maybe cordova-lib should be also posted to npm but not make it latest
> > > until we release.
> > >
> > > I get this errors:
> > >
> > > $ npm install cordova@rc
> > >
> > > npm ERR! Error: version not found: cordova-lib@0.21.8
> > >
> > >
> > > On Tue, Sep 2, 2014 at 9:29 AM, Bryan Higgins <br...@bryanhiggins.net>
> > > wrote:
> > >
> > > > +1
> > > >
> > > > - Verified signatures and hashes for cordova-blackberry
> > > > - Verified sha1 match tag 3.6.0
> > > > - Ran mobile spec on various BB10 devices and OS versions
> > > >
> > > > Steve - I added you as an owner for cordova-blackberry10 on npm. The
> > > > cordova-blackberry package should probably be unpublished.
> > > >
> > > >
> > > > On Tue, Sep 2, 2014 at 1:15 AM, Archana Naik
> > > > <na...@gmail.com>
> > > > wrote:
> > > >
> > > > > vote +1
> > > > > Verified amazon-fireos bundle, signatures and hashes.
> > > > >
> > > > > When are we planning to publish it to npm?
> > > > >
> > > > >
> > > > > On Mon, Sep 1, 2014 at 2:40 PM, Sergey Grebnov (Akvelon) <
> > > > > v-segreb@microsoft.com> wrote:
> > > > >
> > > > > > I vote +1:
> > > > > > * Verified signatures and hashes for cordova-cli, cordova-lib,
> > > > > > cordova-plugman, cordova-windows, cordova-wp8
> > > > > > * Verified sha1s match tags for cordova-cli, cordova-lib,
> > > > > cordova-plugman,
> > > > > > cordova-windows, cordova-wp8
> > > > > > * Run Medic tests for Windows and Windows Phone 8
> > > > > > * Tested Android build on Windows
> > > > > > * Tested Windows platform manually
> > > > > > building and running app with VS2012 (msbuild
> > > > > > 4.0)/VS2013(msbuild
> > > > > 12.0)
> > > > > > -win and -phone switches
> > > > > > support of target platform settings (config.xml)
> > > > > > support of custom icons and splash screen images
> > > > > >
> > > > > > Thx!
> > > > > > Sergey
> > > > > > -----Original Message-----
> > > > > > From: Steven Gill [mailto:stevengill97@gmail.com]
> > > > > > Sent: Saturday, August 30, 2014 5:35 AM
> > > > > > To: dev@cordova.apache.org
> > > > > > Subject: [Vote] 3.6.0 Cadence Release
> > > > > >
> > > > > > Please review and vote on this 3.6.0 Cadence Release.
> > > > > >
> > > > > > Release issue: https://issues.apache.org/jira/browse/CB-7383
> > > > > >
> > > > > > Repos ready to be released have been published to
> > > > > > dist/dev:https://dist.apache.org/repos/dist/dev/cordova/CB-7383
> > > > > >
> > > > > > The packages were published from their corresponding git tags:
> > > > > > cordova-android: 3.6.0 (014327c59a)
> > > > > > cordova-ios: 3.6.0 (3a92b2dbf0)
> > > > > > cordova-blackberry: 3.6.0 (ed435bfc9e)
> > > > > > cordova-windows: 3.6.0 (cdb292f4a3)
> > > > > > cordova-wp8: 3.6.0 (a879f5258b)
> > > > > > cordova-firefoxos: 3.6.0 (9ab176f855)
> > > > > >
> > > > > > cordova-ubuntu: 3.6.0 (bff472e4c2)
> > > > > > cordova-amazon-fireos: 3.6.0 (4e94c6d198)
> > > > > > cordova-js: 3.6.0 (906b34c0a4)
> > > > > > cordova-mobile-spec: 3.6.0 (27053f7dd8)
> > > > > > cordova-app-hello-world: 3.6.0 (65a2171a19)
> > > > > >
> > > > > > cordova-cli: 3.6.0-0.2.8 (01cb09f2d1)
> > > > > > cordova-lib: 0.21.8 (14670ec9b5)
> > > > > > cordova-plugman: 0.22.5 (29488fce7e)
> > > > > >
> > > > > >
> > > > > > Upon a successful vote I will upload the archives to dist/,
> > > > > > publish
> > > > them
> > > > > > to NPM, and post the corresponding blog post.
> > > > > >
> > > > > > Voting guidelines:
> > > > > >
> > > > >
> > > >
> > > https://github.com/apache/cordova-coho/blob/master/docs/release-voting
> > > .md
> > > > > >
> > > > > > Voting will go on for a minimum of 72 hours.
> > > > > >
> > > > > > I vote +1:
> > > > > > * Ran coho audit-license-headers over the relevant repos
> > > > > > * Used `license-checker` to ensure all dependencies have
> > > > > Apache-compatible
> > > > > > licenses
> > > > > > * Ensured continuous build was green when repos were tagged
> > > > > >
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Carlos Santana
> > > <cs...@gmail.com>
> > >
> >
>
Re: [Vote] 3.6.0 Cadence Release
Posted by Josh Soref <js...@blackberry.com>.
We need to have a second registry for staging instead of the official one.
On 9/4/14, 3:13 PM, "Michal Mocny" <mm...@chromium.org> wrote:
>That npm issue sounds like a blocker for voting on RC's that have been
>uploaded to npm, since it means we have to update the package after
>successful vote.
>
>Not sure of workarounds.
>
>-Michal
>
>
>On Thu, Sep 4, 2014 at 3:05 PM, Marcel Kinard <cm...@gmail.com> wrote:
>
>>
>> > One idea would be to bump the version of
>> android/amazon-fireos/windows/wp8 to 3.6.1, both in dist.a.o and in npm.
>> And we could leave all the other platforms/tools at 3.6.0. Except that
>>we
>> would also need to bump those references in
>> cordova-lib/cordova-lib/src/platforms.js, and then bump the reference in
>> cordova-cli to use this newer cordova-lib. Not pretty, but it should
>>work
>> technically. Sigh.
>>
>> If we are going with this approach, I'd actually suggest to bump the
>> version of everything to be 3.6.1, for consistency and less user
>>confusion.
Re: [Vote] 3.6.0 Cadence Release
Posted by Carlos Santana <cs...@gmail.com>.
Hum, Marcel ignore my recommendation.
I think the version is the id that can not be publish again, not the the
npm tag (i.e. rc, latest). So it means that package.json is the one that
contains the version "3.6.1" that can only be publish once.
On Thu, Sep 4, 2014 at 3:20 PM, Carlos Santana <cs...@gmail.com> wrote:
> Marcel sounds good approach for consistency and less confusion. but if
> something goes wrong with voting again, we will have to do a 3.6.2
> Can we publish to npm as it as 3.6.1-rc1, I think in the past we use to
> something similar with with git tags.
> If vote passes then we can publish the same content as 3.6.1, and
> unpublish 3.6.1-rc from npm
>
>
>
> On Thu, Sep 4, 2014 at 3:13 PM, Michal Mocny <mm...@chromium.org> wrote:
>
>> That npm issue sounds like a blocker for voting on RC's that have been
>> uploaded to npm, since it means we have to update the package after
>> successful vote.
>>
>> Not sure of workarounds.
>>
>> -Michal
>>
>>
>> On Thu, Sep 4, 2014 at 3:05 PM, Marcel Kinard <cm...@gmail.com> wrote:
>>
>> >
>> > > One idea would be to bump the version of
>> > android/amazon-fireos/windows/wp8 to 3.6.1, both in dist.a.o and in npm.
>> > And we could leave all the other platforms/tools at 3.6.0. Except that
>> we
>> > would also need to bump those references in
>> > cordova-lib/cordova-lib/src/platforms.js, and then bump the reference in
>> > cordova-cli to use this newer cordova-lib. Not pretty, but it should
>> work
>> > technically. Sigh.
>> >
>> > If we are going with this approach, I'd actually suggest to bump the
>> > version of everything to be 3.6.1, for consistency and less user
>> confusion.
>>
>
>
>
> --
> Carlos Santana
> <cs...@gmail.com>
>
--
Carlos Santana
<cs...@gmail.com>
Re: [Vote] 3.6.0 Cadence Release
Posted by Michal Mocny <mm...@chromium.org>.
You have to vote on the final artifact as it will be shipped to end users.
The problem with voting for tags is that its prone to us making mistakes
with the packaging (happens all the time, btw).
If final step of the releases was "now go update package.json and
re-package everything, then just go ahead and publish since its already
been voted on" that opens up that loophole again (as Jesse says).
-Michal
On Thu, Sep 4, 2014 at 3:33 PM, Joe Bowser <bo...@gmail.com> wrote:
> I think the Apache Way specifies that we have to vote on the final release,
> not the tag. If we can get clarification from an ASF person who knows the
> policy and isn't a troll, that would be helpful.
>
>
> On Thu, Sep 4, 2014 at 12:30 PM, Jesse <pu...@gmail.com> wrote:
>
> > Moving to a 3.6.1 sounds like the only way forward, but let's not publish
> > it until AFTER a vore.
> >
> > We should be voting on what we see in the git-repos ( after verifying
> that
> > it is identical to the packaged binaries)
> > We should be testing via --usegit all the npm stuff should just be gravy.
> >
> > Carlos:
> > - The problem is that we won't be voting on what is already published
> >
> > @purplecabbage
> > risingj.com
> >
> >
> > On Thu, Sep 4, 2014 at 12:20 PM, Carlos Santana <cs...@gmail.com>
> > wrote:
> >
> > > Marcel sounds good approach for consistency and less confusion. but if
> > > something goes wrong with voting again, we will have to do a 3.6.2
> > > Can we publish to npm as it as 3.6.1-rc1, I think in the past we use to
> > > something similar with with git tags.
> > > If vote passes then we can publish the same content as 3.6.1, and
> > unpublish
> > > 3.6.1-rc from npm
> > >
> > >
> > >
> > > On Thu, Sep 4, 2014 at 3:13 PM, Michal Mocny <mm...@chromium.org>
> > wrote:
> > >
> > > > That npm issue sounds like a blocker for voting on RC's that have
> been
> > > > uploaded to npm, since it means we have to update the package after
> > > > successful vote.
> > > >
> > > > Not sure of workarounds.
> > > >
> > > > -Michal
> > > >
> > > >
> > > > On Thu, Sep 4, 2014 at 3:05 PM, Marcel Kinard <cm...@gmail.com>
> > > wrote:
> > > >
> > > > >
> > > > > > One idea would be to bump the version of
> > > > > android/amazon-fireos/windows/wp8 to 3.6.1, both in dist.a.o and in
> > > npm.
> > > > > And we could leave all the other platforms/tools at 3.6.0. Except
> > that
> > > we
> > > > > would also need to bump those references in
> > > > > cordova-lib/cordova-lib/src/platforms.js, and then bump the
> reference
> > > in
> > > > > cordova-cli to use this newer cordova-lib. Not pretty, but it
> should
> > > work
> > > > > technically. Sigh.
> > > > >
> > > > > If we are going with this approach, I'd actually suggest to bump
> the
> > > > > version of everything to be 3.6.1, for consistency and less user
> > > > confusion.
> > > >
> > >
> > >
> > >
> > > --
> > > Carlos Santana
> > > <cs...@gmail.com>
> > >
> >
>
Re: [Vote] 3.6.0 Cadence Release
Posted by Joe Bowser <bo...@gmail.com>.
I think the Apache Way specifies that we have to vote on the final release,
not the tag. If we can get clarification from an ASF person who knows the
policy and isn't a troll, that would be helpful.
On Thu, Sep 4, 2014 at 12:30 PM, Jesse <pu...@gmail.com> wrote:
> Moving to a 3.6.1 sounds like the only way forward, but let's not publish
> it until AFTER a vore.
>
> We should be voting on what we see in the git-repos ( after verifying that
> it is identical to the packaged binaries)
> We should be testing via --usegit all the npm stuff should just be gravy.
>
> Carlos:
> - The problem is that we won't be voting on what is already published
>
> @purplecabbage
> risingj.com
>
>
> On Thu, Sep 4, 2014 at 12:20 PM, Carlos Santana <cs...@gmail.com>
> wrote:
>
> > Marcel sounds good approach for consistency and less confusion. but if
> > something goes wrong with voting again, we will have to do a 3.6.2
> > Can we publish to npm as it as 3.6.1-rc1, I think in the past we use to
> > something similar with with git tags.
> > If vote passes then we can publish the same content as 3.6.1, and
> unpublish
> > 3.6.1-rc from npm
> >
> >
> >
> > On Thu, Sep 4, 2014 at 3:13 PM, Michal Mocny <mm...@chromium.org>
> wrote:
> >
> > > That npm issue sounds like a blocker for voting on RC's that have been
> > > uploaded to npm, since it means we have to update the package after
> > > successful vote.
> > >
> > > Not sure of workarounds.
> > >
> > > -Michal
> > >
> > >
> > > On Thu, Sep 4, 2014 at 3:05 PM, Marcel Kinard <cm...@gmail.com>
> > wrote:
> > >
> > > >
> > > > > One idea would be to bump the version of
> > > > android/amazon-fireos/windows/wp8 to 3.6.1, both in dist.a.o and in
> > npm.
> > > > And we could leave all the other platforms/tools at 3.6.0. Except
> that
> > we
> > > > would also need to bump those references in
> > > > cordova-lib/cordova-lib/src/platforms.js, and then bump the reference
> > in
> > > > cordova-cli to use this newer cordova-lib. Not pretty, but it should
> > work
> > > > technically. Sigh.
> > > >
> > > > If we are going with this approach, I'd actually suggest to bump the
> > > > version of everything to be 3.6.1, for consistency and less user
> > > confusion.
> > >
> >
> >
> >
> > --
> > Carlos Santana
> > <cs...@gmail.com>
> >
>
Re: [Vote] 3.6.0 Cadence Release
Posted by Carlos Santana <cs...@gmail.com>.
Yep I agree with Marcel flow, vote on content from dist-dev including
everything from dist-dev (platform, cli, plugman, plugins) when vote passes
publish from dev-dist to both dist and npm
Does coho currently use to publish to dist and npm.
I propose that we update coho to do a verification on the publishing. coho
after doing a publish to npm, turns around and does a npm install of what
just published and does a compare against content dist/
On Thu, Sep 4, 2014 at 4:38 PM, Shazron <sh...@gmail.com> wrote:
> Don't forget that now coho for a release can update the version in the
> "cordova/version" scripts of the project templates now -- those versions
> have to be updated as well.
>
>
> On Thu, Sep 4, 2014 at 12:54 PM, Marcel Kinard <cm...@gmail.com> wrote:
>
> > Here is more specifics on what I'd suggest:
> >
> > - on the 3.6.x branch of all the platforms and tools in git, modify
> > VERSION and/or package.json to bump the version to 3.6.1. Create a new
> > 3.6.1 tag at this new head of the 3.6.x branches. Do not move the 3.6.0
> > tags.
> > - build new archives of these 3.6.1 images and post them to dist-dev. Do
> > not publish them to npm.
> > - do a vote based on the contents of dist-dev. For testing, use --usegit
> > after verifying dist-dev matches the git content (a script could do the
> > verify).
> > - after the vote passes, publish 3.6.1 to npm at the same time as
> > promoting from dist-dev to dist.
> >
> > Going forward, publishing rc's to npm before the vote isn't possible,
> > because the version in package.json would need to be modified between rc
> > and final.
> >
> > On Sep 4, 2014, at 3:30 PM, Jesse <pu...@gmail.com> wrote:
> >
> > > Moving to a 3.6.1 sounds like the only way forward, but let's not
> publish
> > > it until AFTER a vore.
> > >
> > > We should be voting on what we see in the git-repos ( after verifying
> > that
> > > it is identical to the packaged binaries)
> > > We should be testing via --usegit all the npm stuff should just be
> gravy.
> > >
> > > Carlos:
> > > - The problem is that we won't be voting on what is already published
> > >
> > > @purplecabbage
> > > risingj.com
> >
> >
>
--
Carlos Santana
<cs...@gmail.com>
Re: [Vote] 3.6.0 Cadence Release
Posted by Shazron <sh...@gmail.com>.
Don't forget that now coho for a release can update the version in the
"cordova/version" scripts of the project templates now -- those versions
have to be updated as well.
On Thu, Sep 4, 2014 at 12:54 PM, Marcel Kinard <cm...@gmail.com> wrote:
> Here is more specifics on what I'd suggest:
>
> - on the 3.6.x branch of all the platforms and tools in git, modify
> VERSION and/or package.json to bump the version to 3.6.1. Create a new
> 3.6.1 tag at this new head of the 3.6.x branches. Do not move the 3.6.0
> tags.
> - build new archives of these 3.6.1 images and post them to dist-dev. Do
> not publish them to npm.
> - do a vote based on the contents of dist-dev. For testing, use --usegit
> after verifying dist-dev matches the git content (a script could do the
> verify).
> - after the vote passes, publish 3.6.1 to npm at the same time as
> promoting from dist-dev to dist.
>
> Going forward, publishing rc's to npm before the vote isn't possible,
> because the version in package.json would need to be modified between rc
> and final.
>
> On Sep 4, 2014, at 3:30 PM, Jesse <pu...@gmail.com> wrote:
>
> > Moving to a 3.6.1 sounds like the only way forward, but let's not publish
> > it until AFTER a vore.
> >
> > We should be voting on what we see in the git-repos ( after verifying
> that
> > it is identical to the packaged binaries)
> > We should be testing via --usegit all the npm stuff should just be gravy.
> >
> > Carlos:
> > - The problem is that we won't be voting on what is already published
> >
> > @purplecabbage
> > risingj.com
>
>
RE: [Vote] 3.6.0 Cadence Release
Posted by "Sergey Grebnov (Akvelon)" <v-...@microsoft.com>.
Marcel, thanks a lot!
-----Original Message-----
From: Marcel Kinard [mailto:cmarcelk@gmail.com]
Sent: Friday, September 5, 2014 5:38 PM
To: dev@cordova.apache.org
Subject: Re: [Vote] 3.6.0 Cadence Release
We haven't yet restarted the vote due to the npm-publish issues, so I'll pull this in for release. For tools, since we don't create branches, I'll just bump the version and place a new tag at the head of master.
On Sep 5, 2014, at 3:56 AM, Sergey Grebnov (Akvelon) <v-...@microsoft.com> wrote:
> Just found out that the following fix has been landed to master only and not included to LIB release, I don't want to break the voting since we have a workaround for this, but if we do another voting round by some another reason, please include it.
>
> https://github.com/apache/cordova-lib/commit/165863134c31f4203c2bdbee6f5720baf48fee17
>
> Thx!
> Sergey
Re: [Vote] 3.6.0 Cadence Release
Posted by Marcel Kinard <cm...@gmail.com>.
We haven't yet restarted the vote due to the npm-publish issues, so I'll pull this in for release. For tools, since we don't create branches, I'll just bump the version and place a new tag at the head of master.
On Sep 5, 2014, at 3:56 AM, Sergey Grebnov (Akvelon) <v-...@microsoft.com> wrote:
> Just found out that the following fix has been landed to master only and not included to LIB release, I don't want to break the voting since we have a workaround for this, but if we do another voting round by some another reason, please include it.
>
> https://github.com/apache/cordova-lib/commit/165863134c31f4203c2bdbee6f5720baf48fee17
>
> Thx!
> Sergey
RE: [Vote] 3.6.0 Cadence Release
Posted by "Sergey Grebnov (Akvelon)" <v-...@microsoft.com>.
Just found out that the following fix has been landed to master only and not included to LIB release, I don't want to break the voting since we have a workaround for this, but if we do another voting round by some another reason, please include it.
https://github.com/apache/cordova-lib/commit/165863134c31f4203c2bdbee6f5720baf48fee17
Thx!
Sergey
-----Original Message-----
From: Marcel Kinard [mailto:cmarcelk@gmail.com]
Sent: Friday, September 5, 2014 1:03 AM
To: dev@cordova.apache.org
Subject: Re: [Vote] 3.6.0 Cadence Release
If memory serves, there was a problem discovered a while back with 0.0.1rc1 being "greater than" 0.0.1 in the alphabetical sort order. So if your dependencies didn't pin to exactly "0.0.1" then users could end up with some rc's in their node_modules folder when dependencies were installed.
If we could solve that problem, and if we'd be willing to change the package.json between rc and final, then it could probably work.
I'm interested to see how painless we can make --usegit.
On Sep 4, 2014, at 4:05 PM, Brian LeRoux <b...@brian.io> wrote:
> 0.0.1rc1
> 0.0.1rc2
>
> no?
Re: [Vote] 3.6.0 Cadence Release
Posted by Marcel Kinard <cm...@gmail.com>.
If memory serves, there was a problem discovered a while back with 0.0.1rc1 being "greater than" 0.0.1 in the alphabetical sort order. So if your dependencies didn't pin to exactly "0.0.1" then users could end up with some rc's in their node_modules folder when dependencies were installed.
If we could solve that problem, and if we'd be willing to change the package.json between rc and final, then it could probably work.
I'm interested to see how painless we can make --usegit.
On Sep 4, 2014, at 4:05 PM, Brian LeRoux <b...@brian.io> wrote:
> 0.0.1rc1
> 0.0.1rc2
>
> no?
Re: [Vote] 3.6.0 Cadence Release
Posted by Joe Bowser <bo...@gmail.com>.
Well, for some reason we deviated from that last release. I don't know why
but Steve proposed the change and it made sense at the time.
On Sep 4, 2014 1:05 PM, "Brian LeRoux" <b...@brian.io> wrote:
> 0.0.1rc1
> 0.0.1rc2
>
> no?
>
>
> On Thu, Sep 4, 2014 at 12:54 PM, Marcel Kinard <cm...@gmail.com> wrote:
>
> > Here is more specifics on what I'd suggest:
> >
> > - on the 3.6.x branch of all the platforms and tools in git, modify
> > VERSION and/or package.json to bump the version to 3.6.1. Create a new
> > 3.6.1 tag at this new head of the 3.6.x branches. Do not move the 3.6.0
> > tags.
> > - build new archives of these 3.6.1 images and post them to dist-dev. Do
> > not publish them to npm.
> > - do a vote based on the contents of dist-dev. For testing, use --usegit
> > after verifying dist-dev matches the git content (a script could do the
> > verify).
> > - after the vote passes, publish 3.6.1 to npm at the same time as
> > promoting from dist-dev to dist.
> >
> > Going forward, publishing rc's to npm before the vote isn't possible,
> > because the version in package.json would need to be modified between rc
> > and final.
> >
> > On Sep 4, 2014, at 3:30 PM, Jesse <pu...@gmail.com> wrote:
> >
> > > Moving to a 3.6.1 sounds like the only way forward, but let's not
> publish
> > > it until AFTER a vore.
> > >
> > > We should be voting on what we see in the git-repos ( after verifying
> > that
> > > it is identical to the packaged binaries)
> > > We should be testing via --usegit all the npm stuff should just be
> gravy.
> > >
> > > Carlos:
> > > - The problem is that we won't be voting on what is already published
> > >
> > > @purplecabbage
> > > risingj.com
> >
> >
>
Re: [Vote] 3.6.0 Cadence Release
Posted by Brian LeRoux <b...@brian.io>.
0.0.1rc1
0.0.1rc2
no?
On Thu, Sep 4, 2014 at 12:54 PM, Marcel Kinard <cm...@gmail.com> wrote:
> Here is more specifics on what I'd suggest:
>
> - on the 3.6.x branch of all the platforms and tools in git, modify
> VERSION and/or package.json to bump the version to 3.6.1. Create a new
> 3.6.1 tag at this new head of the 3.6.x branches. Do not move the 3.6.0
> tags.
> - build new archives of these 3.6.1 images and post them to dist-dev. Do
> not publish them to npm.
> - do a vote based on the contents of dist-dev. For testing, use --usegit
> after verifying dist-dev matches the git content (a script could do the
> verify).
> - after the vote passes, publish 3.6.1 to npm at the same time as
> promoting from dist-dev to dist.
>
> Going forward, publishing rc's to npm before the vote isn't possible,
> because the version in package.json would need to be modified between rc
> and final.
>
> On Sep 4, 2014, at 3:30 PM, Jesse <pu...@gmail.com> wrote:
>
> > Moving to a 3.6.1 sounds like the only way forward, but let's not publish
> > it until AFTER a vore.
> >
> > We should be voting on what we see in the git-repos ( after verifying
> that
> > it is identical to the packaged binaries)
> > We should be testing via --usegit all the npm stuff should just be gravy.
> >
> > Carlos:
> > - The problem is that we won't be voting on what is already published
> >
> > @purplecabbage
> > risingj.com
>
>
Re: [Vote] 3.6.0 Cadence Release
Posted by Joe Bowser <bo...@gmail.com>.
Sounds good.
On Thu, Sep 4, 2014 at 12:59 PM, Jesse <pu...@gmail.com> wrote:
> I agree with all of Marcel's suggestions.
>
> @purplecabbage
> risingj.com
>
>
> On Thu, Sep 4, 2014 at 12:54 PM, Marcel Kinard <cm...@gmail.com> wrote:
>
> > Here is more specifics on what I'd suggest:
> >
> > - on the 3.6.x branch of all the platforms and tools in git, modify
> > VERSION and/or package.json to bump the version to 3.6.1. Create a new
> > 3.6.1 tag at this new head of the 3.6.x branches. Do not move the 3.6.0
> > tags.
> > - build new archives of these 3.6.1 images and post them to dist-dev. Do
> > not publish them to npm.
> > - do a vote based on the contents of dist-dev. For testing, use --usegit
> > after verifying dist-dev matches the git content (a script could do the
> > verify).
> > - after the vote passes, publish 3.6.1 to npm at the same time as
> > promoting from dist-dev to dist.
> >
> > Going forward, publishing rc's to npm before the vote isn't possible,
> > because the version in package.json would need to be modified between rc
> > and final.
> >
> > On Sep 4, 2014, at 3:30 PM, Jesse <pu...@gmail.com> wrote:
> >
> > > Moving to a 3.6.1 sounds like the only way forward, but let's not
> publish
> > > it until AFTER a vore.
> > >
> > > We should be voting on what we see in the git-repos ( after verifying
> > that
> > > it is identical to the packaged binaries)
> > > We should be testing via --usegit all the npm stuff should just be
> gravy.
> > >
> > > Carlos:
> > > - The problem is that we won't be voting on what is already published
> > >
> > > @purplecabbage
> > > risingj.com
> >
> >
>
Re: [Vote] 3.6.0 Cadence Release
Posted by Jesse <pu...@gmail.com>.
I agree with all of Marcel's suggestions.
@purplecabbage
risingj.com
On Thu, Sep 4, 2014 at 12:54 PM, Marcel Kinard <cm...@gmail.com> wrote:
> Here is more specifics on what I'd suggest:
>
> - on the 3.6.x branch of all the platforms and tools in git, modify
> VERSION and/or package.json to bump the version to 3.6.1. Create a new
> 3.6.1 tag at this new head of the 3.6.x branches. Do not move the 3.6.0
> tags.
> - build new archives of these 3.6.1 images and post them to dist-dev. Do
> not publish them to npm.
> - do a vote based on the contents of dist-dev. For testing, use --usegit
> after verifying dist-dev matches the git content (a script could do the
> verify).
> - after the vote passes, publish 3.6.1 to npm at the same time as
> promoting from dist-dev to dist.
>
> Going forward, publishing rc's to npm before the vote isn't possible,
> because the version in package.json would need to be modified between rc
> and final.
>
> On Sep 4, 2014, at 3:30 PM, Jesse <pu...@gmail.com> wrote:
>
> > Moving to a 3.6.1 sounds like the only way forward, but let's not publish
> > it until AFTER a vore.
> >
> > We should be voting on what we see in the git-repos ( after verifying
> that
> > it is identical to the packaged binaries)
> > We should be testing via --usegit all the npm stuff should just be gravy.
> >
> > Carlos:
> > - The problem is that we won't be voting on what is already published
> >
> > @purplecabbage
> > risingj.com
>
>
Re: [Vote] 3.6.0 Cadence Release
Posted by Marcel Kinard <cm...@gmail.com>.
Here is more specifics on what I'd suggest:
- on the 3.6.x branch of all the platforms and tools in git, modify VERSION and/or package.json to bump the version to 3.6.1. Create a new 3.6.1 tag at this new head of the 3.6.x branches. Do not move the 3.6.0 tags.
- build new archives of these 3.6.1 images and post them to dist-dev. Do not publish them to npm.
- do a vote based on the contents of dist-dev. For testing, use --usegit after verifying dist-dev matches the git content (a script could do the verify).
- after the vote passes, publish 3.6.1 to npm at the same time as promoting from dist-dev to dist.
Going forward, publishing rc's to npm before the vote isn't possible, because the version in package.json would need to be modified between rc and final.
On Sep 4, 2014, at 3:30 PM, Jesse <pu...@gmail.com> wrote:
> Moving to a 3.6.1 sounds like the only way forward, but let's not publish
> it until AFTER a vore.
>
> We should be voting on what we see in the git-repos ( after verifying that
> it is identical to the packaged binaries)
> We should be testing via --usegit all the npm stuff should just be gravy.
>
> Carlos:
> - The problem is that we won't be voting on what is already published
>
> @purplecabbage
> risingj.com
Re: [Vote] 3.6.0 Cadence Release
Posted by Jesse <pu...@gmail.com>.
Moving to a 3.6.1 sounds like the only way forward, but let's not publish
it until AFTER a vore.
We should be voting on what we see in the git-repos ( after verifying that
it is identical to the packaged binaries)
We should be testing via --usegit all the npm stuff should just be gravy.
Carlos:
- The problem is that we won't be voting on what is already published
@purplecabbage
risingj.com
On Thu, Sep 4, 2014 at 12:20 PM, Carlos Santana <cs...@gmail.com>
wrote:
> Marcel sounds good approach for consistency and less confusion. but if
> something goes wrong with voting again, we will have to do a 3.6.2
> Can we publish to npm as it as 3.6.1-rc1, I think in the past we use to
> something similar with with git tags.
> If vote passes then we can publish the same content as 3.6.1, and unpublish
> 3.6.1-rc from npm
>
>
>
> On Thu, Sep 4, 2014 at 3:13 PM, Michal Mocny <mm...@chromium.org> wrote:
>
> > That npm issue sounds like a blocker for voting on RC's that have been
> > uploaded to npm, since it means we have to update the package after
> > successful vote.
> >
> > Not sure of workarounds.
> >
> > -Michal
> >
> >
> > On Thu, Sep 4, 2014 at 3:05 PM, Marcel Kinard <cm...@gmail.com>
> wrote:
> >
> > >
> > > > One idea would be to bump the version of
> > > android/amazon-fireos/windows/wp8 to 3.6.1, both in dist.a.o and in
> npm.
> > > And we could leave all the other platforms/tools at 3.6.0. Except that
> we
> > > would also need to bump those references in
> > > cordova-lib/cordova-lib/src/platforms.js, and then bump the reference
> in
> > > cordova-cli to use this newer cordova-lib. Not pretty, but it should
> work
> > > technically. Sigh.
> > >
> > > If we are going with this approach, I'd actually suggest to bump the
> > > version of everything to be 3.6.1, for consistency and less user
> > confusion.
> >
>
>
>
> --
> Carlos Santana
> <cs...@gmail.com>
>
Re: [Vote] 3.6.0 Cadence Release
Posted by Carlos Santana <cs...@gmail.com>.
Marcel sounds good approach for consistency and less confusion. but if
something goes wrong with voting again, we will have to do a 3.6.2
Can we publish to npm as it as 3.6.1-rc1, I think in the past we use to
something similar with with git tags.
If vote passes then we can publish the same content as 3.6.1, and unpublish
3.6.1-rc from npm
On Thu, Sep 4, 2014 at 3:13 PM, Michal Mocny <mm...@chromium.org> wrote:
> That npm issue sounds like a blocker for voting on RC's that have been
> uploaded to npm, since it means we have to update the package after
> successful vote.
>
> Not sure of workarounds.
>
> -Michal
>
>
> On Thu, Sep 4, 2014 at 3:05 PM, Marcel Kinard <cm...@gmail.com> wrote:
>
> >
> > > One idea would be to bump the version of
> > android/amazon-fireos/windows/wp8 to 3.6.1, both in dist.a.o and in npm.
> > And we could leave all the other platforms/tools at 3.6.0. Except that we
> > would also need to bump those references in
> > cordova-lib/cordova-lib/src/platforms.js, and then bump the reference in
> > cordova-cli to use this newer cordova-lib. Not pretty, but it should work
> > technically. Sigh.
> >
> > If we are going with this approach, I'd actually suggest to bump the
> > version of everything to be 3.6.1, for consistency and less user
> confusion.
>
--
Carlos Santana
<cs...@gmail.com>
Re: [Vote] 3.6.0 Cadence Release
Posted by Michal Mocny <mm...@chromium.org>.
That npm issue sounds like a blocker for voting on RC's that have been
uploaded to npm, since it means we have to update the package after
successful vote.
Not sure of workarounds.
-Michal
On Thu, Sep 4, 2014 at 3:05 PM, Marcel Kinard <cm...@gmail.com> wrote:
>
> > One idea would be to bump the version of
> android/amazon-fireos/windows/wp8 to 3.6.1, both in dist.a.o and in npm.
> And we could leave all the other platforms/tools at 3.6.0. Except that we
> would also need to bump those references in
> cordova-lib/cordova-lib/src/platforms.js, and then bump the reference in
> cordova-cli to use this newer cordova-lib. Not pretty, but it should work
> technically. Sigh.
>
> If we are going with this approach, I'd actually suggest to bump the
> version of everything to be 3.6.1, for consistency and less user confusion.
Re: [Vote] 3.6.0 Cadence Release
Posted by Marcel Kinard <cm...@gmail.com>.
> One idea would be to bump the version of android/amazon-fireos/windows/wp8 to 3.6.1, both in dist.a.o and in npm. And we could leave all the other platforms/tools at 3.6.0. Except that we would also need to bump those references in cordova-lib/cordova-lib/src/platforms.js, and then bump the reference in cordova-cli to use this newer cordova-lib. Not pretty, but it should work technically. Sigh.
If we are going with this approach, I'd actually suggest to bump the version of everything to be 3.6.1, for consistency and less user confusion.
Re: [Vote] 3.6.0 Cadence Release
Posted by Marcel Kinard <cm...@gmail.com>.
I think we have unintentionally shot ourselves in the foot.
While trying to "npm publish" the updated 3.6.0 rc snapshots of android/amazon-fireos/windows/wp8, npm is rejecting it with:
npm ERR! Error: forbidden cannot modify pre-existing version: 3.6.0
When I do an "npm info cordova-android", it already knows the 3.6.0 version (because it parsed it from first rc's package.json), even though the "latest" tag points at 3.5.1 and the "rc" tag points at 3.6.0.
I found the following items:
https://github.com/npm/npm-registry-couchapp/issues/148
...if you publish foo@1.2.3, you can still un-publish foo@1.2.3. But then, you will not be able to publish something else to that same package identifier. Not now, not never. Deleting documents entirely will be forbidden...
If the bits are gone, ok, it's an error, you notice and deal with it. But if the bits are changed, then this can be really hazardous.
https://www.npmjs.org/doc/cli/npm-publish.html
Fails if the package name and version combination already exists in the registry. Once a package is published with a given name and version, that specific name and version combination can never be used again, even if it is removed with npm-unpublish(1).
So we can not publish to npm the updates for android/amazon-fireos/windows/wp8 as they currently exist.
One idea would be to bump the version of android/amazon-fireos/windows/wp8 to 3.6.1, both in dist.a.o and in npm. And we could leave all the other platforms/tools at 3.6.0. Except that we would also need to bump those references in cordova-lib/cordova-lib/src/platforms.js, and then bump the reference in cordova-cli to use this newer cordova-lib. Not pretty, but it should work technically. Sigh.
Other ideas?
On Sep 2, 2014, at 1:26 PM, Steven Gill <st...@gmail.com> wrote:
> Actually, I like Carlos suggestion.
>
> We have already been publishing to npm under the RC tag for testing (not
> releasing to public but just for dev testing).
>
> The last few releases you could go npm install cordova@rc and that would
> download the RC version of cordova that we were voting on.
>
> I went ahead and published all of the platforms + lib + plugman + js
> (everything we are voting on) to npm under an rc tag. So npm install
> cordova-android@rc would grab version 3.6.0.
>
> The easiest way to test is to now go npm install cordova@rc. No need to
> --usegit anymore.
>
> The --usegit method would require you to checkout the tags in cordova-lib,
> cordova-js, npm link them, go to cli, npm link them, etc.
>
> -Steve
Re: [Vote] 3.6.0 Cadence Release
Posted by Steven Gill <st...@gmail.com>.
Actually, I like Carlos suggestion.
We have already been publishing to npm under the RC tag for testing (not
releasing to public but just for dev testing).
The last few releases you could go npm install cordova@rc and that would
download the RC version of cordova that we were voting on.
I went ahead and published all of the platforms + lib + plugman + js
(everything we are voting on) to npm under an rc tag. So npm install
cordova-android@rc would grab version 3.6.0.
The easiest way to test is to now go npm install cordova@rc. No need to
--usegit anymore.
The --usegit method would require you to checkout the tags in cordova-lib,
cordova-js, npm link them, go to cli, npm link them, etc.
-Steve
On Tue, Sep 2, 2014 at 10:23 AM, Parashuram Narasimhan (MS OPEN TECH) <
panarasi@microsoft.com> wrote:
> Agree with Jesse. If you still want to test it, I tried doing it with a
> private npm registry, and changed my npm to pick up from that registry. I
> did not see a lot of value added though. I did this when I was playing with
> the idea of using npm to use plugins.
>
> -----Original Message-----
> From: Jesse [mailto:purplecabbage@gmail.com]
> Sent: Tuesday, September 2, 2014 10:21 AM
> To: dev@cordova.apache.org
> Subject: Re: [Vote] 3.6.0 Cadence Release
>
> We cannot post to npm without the vote passing. There is a bunch of crazy
> overhead tag bs we could do, but then we would not be voting on the final
> released binaries.
>
> Just test with --usegit
>
>
>
> @purplecabbage
> risingj.com
>
>
> On Tue, Sep 2, 2014 at 6:47 AM, Carlos Santana <cs...@gmail.com>
> wrote:
>
> > I see cordova cli rc on npm, I want to test it using npm but I get
> errors.
> > Maybe cordova-lib should be also posted to npm but not make it latest
> > until we release.
> >
> > I get this errors:
> >
> > $ npm install cordova@rc
> >
> > npm ERR! Error: version not found: cordova-lib@0.21.8
> >
> >
> > On Tue, Sep 2, 2014 at 9:29 AM, Bryan Higgins <br...@bryanhiggins.net>
> > wrote:
> >
> > > +1
> > >
> > > - Verified signatures and hashes for cordova-blackberry
> > > - Verified sha1 match tag 3.6.0
> > > - Ran mobile spec on various BB10 devices and OS versions
> > >
> > > Steve - I added you as an owner for cordova-blackberry10 on npm. The
> > > cordova-blackberry package should probably be unpublished.
> > >
> > >
> > > On Tue, Sep 2, 2014 at 1:15 AM, Archana Naik
> > > <na...@gmail.com>
> > > wrote:
> > >
> > > > vote +1
> > > > Verified amazon-fireos bundle, signatures and hashes.
> > > >
> > > > When are we planning to publish it to npm?
> > > >
> > > >
> > > > On Mon, Sep 1, 2014 at 2:40 PM, Sergey Grebnov (Akvelon) <
> > > > v-segreb@microsoft.com> wrote:
> > > >
> > > > > I vote +1:
> > > > > * Verified signatures and hashes for cordova-cli, cordova-lib,
> > > > > cordova-plugman, cordova-windows, cordova-wp8
> > > > > * Verified sha1s match tags for cordova-cli, cordova-lib,
> > > > cordova-plugman,
> > > > > cordova-windows, cordova-wp8
> > > > > * Run Medic tests for Windows and Windows Phone 8
> > > > > * Tested Android build on Windows
> > > > > * Tested Windows platform manually
> > > > > building and running app with VS2012 (msbuild
> > > > > 4.0)/VS2013(msbuild
> > > > 12.0)
> > > > > -win and -phone switches
> > > > > support of target platform settings (config.xml)
> > > > > support of custom icons and splash screen images
> > > > >
> > > > > Thx!
> > > > > Sergey
> > > > > -----Original Message-----
> > > > > From: Steven Gill [mailto:stevengill97@gmail.com]
> > > > > Sent: Saturday, August 30, 2014 5:35 AM
> > > > > To: dev@cordova.apache.org
> > > > > Subject: [Vote] 3.6.0 Cadence Release
> > > > >
> > > > > Please review and vote on this 3.6.0 Cadence Release.
> > > > >
> > > > > Release issue: https://issues.apache.org/jira/browse/CB-7383
> > > > >
> > > > > Repos ready to be released have been published to
> > > > > dist/dev:https://dist.apache.org/repos/dist/dev/cordova/CB-7383
> > > > >
> > > > > The packages were published from their corresponding git tags:
> > > > > cordova-android: 3.6.0 (014327c59a)
> > > > > cordova-ios: 3.6.0 (3a92b2dbf0)
> > > > > cordova-blackberry: 3.6.0 (ed435bfc9e)
> > > > > cordova-windows: 3.6.0 (cdb292f4a3)
> > > > > cordova-wp8: 3.6.0 (a879f5258b)
> > > > > cordova-firefoxos: 3.6.0 (9ab176f855)
> > > > >
> > > > > cordova-ubuntu: 3.6.0 (bff472e4c2)
> > > > > cordova-amazon-fireos: 3.6.0 (4e94c6d198)
> > > > > cordova-js: 3.6.0 (906b34c0a4)
> > > > > cordova-mobile-spec: 3.6.0 (27053f7dd8)
> > > > > cordova-app-hello-world: 3.6.0 (65a2171a19)
> > > > >
> > > > > cordova-cli: 3.6.0-0.2.8 (01cb09f2d1)
> > > > > cordova-lib: 0.21.8 (14670ec9b5)
> > > > > cordova-plugman: 0.22.5 (29488fce7e)
> > > > >
> > > > >
> > > > > Upon a successful vote I will upload the archives to dist/,
> > > > > publish
> > > them
> > > > > to NPM, and post the corresponding blog post.
> > > > >
> > > > > Voting guidelines:
> > > > >
> > > >
> > >
> > https://github.com/apache/cordova-coho/blob/master/docs/release-voting
> > .md
> > > > >
> > > > > Voting will go on for a minimum of 72 hours.
> > > > >
> > > > > I vote +1:
> > > > > * Ran coho audit-license-headers over the relevant repos
> > > > > * Used `license-checker` to ensure all dependencies have
> > > > Apache-compatible
> > > > > licenses
> > > > > * Ensured continuous build was green when repos were tagged
> > > > >
> > > >
> > >
> >
> >
> >
> > --
> > Carlos Santana
> > <cs...@gmail.com>
> >
>
RE: [Vote] 3.6.0 Cadence Release
Posted by "Parashuram Narasimhan (MS OPEN TECH)" <pa...@microsoft.com>.
Agree with Jesse. If you still want to test it, I tried doing it with a private npm registry, and changed my npm to pick up from that registry. I did not see a lot of value added though. I did this when I was playing with the idea of using npm to use plugins.
-----Original Message-----
From: Jesse [mailto:purplecabbage@gmail.com]
Sent: Tuesday, September 2, 2014 10:21 AM
To: dev@cordova.apache.org
Subject: Re: [Vote] 3.6.0 Cadence Release
We cannot post to npm without the vote passing. There is a bunch of crazy overhead tag bs we could do, but then we would not be voting on the final released binaries.
Just test with --usegit
@purplecabbage
risingj.com
On Tue, Sep 2, 2014 at 6:47 AM, Carlos Santana <cs...@gmail.com> wrote:
> I see cordova cli rc on npm, I want to test it using npm but I get errors.
> Maybe cordova-lib should be also posted to npm but not make it latest
> until we release.
>
> I get this errors:
>
> $ npm install cordova@rc
>
> npm ERR! Error: version not found: cordova-lib@0.21.8
>
>
> On Tue, Sep 2, 2014 at 9:29 AM, Bryan Higgins <br...@bryanhiggins.net>
> wrote:
>
> > +1
> >
> > - Verified signatures and hashes for cordova-blackberry
> > - Verified sha1 match tag 3.6.0
> > - Ran mobile spec on various BB10 devices and OS versions
> >
> > Steve - I added you as an owner for cordova-blackberry10 on npm. The
> > cordova-blackberry package should probably be unpublished.
> >
> >
> > On Tue, Sep 2, 2014 at 1:15 AM, Archana Naik
> > <na...@gmail.com>
> > wrote:
> >
> > > vote +1
> > > Verified amazon-fireos bundle, signatures and hashes.
> > >
> > > When are we planning to publish it to npm?
> > >
> > >
> > > On Mon, Sep 1, 2014 at 2:40 PM, Sergey Grebnov (Akvelon) <
> > > v-segreb@microsoft.com> wrote:
> > >
> > > > I vote +1:
> > > > * Verified signatures and hashes for cordova-cli, cordova-lib,
> > > > cordova-plugman, cordova-windows, cordova-wp8
> > > > * Verified sha1s match tags for cordova-cli, cordova-lib,
> > > cordova-plugman,
> > > > cordova-windows, cordova-wp8
> > > > * Run Medic tests for Windows and Windows Phone 8
> > > > * Tested Android build on Windows
> > > > * Tested Windows platform manually
> > > > building and running app with VS2012 (msbuild
> > > > 4.0)/VS2013(msbuild
> > > 12.0)
> > > > -win and -phone switches
> > > > support of target platform settings (config.xml)
> > > > support of custom icons and splash screen images
> > > >
> > > > Thx!
> > > > Sergey
> > > > -----Original Message-----
> > > > From: Steven Gill [mailto:stevengill97@gmail.com]
> > > > Sent: Saturday, August 30, 2014 5:35 AM
> > > > To: dev@cordova.apache.org
> > > > Subject: [Vote] 3.6.0 Cadence Release
> > > >
> > > > Please review and vote on this 3.6.0 Cadence Release.
> > > >
> > > > Release issue: https://issues.apache.org/jira/browse/CB-7383
> > > >
> > > > Repos ready to be released have been published to
> > > > dist/dev:https://dist.apache.org/repos/dist/dev/cordova/CB-7383
> > > >
> > > > The packages were published from their corresponding git tags:
> > > > cordova-android: 3.6.0 (014327c59a)
> > > > cordova-ios: 3.6.0 (3a92b2dbf0)
> > > > cordova-blackberry: 3.6.0 (ed435bfc9e)
> > > > cordova-windows: 3.6.0 (cdb292f4a3)
> > > > cordova-wp8: 3.6.0 (a879f5258b)
> > > > cordova-firefoxos: 3.6.0 (9ab176f855)
> > > >
> > > > cordova-ubuntu: 3.6.0 (bff472e4c2)
> > > > cordova-amazon-fireos: 3.6.0 (4e94c6d198)
> > > > cordova-js: 3.6.0 (906b34c0a4)
> > > > cordova-mobile-spec: 3.6.0 (27053f7dd8)
> > > > cordova-app-hello-world: 3.6.0 (65a2171a19)
> > > >
> > > > cordova-cli: 3.6.0-0.2.8 (01cb09f2d1)
> > > > cordova-lib: 0.21.8 (14670ec9b5)
> > > > cordova-plugman: 0.22.5 (29488fce7e)
> > > >
> > > >
> > > > Upon a successful vote I will upload the archives to dist/,
> > > > publish
> > them
> > > > to NPM, and post the corresponding blog post.
> > > >
> > > > Voting guidelines:
> > > >
> > >
> >
> https://github.com/apache/cordova-coho/blob/master/docs/release-voting
> .md
> > > >
> > > > Voting will go on for a minimum of 72 hours.
> > > >
> > > > I vote +1:
> > > > * Ran coho audit-license-headers over the relevant repos
> > > > * Used `license-checker` to ensure all dependencies have
> > > Apache-compatible
> > > > licenses
> > > > * Ensured continuous build was green when repos were tagged
> > > >
> > >
> >
>
>
>
> --
> Carlos Santana
> <cs...@gmail.com>
>
Re: [Vote] 3.6.0 Cadence Release
Posted by Jesse <pu...@gmail.com>.
We cannot post to npm without the vote passing. There is a bunch of crazy
overhead tag bs we could do, but then we would not be voting on the final
released binaries.
Just test with --usegit
@purplecabbage
risingj.com
On Tue, Sep 2, 2014 at 6:47 AM, Carlos Santana <cs...@gmail.com> wrote:
> I see cordova cli rc on npm, I want to test it using npm but I get errors.
> Maybe cordova-lib should be also posted to npm but not make it latest until
> we release.
>
> I get this errors:
>
> $ npm install cordova@rc
>
> npm ERR! Error: version not found: cordova-lib@0.21.8
>
>
> On Tue, Sep 2, 2014 at 9:29 AM, Bryan Higgins <br...@bryanhiggins.net>
> wrote:
>
> > +1
> >
> > - Verified signatures and hashes for cordova-blackberry
> > - Verified sha1 match tag 3.6.0
> > - Ran mobile spec on various BB10 devices and OS versions
> >
> > Steve - I added you as an owner for cordova-blackberry10 on npm. The
> > cordova-blackberry package should probably be unpublished.
> >
> >
> > On Tue, Sep 2, 2014 at 1:15 AM, Archana Naik <na...@gmail.com>
> > wrote:
> >
> > > vote +1
> > > Verified amazon-fireos bundle, signatures and hashes.
> > >
> > > When are we planning to publish it to npm?
> > >
> > >
> > > On Mon, Sep 1, 2014 at 2:40 PM, Sergey Grebnov (Akvelon) <
> > > v-segreb@microsoft.com> wrote:
> > >
> > > > I vote +1:
> > > > * Verified signatures and hashes for cordova-cli, cordova-lib,
> > > > cordova-plugman, cordova-windows, cordova-wp8
> > > > * Verified sha1s match tags for cordova-cli, cordova-lib,
> > > cordova-plugman,
> > > > cordova-windows, cordova-wp8
> > > > * Run Medic tests for Windows and Windows Phone 8
> > > > * Tested Android build on Windows
> > > > * Tested Windows platform manually
> > > > building and running app with VS2012 (msbuild 4.0)/VS2013(msbuild
> > > 12.0)
> > > > -win and -phone switches
> > > > support of target platform settings (config.xml)
> > > > support of custom icons and splash screen images
> > > >
> > > > Thx!
> > > > Sergey
> > > > -----Original Message-----
> > > > From: Steven Gill [mailto:stevengill97@gmail.com]
> > > > Sent: Saturday, August 30, 2014 5:35 AM
> > > > To: dev@cordova.apache.org
> > > > Subject: [Vote] 3.6.0 Cadence Release
> > > >
> > > > Please review and vote on this 3.6.0 Cadence Release.
> > > >
> > > > Release issue: https://issues.apache.org/jira/browse/CB-7383
> > > >
> > > > Repos ready to be released have been published to
> > > > dist/dev:https://dist.apache.org/repos/dist/dev/cordova/CB-7383
> > > >
> > > > The packages were published from their corresponding git tags:
> > > > cordova-android: 3.6.0 (014327c59a)
> > > > cordova-ios: 3.6.0 (3a92b2dbf0)
> > > > cordova-blackberry: 3.6.0 (ed435bfc9e)
> > > > cordova-windows: 3.6.0 (cdb292f4a3)
> > > > cordova-wp8: 3.6.0 (a879f5258b)
> > > > cordova-firefoxos: 3.6.0 (9ab176f855)
> > > >
> > > > cordova-ubuntu: 3.6.0 (bff472e4c2)
> > > > cordova-amazon-fireos: 3.6.0 (4e94c6d198)
> > > > cordova-js: 3.6.0 (906b34c0a4)
> > > > cordova-mobile-spec: 3.6.0 (27053f7dd8)
> > > > cordova-app-hello-world: 3.6.0 (65a2171a19)
> > > >
> > > > cordova-cli: 3.6.0-0.2.8 (01cb09f2d1)
> > > > cordova-lib: 0.21.8 (14670ec9b5)
> > > > cordova-plugman: 0.22.5 (29488fce7e)
> > > >
> > > >
> > > > Upon a successful vote I will upload the archives to dist/, publish
> > them
> > > > to NPM, and post the corresponding blog post.
> > > >
> > > > Voting guidelines:
> > > >
> > >
> >
> https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md
> > > >
> > > > Voting will go on for a minimum of 72 hours.
> > > >
> > > > I vote +1:
> > > > * Ran coho audit-license-headers over the relevant repos
> > > > * Used `license-checker` to ensure all dependencies have
> > > Apache-compatible
> > > > licenses
> > > > * Ensured continuous build was green when repos were tagged
> > > >
> > >
> >
>
>
>
> --
> Carlos Santana
> <cs...@gmail.com>
>
Re: [Vote] 3.6.0 Cadence Release
Posted by Carlos Santana <cs...@gmail.com>.
I see cordova cli rc on npm, I want to test it using npm but I get errors.
Maybe cordova-lib should be also posted to npm but not make it latest until
we release.
I get this errors:
$ npm install cordova@rc
npm ERR! Error: version not found: cordova-lib@0.21.8
On Tue, Sep 2, 2014 at 9:29 AM, Bryan Higgins <br...@bryanhiggins.net>
wrote:
> +1
>
> - Verified signatures and hashes for cordova-blackberry
> - Verified sha1 match tag 3.6.0
> - Ran mobile spec on various BB10 devices and OS versions
>
> Steve - I added you as an owner for cordova-blackberry10 on npm. The
> cordova-blackberry package should probably be unpublished.
>
>
> On Tue, Sep 2, 2014 at 1:15 AM, Archana Naik <na...@gmail.com>
> wrote:
>
> > vote +1
> > Verified amazon-fireos bundle, signatures and hashes.
> >
> > When are we planning to publish it to npm?
> >
> >
> > On Mon, Sep 1, 2014 at 2:40 PM, Sergey Grebnov (Akvelon) <
> > v-segreb@microsoft.com> wrote:
> >
> > > I vote +1:
> > > * Verified signatures and hashes for cordova-cli, cordova-lib,
> > > cordova-plugman, cordova-windows, cordova-wp8
> > > * Verified sha1s match tags for cordova-cli, cordova-lib,
> > cordova-plugman,
> > > cordova-windows, cordova-wp8
> > > * Run Medic tests for Windows and Windows Phone 8
> > > * Tested Android build on Windows
> > > * Tested Windows platform manually
> > > building and running app with VS2012 (msbuild 4.0)/VS2013(msbuild
> > 12.0)
> > > -win and -phone switches
> > > support of target platform settings (config.xml)
> > > support of custom icons and splash screen images
> > >
> > > Thx!
> > > Sergey
> > > -----Original Message-----
> > > From: Steven Gill [mailto:stevengill97@gmail.com]
> > > Sent: Saturday, August 30, 2014 5:35 AM
> > > To: dev@cordova.apache.org
> > > Subject: [Vote] 3.6.0 Cadence Release
> > >
> > > Please review and vote on this 3.6.0 Cadence Release.
> > >
> > > Release issue: https://issues.apache.org/jira/browse/CB-7383
> > >
> > > Repos ready to be released have been published to
> > > dist/dev:https://dist.apache.org/repos/dist/dev/cordova/CB-7383
> > >
> > > The packages were published from their corresponding git tags:
> > > cordova-android: 3.6.0 (014327c59a)
> > > cordova-ios: 3.6.0 (3a92b2dbf0)
> > > cordova-blackberry: 3.6.0 (ed435bfc9e)
> > > cordova-windows: 3.6.0 (cdb292f4a3)
> > > cordova-wp8: 3.6.0 (a879f5258b)
> > > cordova-firefoxos: 3.6.0 (9ab176f855)
> > >
> > > cordova-ubuntu: 3.6.0 (bff472e4c2)
> > > cordova-amazon-fireos: 3.6.0 (4e94c6d198)
> > > cordova-js: 3.6.0 (906b34c0a4)
> > > cordova-mobile-spec: 3.6.0 (27053f7dd8)
> > > cordova-app-hello-world: 3.6.0 (65a2171a19)
> > >
> > > cordova-cli: 3.6.0-0.2.8 (01cb09f2d1)
> > > cordova-lib: 0.21.8 (14670ec9b5)
> > > cordova-plugman: 0.22.5 (29488fce7e)
> > >
> > >
> > > Upon a successful vote I will upload the archives to dist/, publish
> them
> > > to NPM, and post the corresponding blog post.
> > >
> > > Voting guidelines:
> > >
> >
> https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md
> > >
> > > Voting will go on for a minimum of 72 hours.
> > >
> > > I vote +1:
> > > * Ran coho audit-license-headers over the relevant repos
> > > * Used `license-checker` to ensure all dependencies have
> > Apache-compatible
> > > licenses
> > > * Ensured continuous build was green when repos were tagged
> > >
> >
>
--
Carlos Santana
<cs...@gmail.com>
Re: [Vote] 3.6.0 Cadence Release
Posted by Bryan Higgins <br...@bryanhiggins.net>.
+1
- Verified signatures and hashes for cordova-blackberry
- Verified sha1 match tag 3.6.0
- Ran mobile spec on various BB10 devices and OS versions
Steve - I added you as an owner for cordova-blackberry10 on npm. The
cordova-blackberry package should probably be unpublished.
On Tue, Sep 2, 2014 at 1:15 AM, Archana Naik <na...@gmail.com> wrote:
> vote +1
> Verified amazon-fireos bundle, signatures and hashes.
>
> When are we planning to publish it to npm?
>
>
> On Mon, Sep 1, 2014 at 2:40 PM, Sergey Grebnov (Akvelon) <
> v-segreb@microsoft.com> wrote:
>
> > I vote +1:
> > * Verified signatures and hashes for cordova-cli, cordova-lib,
> > cordova-plugman, cordova-windows, cordova-wp8
> > * Verified sha1s match tags for cordova-cli, cordova-lib,
> cordova-plugman,
> > cordova-windows, cordova-wp8
> > * Run Medic tests for Windows and Windows Phone 8
> > * Tested Android build on Windows
> > * Tested Windows platform manually
> > building and running app with VS2012 (msbuild 4.0)/VS2013(msbuild
> 12.0)
> > -win and -phone switches
> > support of target platform settings (config.xml)
> > support of custom icons and splash screen images
> >
> > Thx!
> > Sergey
> > -----Original Message-----
> > From: Steven Gill [mailto:stevengill97@gmail.com]
> > Sent: Saturday, August 30, 2014 5:35 AM
> > To: dev@cordova.apache.org
> > Subject: [Vote] 3.6.0 Cadence Release
> >
> > Please review and vote on this 3.6.0 Cadence Release.
> >
> > Release issue: https://issues.apache.org/jira/browse/CB-7383
> >
> > Repos ready to be released have been published to
> > dist/dev:https://dist.apache.org/repos/dist/dev/cordova/CB-7383
> >
> > The packages were published from their corresponding git tags:
> > cordova-android: 3.6.0 (014327c59a)
> > cordova-ios: 3.6.0 (3a92b2dbf0)
> > cordova-blackberry: 3.6.0 (ed435bfc9e)
> > cordova-windows: 3.6.0 (cdb292f4a3)
> > cordova-wp8: 3.6.0 (a879f5258b)
> > cordova-firefoxos: 3.6.0 (9ab176f855)
> >
> > cordova-ubuntu: 3.6.0 (bff472e4c2)
> > cordova-amazon-fireos: 3.6.0 (4e94c6d198)
> > cordova-js: 3.6.0 (906b34c0a4)
> > cordova-mobile-spec: 3.6.0 (27053f7dd8)
> > cordova-app-hello-world: 3.6.0 (65a2171a19)
> >
> > cordova-cli: 3.6.0-0.2.8 (01cb09f2d1)
> > cordova-lib: 0.21.8 (14670ec9b5)
> > cordova-plugman: 0.22.5 (29488fce7e)
> >
> >
> > Upon a successful vote I will upload the archives to dist/, publish them
> > to NPM, and post the corresponding blog post.
> >
> > Voting guidelines:
> >
> https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md
> >
> > Voting will go on for a minimum of 72 hours.
> >
> > I vote +1:
> > * Ran coho audit-license-headers over the relevant repos
> > * Used `license-checker` to ensure all dependencies have
> Apache-compatible
> > licenses
> > * Ensured continuous build was green when repos were tagged
> >
>
Re: [Vote] 3.6.0 Cadence Release
Posted by Archana Naik <na...@gmail.com>.
vote +1
Verified amazon-fireos bundle, signatures and hashes.
When are we planning to publish it to npm?
On Mon, Sep 1, 2014 at 2:40 PM, Sergey Grebnov (Akvelon) <
v-segreb@microsoft.com> wrote:
> I vote +1:
> * Verified signatures and hashes for cordova-cli, cordova-lib,
> cordova-plugman, cordova-windows, cordova-wp8
> * Verified sha1s match tags for cordova-cli, cordova-lib, cordova-plugman,
> cordova-windows, cordova-wp8
> * Run Medic tests for Windows and Windows Phone 8
> * Tested Android build on Windows
> * Tested Windows platform manually
> building and running app with VS2012 (msbuild 4.0)/VS2013(msbuild 12.0)
> -win and -phone switches
> support of target platform settings (config.xml)
> support of custom icons and splash screen images
>
> Thx!
> Sergey
> -----Original Message-----
> From: Steven Gill [mailto:stevengill97@gmail.com]
> Sent: Saturday, August 30, 2014 5:35 AM
> To: dev@cordova.apache.org
> Subject: [Vote] 3.6.0 Cadence Release
>
> Please review and vote on this 3.6.0 Cadence Release.
>
> Release issue: https://issues.apache.org/jira/browse/CB-7383
>
> Repos ready to be released have been published to
> dist/dev:https://dist.apache.org/repos/dist/dev/cordova/CB-7383
>
> The packages were published from their corresponding git tags:
> cordova-android: 3.6.0 (014327c59a)
> cordova-ios: 3.6.0 (3a92b2dbf0)
> cordova-blackberry: 3.6.0 (ed435bfc9e)
> cordova-windows: 3.6.0 (cdb292f4a3)
> cordova-wp8: 3.6.0 (a879f5258b)
> cordova-firefoxos: 3.6.0 (9ab176f855)
>
> cordova-ubuntu: 3.6.0 (bff472e4c2)
> cordova-amazon-fireos: 3.6.0 (4e94c6d198)
> cordova-js: 3.6.0 (906b34c0a4)
> cordova-mobile-spec: 3.6.0 (27053f7dd8)
> cordova-app-hello-world: 3.6.0 (65a2171a19)
>
> cordova-cli: 3.6.0-0.2.8 (01cb09f2d1)
> cordova-lib: 0.21.8 (14670ec9b5)
> cordova-plugman: 0.22.5 (29488fce7e)
>
>
> Upon a successful vote I will upload the archives to dist/, publish them
> to NPM, and post the corresponding blog post.
>
> Voting guidelines:
> https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md
>
> Voting will go on for a minimum of 72 hours.
>
> I vote +1:
> * Ran coho audit-license-headers over the relevant repos
> * Used `license-checker` to ensure all dependencies have Apache-compatible
> licenses
> * Ensured continuous build was green when repos were tagged
>
RE: [Vote] 3.6.0 Cadence Release
Posted by "Sergey Grebnov (Akvelon)" <v-...@microsoft.com>.
I vote +1:
* Verified signatures and hashes for cordova-cli, cordova-lib, cordova-plugman, cordova-windows, cordova-wp8
* Verified sha1s match tags for cordova-cli, cordova-lib, cordova-plugman, cordova-windows, cordova-wp8
* Run Medic tests for Windows and Windows Phone 8
* Tested Android build on Windows
* Tested Windows platform manually
building and running app with VS2012 (msbuild 4.0)/VS2013(msbuild 12.0)
-win and -phone switches
support of target platform settings (config.xml)
support of custom icons and splash screen images
Thx!
Sergey
-----Original Message-----
From: Steven Gill [mailto:stevengill97@gmail.com]
Sent: Saturday, August 30, 2014 5:35 AM
To: dev@cordova.apache.org
Subject: [Vote] 3.6.0 Cadence Release
Please review and vote on this 3.6.0 Cadence Release.
Release issue: https://issues.apache.org/jira/browse/CB-7383
Repos ready to be released have been published to
dist/dev:https://dist.apache.org/repos/dist/dev/cordova/CB-7383
The packages were published from their corresponding git tags:
cordova-android: 3.6.0 (014327c59a)
cordova-ios: 3.6.0 (3a92b2dbf0)
cordova-blackberry: 3.6.0 (ed435bfc9e)
cordova-windows: 3.6.0 (cdb292f4a3)
cordova-wp8: 3.6.0 (a879f5258b)
cordova-firefoxos: 3.6.0 (9ab176f855)
cordova-ubuntu: 3.6.0 (bff472e4c2)
cordova-amazon-fireos: 3.6.0 (4e94c6d198)
cordova-js: 3.6.0 (906b34c0a4)
cordova-mobile-spec: 3.6.0 (27053f7dd8)
cordova-app-hello-world: 3.6.0 (65a2171a19)
cordova-cli: 3.6.0-0.2.8 (01cb09f2d1)
cordova-lib: 0.21.8 (14670ec9b5)
cordova-plugman: 0.22.5 (29488fce7e)
Upon a successful vote I will upload the archives to dist/, publish them to NPM, and post the corresponding blog post.
Voting guidelines:
https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md
Voting will go on for a minimum of 72 hours.
I vote +1:
* Ran coho audit-license-headers over the relevant repos
* Used `license-checker` to ensure all dependencies have Apache-compatible licenses
* Ensured continuous build was green when repos were tagged