ashatora/openlayers
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

add note about npm adducer

Bart van den Eijnden
2015-03-27 10:27:44 +01:00
parent e5509ced5e
commit a9b985fe0e
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Release-Procedure.md
+2 -2
@@ -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
<a name="race-condition"></a>
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.