[
https://issues.apache.org/jira/browse/CB-7550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Kinard updated CB-7550:
------------------------------
Description:
Given the "npm publish" problems during the 3.6 release, it might be helpful to
have a private npm registry to which we could replicate from registry.npmjs.org
and then do a test publish and a test "npm install". And do all that before
publishing it to the real npm registry.
And having a private registry would give us a chance to wipe content from it to
republish any new rc's without having to bump version numbers.
Implementing this private npm registry as a Vagrant VM might be a nice way to
do this.
was:
Given the "npm publish" problems during the 3.6 release, it might be helpful to
have a private npm registry to which we could replicate from registry.npmjs.org
and then do a test publish and a test "npm install". And do all that before
publishing it to the real npm registry.
Implementing this private npm registry as a Vagrant VM might be a nice way to
do this.
> define a Vagrant vm to test npm publishing
> ------------------------------------------
>
> Key: CB-7550
> URL: https://issues.apache.org/jira/browse/CB-7550
> Project: Apache Cordova
> Issue Type: Improvement
> Components: Coho
> Reporter: Marcel Kinard
> Priority: Minor
>
> Given the "npm publish" problems during the 3.6 release, it might be helpful
> to have a private npm registry to which we could replicate from
> registry.npmjs.org and then do a test publish and a test "npm install". And
> do all that before publishing it to the real npm registry.
> And having a private registry would give us a chance to wipe content from it
> to republish any new rc's without having to bump version numbers.
> Implementing this private npm registry as a Vagrant VM might be a nice way to
> do this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
