From a9b985fe0e164a1851b57fe457b000f00df53e3c Mon Sep 17 00:00:00 2001 From: Bart van den Eijnden Date: Fri, 27 Mar 2015 10:27:44 +0100 Subject: [PATCH] add note about npm adducer --- Release-Procedure.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Release-Procedure.md b/Release-Procedure.md index 2bf4129..a171108 100644 --- a/Release-Procedure.md +++ b/Release-Procedure.md @@ -55,7 +55,7 @@ Tag the release. In a working copy of the openlayers/ol3 repo: ### Publish to npm -Run the `publish.sh` task with the version number as specified in the `package.json` (without the "v" prefix). The `publish.sh` script makes sure that the tag name and the version in `package.json` for that tag match. +Run the `publish.sh` task with the version number as specified in the `package.json` (without the "v" prefix). The `publish.sh` script makes sure that the tag name and the version in `package.json` for that tag match. If you have not created a user before, do so now, see: https://docs.npmjs.com/cli/adduser ./tasks/publish.sh 3.1.0 @@ -102,4 +102,4 @@ Attach the `.zip` archive created above to the release page. ### Notes -Note that there is a potential race condition related to creating a changelog before a release is tagged. This could be avoided by generating the changelog after tagging the release. However, since we already need to make a change to the repository for the release (updating the version in package.json), the changelog creation step is included with this change for convenience. There aren't serious consequences associated with missing an entry in the changelog, so this should be an acceptable tradeoff. +Note that there is a potential race condition related to creating a changelog before a release is tagged. This could be avoided by generating the changelog after tagging the release. However, since we already need to make a change to the repository for the release (updating the version in package.json), the changelog creation step is included with this change for convenience. There aren't serious consequences associated with missing an entry in the changelog, so this should be an acceptable tradeoff. \ No newline at end of file