cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marcel Kinard <>
Subject Re: [Vote] 3.6.1 Cadence Release 3rd attempt
Date Fri, 12 Sep 2014 16:42:41 GMT
I just finished moving the "latest" tag in npm to the 3.5.x version of platforms and tools,
following on what Bryan did yesterday. Shouldn't matter since the CLI does pinning, but better
to be consistent.

Here is my plan to deal with CB-7526, basically a do-over:

0) uninstall node v0.11 from my workstation and upgrade to the latest v0.10.
1) bump the versions in all the package.json, VERSION, and related files for platforms so
that a new version can be published to npm without the shasum bug. Since cordova-js was already
at 3.6.3 and is fine in the npm repo, would be nice to have all the platform versions line
up to the js as 3.6.3 instead of using 3.6.2 there.
2) bump the versions in cordova-lib/.../platforms.js to reference the platform versions from
step #1. And bump the version in cordova-lib/package.json.
3) bump the version in cordova-cli/package.json to reference the cordova-lib version from
step #2.
4) create the tarballs and post them to dist-dev
5) start a new vote thread titled "3.6.3 platforms and tools"
6) npm unpublish the 3.6.1 platforms that are stored with the hosed shasum, since they'll
never install correctly anyway.
7) prep cordova-docs with the new version "3.6.0" (i.e., en/3.6.0) instead of what I previously
did as "3.6.1" (i.e., en/3.6.1)
7) follow the rest of the cadence release process

Let me know if you have any other suggestions or ideas.

On Sep 12, 2014, at 7:29 AM, Marcel Kinard <> wrote:

> See
> Looks like a do-over.
> On Sep 12, 2014, at 1:28 AM, Andrey Kurdumov <> wrote:
>> On the StackOverflow recently posted following question
>> Looks like it is related to recent release
>> 2014-09-12 5:39 GMT+06:00 Bryan Higgins <>:
>>> I've pointed latest back to 3.5.0-0.2.7 for now.
>>> On Thu, Sep 11, 2014 at 6:29 PM, Bryan Higgins <>
>>> wrote:
>>>> My inbox is getting flooded with reports of this issue:
>>>> npm http 200
>>>> Unable to fetch platform blackberry10: Error: shasum check failed for
>>> /var/folders/dk/f9mzz67s72s0lzsv2b92ccwm0000gn/T/npm-28823-kUnITCqE/1410474423022-0.06607100926339626/tmp.tgz
>>>> Expected: 768267141f7716a3745073227b82ee654bea3371
>>>> Actual:   a3e007d3730d20b9711f004fb2da9a3528d1175c
>>>> It appears to affect all platforms.
>>>> Anything I can do to help? Can we point latest to 3.5 until this is
>>>> resolved?

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