Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (nike.apache.org: domain of mmocny@google.com designates
 209.85.213.179 as permitted sender)
MIME-Version: 1.0
Sender: mmocny@google.com
In-Reply-To: <96F42AB2-65A8-40DF-B2C6-1C2F60AF38F0@gmail.com>
References: 
 <CAMSbhBjGFj8bb8C4Ef3MYkcef4-RV94W_ppSC=6+b7fo4Y_E6w@mail.gmail.com>
 <544a543dd5114abe89931eae4e3f1100@BL2PR03MB417.namprd03.prod.outlook.com>
 <CAFQxR399MSmCDFU=CBH3Q9yU9mk77+t0UyHQy4T-Re=V1GRCaA@mail.gmail.com>
 <CAEeRA4qHPZJo5sTL8=nac0ngRTxHDUVdHEO+5QkYcZ4cPDucgg@mail.gmail.com>
 <CAHYtTq=TPo0s8sSvwEyX+sp5ioBcmSLGUvuqoiwDmW0hHtbVhQ@mail.gmail.com>
 <CAKP6k2tkd8LPNhPBgcA3-qMSLdyoQgBJTnyKGpMCJahziGE6CA@mail.gmail.com>
 <9310671801da43488cc53c75787777ee@DM2PR03MB366.namprd03.prod.outlook.com>
 <CAMSbhBjcj8_wRWuSSrGnSTghsjOrTnoJgN8XVNvh=aBMKcm4yg@mail.gmail.com>
 <E04E213F-9A30-4342-93B7-D600695B70A1@gmail.com>
 <96F42AB2-65A8-40DF-B2C6-1C2F60AF38F0@gmail.com>
From: Michal Mocny <mmocny@chromium.org>
Date: Thu, 4 Sep 2014 15:13:22 -0400
Message-ID: 
 <CAEeF2TebY_7ryc4w3cA7uE5GbFXBsqAmUm2GE6YvzHh+FHz68A@mail.gmail.com>
Subject: Re: [Vote] 3.6.0 Cadence Release
To: dev <dev@cordova.apache.org>
Content-Type: multipart/alternative; boundary=089e0149bf94a1e5e9050242264e

--089e0149bf94a1e5e9050242264e
Content-Type: text/plain; charset=UTF-8

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 <cmarcelk@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.

--089e0149bf94a1e5e9050242264e--