Update release with info about release tag (#156)

developer/release.rst

@@ -56,7 +56,8 @@ After having a release properly tagged, it can be published on NPM.  For ``dojo`
 1. Make sure you are on the current, up-to-date ``master`` branch via ``git``.
 2. Run ``git checkout x.x.x`` where ``x.x.x`` is the release tag you want to publish.
 3. Run ``npm publish`` (you will need to be logged into ``npm`` as an authorized
-   maintainer of the package.
+   maintainer of the package). Use ``publish --tag=patch1.XX`` to publish a point 
+   release that is not the latest release, where 1.XX is the branch number. 
 4. Validate that the package is published as you expect via ``npm view``.
 
 Because ``dojox`` and ``util`` contain submodules, the workflow is slightly different:
@@ -67,5 +68,6 @@ Because ``dojox`` and ``util`` contain submodules, the workflow is slightly diff
 4. Run ``git submodule update --init --recursive`` which will ensure that the
    submodule is checked out to the commit associated with the current tag.
 5. Run ``npm publish`` (you will need to be logged into ``npm`` as an authorized
-   maintainer of the package.
+   maintainer of the package). Use ``publish --tag=patch1.XX`` to publish a point 
+   release that is not the latest release, where 1.XX is the branch number.
 6. Validate that the package is published as you expect via ``npm view``.