From 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 <agri...@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. > > On Wed, Oct 1, 2014 at 4:00 PM, Josh Soref <jso...@blackberry.com> wrote: > >> Steven Gill wrote: >>> we can test platform rc's with --usegit and >>> eventually a private npm registry for testing. >> >> +1 >> >>
