NPM Publish Procedures for this repo

1. First go through the normal commit and branch merge process in GitHub to the point where you have the new releases you want to publish to npm (along with their associated tag). Be sure to update the package.json version to match the new releases before you create the release in git. Be sure to update the rtcomm (node) module dependency in the rtcomm (node-red) package.json to the appropriate dependency before you publish it as well.
2. The next step is to pull the release you want to publish to your local repo. When you do the npm publish it will actually package up this release and deliver it to the npm registry. These next steps are what is needed to get the local repo updated to the appropriate release.
3. From Eclipse, using the git tool, do a "Pull" (can be found under team from the Javascript view in Eclipse). This will update the local repo with all the latest tags.
4. Then do a "Switch To" and locate the tag you just created. Select the release tag and your local repo should now contain the release. Note that you will be in a "Detached Head" mode now which means you do NOT want to make any code changes that might need to be commited.
5. Now its time to publish to npm. On this step just let npm use the version number contained in you package.json file to tag the install. npm will use the version number from the package.json. To do the publish, navigate to the root directory of your local git repo and simply type: npm publish ./
6. You will need to do this for both the node and node-red rtcomm modules.
7. For developers doing this manually, after publishing to npm, you'll need to immediately checkout whatever branch you plan to work in next to move your HEAD back to the tip of a branch you can deliver on.