increment release number in package.json, edits to DEVELOPERS.md

Author: Alexander Goedde

DEVELOPERS.md

@@ -13,6 +13,23 @@ Set `$JS_COMPILER` to `${HOME}/compiler.jar`.
 
 ## Release Steps
 
+
+### Update the release number in the repo
+
+Update 'package/package.json' with the new release number.
+
+
+### Build for browsers
+
+In the root directory, do 
+
+```
+make all
+``` 
+
+which will package the library for browser use into the `build` directory.
+
+
 ### Tag the release
 
 E.g. by doing
@@ -26,7 +43,9 @@ before you commit. (Add the hash of a commit at the end of the above to tag at a
 
 ### Draft a release on GitHub
 
-Go to 'releases' and 'Draft a new release' (adding some release notes is nice!).
+If your comment for the tagging did not include "tagged release", then you need to manually draft a release. Go to 'releases' and 'Draft a new release' (adding some release notes is nice!).
+
+Otherwise: add release notes to the automatically created release.
 
 
 ### Publish to npm
@@ -40,25 +59,14 @@ make publish
 (This requires your npm user to have publishing priviledges for the package on npm.)
 
 
-### Build for browsers
-
-In the root directory, do 
-
-```
-make all
-``` 
-
-which will package the library for browser use into the `build` directory.
-
-
 ### Copy over to AutobahnJSbuilt
 
 Just copy over the contents of the `build` directory to the AutobahnJSbuilt repo, tag and commit.
 
 
 ### Upload to S3
 
-Dp 
+Do
 
 ```
 scons publish

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "autobahn",
-  "version": "0.9.7",
+  "version": "0.9.8",
   "description": "An implementation of The Web Application Messaging Protocol (WAMP).",
   "main": "index.js",
   "browser": {