cordova-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ste...@apache.org
Subject git commit: Fixing todos
Date Tue, 08 Apr 2014 23:31:10 GMT
Repository: cordova-coho
Updated Branches:
  refs/heads/master 22087c798 -> 69cb6620b


Fixing todos

Project: http://git-wip-us.apache.org/repos/asf/cordova-coho/repo
Commit: http://git-wip-us.apache.org/repos/asf/cordova-coho/commit/69cb6620
Tree: http://git-wip-us.apache.org/repos/asf/cordova-coho/tree/69cb6620
Diff: http://git-wip-us.apache.org/repos/asf/cordova-coho/diff/69cb6620

Branch: refs/heads/master
Commit: 69cb6620b151bbf401f7f29fbdb285bccc80923e
Parents: 22087c7
Author: Steve Gill <stevengill97@gmail.com>
Authored: Tue Apr 8 17:30:23 2014 -0600
Committer: Steve Gill <stevengill97@gmail.com>
Committed: Tue Apr 8 17:30:23 2014 -0600

----------------------------------------------------------------------
 docs/tools-release-process.md | 14 +++-----------
 1 file changed, 3 insertions(+), 11 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/cordova-coho/blob/69cb6620/docs/tools-release-process.md
----------------------------------------------------------------------
diff --git a/docs/tools-release-process.md b/docs/tools-release-process.md
index acf09c2..f268d57 100644
--- a/docs/tools-release-process.md
+++ b/docs/tools-release-process.md
@@ -8,18 +8,8 @@ Plugman and CLI are released at most weekly (see: [versioning-and-release-strate
 
 A tools release is performed by a single person each week. We call this person the "Release
Manager". How to select the Release Manager is still TDB.
 
-TODO: add in RAT instruction (via coho) for next release
-
-TODO: use npm pack instead of git archive (and have testers npm install path/to/archive.tgz)
-
 TODO: Use perl instead of sed in these commands so they work on Linux.
 
-TODO: We may want to be using [signed tags](http://git-scm.com/book/en/Git-Basics-Tagging),
or at least annotated tags.
-
-TODO: Get blog post reviewed via GDocs / online collaborative markdown site?
-
-TODO: Add step about ensuring npm owner
-
 ## Get Buy-in
 
 Email the dev mailing-list and see if anyone has reason to postpone the release.
@@ -151,7 +141,7 @@ Find your release here: https://dist.apache.org/repos/dist/dev/cordova/
 ## Prepare Blog Post
  * Combine highlights from RELEASENOTES.md into a Release Announcement blog post
    * Instructions on [sites page README](https://svn.apache.org/repos/asf/cordova/site/README.md)
- * Get blog post proofread.
+ * Get blog post proofread via [piratepad](http://piratepad.net/front-page/).
 
 ## Start VOTE Thread
 Send an email to dev ML with:
@@ -229,6 +219,8 @@ Find your release here: https://dist.apache.org/repos/dist/release/cordova/tools
     git checkout THEVERSIONTAG
     npm publish plugman
 
+If npm publish fails for you, run `npm owner ls PACKAGENAME` to see if you are an owner.
If you aren't, ask one of the owners to add you.
+
 
 ## Post Blog Post
 


Mime
View raw message