Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (athena.apache.org: domain of cmarcelk@gmail.com designates
 209.85.223.171 as permitted sender)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: [DISCUSS] shrinkwrap
From: Marcel Kinard <cmarcelk@gmail.com>
In-Reply-To: 
 <CABiQX1Xw91po=GY14G+L02dW6UUPGNK1++u2Cqc7=Yajs6n=hw@mail.gmail.com>
Date: Wed, 1 Oct 2014 16:46:14 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <715D6554-2072-4175-B857-00D010F926F6@gmail.com>
References: <62368B3C-70D3-4ED3-B470-8BFFD1DF2EDB@gmail.com>
 <CA+GVa3bKbJ4bbmVi+mi3fk1ej1q3uqfNkRdGwp41ZSci+vA8Ag@mail.gmail.com>
 <7ef63ff7ae6f4986a7d96fd47b690437@DM2PR03MB366.namprd03.prod.outlook.com>
 <87566401-D50F-44A8-B42A-442A9325EAD0@gmail.com>
 <CADVgkyOUD5Y6S+vA7QF8hNu=J25o0w+S3Wh_2QzAiq4CiRDVQA@mail.gmail.com>
 <CAHYtTqnizpMnTT04NxR1Y20EEvMKA-5wX=BUXL7mSmbsjW0BkA@mail.gmail.com>
 <CADVgkyMKiaYO+MPJc9L-JDjW4=eZ-Y1Hu7A8pWC9d6JoGamgPA@mail.gmail.com>
 <CAHYtTqmNqjLwbue_edsMKWCSE_Yabnrc2-yaEdrsoK=-Pmsnyg@mail.gmail.com>
 <CADVgkyOc0aCL7rRw2tzzyiveqU_C6CN_iN1wYod2jim+s-qKEw@mail.gmail.com>
 <CAHYtTqnsnO+CfYw_igvFj7pGXNKcLHZ3Fgt_tJAjv_rSuzVvsg@mail.gmail.com>
 <CAHYtTqmzFeStiBP8gPQOVU6R4Am8O4Y8cvO=Nj3G9rBsQsxhag@mail.gmail.com>
 <CABiQX1VYp-YkroBCtXK3py=Z6mxPR3gnvpk6JfaeWfF6+_=Jpw@mail.gmail.com>
 <55ED2FC4-F04D-4E13-B345-26D1EB89F32D@gmail.com>
 <CAKP6k2tEJWoedrOtkNMs68dobzi05U9gx9UG39pJm09EJ=p8jw@mail.gmail.com>
 <CABiQX1X36CORNQdYfv=t=saurSVenTeE_18hUQoPY-7fyUhWYA@mail.gmail.com>
 <CAMSbhBgR_XFFsiLPY8rN5K6c8UFn+GWq6Z5n6MqYbgZ44yyq0Q@mail.gmail.com>
 <D051D599.4B85E%jsoref@blackberry.com>
 <CABiQX1Xw91po=GY14G+L02dW6UUPGNK1++u2Cqc7=Yajs6n=hw@mail.gmail.com>
To: dev@cordova.apache.org

=46rom my scars of the last release, what I'd suggest as closer to the =
ideal of "benefits of shrinkwrap with a lower cost" would be to publish =
to a private npm repo and use something like the --registry flag to =
test. Using a private registry would also give us the opportunity to =
wipe any published packages in case a republish is needed, to avoid =
bumping the version numbers.  =
https://issues.apache.org/jira/browse/CB-7550

Until we have a private registry for release testing, I agree with Steve =
that rc's should not be published to npm, and instead use --usegit.

On Oct 1, 2014, at 4:25 PM, Andrew Grieve <agrieve@chromium.org> wrote:

> The root of what I meant I guess, was that if shrinkwrap doesn't work
> without publishing, then let's just publish and don't sweat version =
numbers
> jumping by more than one. If we can get shrinkwrap to work through =
another
> means (private npm repo?), than that's even better.
>=20
> On Wed, Oct 1, 2014 at 4:00 PM, Josh Soref <jsoref@blackberry.com> =
wrote:
>=20
>> Steven Gill wrote:
>>> we can test platform rc's with --usegit and
>>> eventually a private npm registry for testing.
>>=20
>> +1
>>=20
>>=20