Argh, I discovered that cordova-lib/cordova-lib/src/cordova/platforms.js hadn't
been updated to 3.6.1. I'll update the coho docs, update platforms.js, generate
a new archive, and start a new vote thread with the updated tag/hash. And there
is a typo in this subject line :-/
This vote thread is
/165863134c31f4203c2bdbee6f5720baf48fee17
Thx!
Sergey
-Original Message-
From: Marcel Kinard [mailto:cmarc...@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
Marcel, thanks a lot!
-Original Message-
From: Marcel Kinard [mailto:cmarc...@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
I will get to this today.
On Sep 3, 2014, at 7:42 PM, Jesse purplecabb...@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
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
Oops, I'll sort this mess out now.
@purplecabbage
risingj.com
On Thu, Sep 4, 2014 at 8:23 AM, Marcel Kinard cmarc...@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
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 purplecabb...@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 cmarc...@gmail.com
That looks better. Thanks!
On Sep 4, 2014, at 12:05 PM, Jesse purplecabb...@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 purplecabb...@gmail.com wrote:
Oops, I'll sort this mess out
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
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
On Thu, Sep 4, 2014 at 10:26 AM, Josh Soref jso...@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
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
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*'
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 jso...@blackberry.com wrote:
If you want to, now is the time.
On Sep 4, 2014, at 1:33 PM, Joe Bowser bows...@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
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 jso...@blackberry.com wrote:
Joe Bowser wrote:
So, should we also fix this before the release? I'm thinking we probably
should:
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.
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 jso...@blackberry.com wrote:
Joe Bowser wrote:
I think we do ship the native tests.
You do. They
I updated the archive in dist-dev with this new content and tag.
On Sep 4, 2014, at 2:19 PM, Joe Bowser bows...@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,
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,
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 cmarc...@gmail.com wrote:
One idea would be to bump the
We need to have a second registry for staging instead of the official one.
On 9/4/14, 3:13 PM, Michal Mocny mmo...@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
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
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
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:
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 purplecabb...@gmail.com wrote:
Moving to a 3.6.1 sounds
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
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
I agree with all of Marcel's suggestions.
@purplecabbage
risingj.com
On Thu, Sep 4, 2014 at 12:54 PM, Marcel Kinard cmarc...@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
Sounds good.
On Thu, Sep 4, 2014 at 12:59 PM, Jesse purplecabb...@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 cmarc...@gmail.com wrote:
Here is more specifics on what I'd suggest:
- on the
0.0.1rc1
0.0.1rc2
no?
On Thu, Sep 4, 2014 at 12:54 PM, Marcel Kinard cmarc...@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
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 cmarc...@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 cmarc...@gmail.com wrote:
Here is more specifics on what I'd suggest:
- on
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
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
#1 I see that cordova-windows and cordova-wp8 are still 3.5.0 here
https://dist.apache.org/repos/dist/dev/cordova/CB-7383/
And the '[Release + 3.6.0] Test Tag 3.6.0 for Windows Phone 7 8' issue is
still opened. Does this mean that that cordova-wp8 package has not been created
yet? Asking due
Sergey wrote:
#2 cordova-wp8 distributed to npm has 'node_modules' folder missing so fails
to install (this is due to 'npm pack' specific logic which removed this
folder, we should move node_modules to bin, will push a fix for this in
master soon).
No need for that, just add
Thx, Josh! Another reason of moving node_modules to bin was consistency with
Android and Windows.
Thx!
Sergey
-Original Message-
From: Josh Soref [mailto:jso...@blackberry.com]
Sent: Wednesday, September 3, 2014 3:21 PM
To: Cordova Dev
Subject: Re: [Vote] 3.6.0 Cadence Release (attempt
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 stevengil...@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
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 cmarc...@gmail.com wrote:
So the last thing holding back a new vote thread is a
Could Sergey or Staci help out? If your time runs out, what specifically is
left?
On Sep 3, 2014, at 1:42 PM, Jesse purplecabb...@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
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:cmarc...@gmail.com]
Sent: Wednesday, September 3, 2014 2:16 PM
To: dev@cordova.apache.org
Subject: Re: [Vote] 3.6.0 Cadence Release
Message-
From: Marcel Kinard [mailto:cmarc...@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
...@blackberry.com]
Sent: Wednesday, September 3, 2014 3:21 PM
To: Cordova Dev
Subject: Re: [Vote] 3.6.0 Cadence Release (attempt 2)
Sergey wrote:
#2 cordova-wp8 distributed to npm has 'node_modules' folder missing so
fails to install (this is due to 'npm pack' specific logic which removed
! Another reason of moving node_modules to bin was consistency
with Android and Windows.
Thx!
Sergey
-Original Message-
From: Josh Soref [mailto:jso...@blackberry.com]
Sent: Wednesday, September 3, 2014 3:21 PM
To: Cordova Dev
Subject: Re: [Vote] 3.6.0 Cadence Release (attempt
:
Thx, Josh! Another reason of moving node_modules to bin was consistency
with Android and Windows.
Thx!
Sergey
-Original Message-
From: Josh Soref [mailto:jso...@blackberry.com]
Sent: Wednesday, September 3, 2014 3:21 PM
To: Cordova Dev
Subject: Re: [Vote] 3.6.0
-Original Message-
From: Josh Soref [mailto:jso...@blackberry.com]
Sent: Wednesday, September 3, 2014 3:21 PM
To: Cordova Dev
Subject: Re: [Vote] 3.6.0 Cadence Release (attempt 2)
Sergey wrote:
#2 cordova-wp8 distributed to npm has 'node_modules' folder missing
so
is in a different time zone. Do we
know a list of things remaining ?
-Original Message-
From: Marcel Kinard [mailto:cmarc...@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
+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,
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,
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 csantan...@gmail.com wrote:
: Jesse [mailto:purplecabb...@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
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
: 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
, 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
was playing
with
the idea of using npm to use plugins.
-Original Message-
From: Jesse [mailto:purplecabb...@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
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:purplecabb...@gmail.com]
Sent: Tuesday, September 2, 2014 10:21 AM
To: dev@cordova.apache.org
Subject: Re: [Vote] 3.6.0
...@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
@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
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 stevengil...@gmail.com wrote:
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 /
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
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
or someone else will be able to accomplish this?
Thx!
Sergey
-Original Message-
From: Steven Gill [mailto:stevengil...@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
this?
Thx!
Sergey
-Original Message-
From: Steven Gill [mailto:stevengil...@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
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 purplecabb...@gmail.com wrote:
Yes. I can do that.
@purplecabbage
risingj.com
On Tue, Sep 2, 2014 at 12:44 PM, Steven Gill stevengil...@gmail.com wrote:
I will get the
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 cmarc...@gmail.com wrote:
I would also be willing to do it, so feel free to use me now or in the
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
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-seg...@microsoft.com wrote:
I vote +1:
* Verified signatures and hashes for cordova-cli, cordova-lib,
cordova-plugman,
69 matches
Mail list logo
