cordova-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [2/2] git commit: test the rc's in npm before moving the tag to "latest"
Date Mon, 15 Sep 2014 17:00:22 GMT
test the rc's in npm before moving the tag to "latest"


Branch: refs/heads/master
Commit: 91cb46f59146473094880175c0110d301d0260ef
Parents: 47cfd76
Author: Marcel Kinard <>
Authored: Mon Sep 15 12:58:50 2014 -0400
Committer: Marcel Kinard <>
Committed: Mon Sep 15 12:58:50 2014 -0400

 docs/ | 11 +++++++++++
 1 file changed, 11 insertions(+)
diff --git a/docs/ b/docs/
index fedca45..1323ce8 100644
--- a/docs/
+++ b/docs/
@@ -338,8 +338,19 @@ publish one package at a time
 Note: You need to be an owner for each of these repos and the versions can't already have
been published. You want to publish with the rc tag, so you can move everything to "latest"
all at once after they have all been published.
+Do a quick test of the rc version
+    npm -g uninstall cordova
+    npm -g install cordova@rc
+    cordova create mytest com.example.mytest MyTest
+    cd mytest
+    cordova platform add android
+    cordova plugin add org.apache.cordova.device
+    cordova run android
 Tag this new version in npm as the latest
+    npm tag cordova@3.6.0-0.2.8 latest
     npm tag cordova-android@3.6.0 latest
 Repeat the tagging as "latest" for all the npm packages. You can check your work by running
"npm info cordova-android" and look at the value for 'dist-tags'.

View raw message