Now that tests are being added, development is continuing, and the project has multiple maintainers, I think it would be good to make the release cycle of this project easier. This will offload the requirement of devongovett to step in a publish to NPM and will help get contributions out the door quicker.
Off the top of my head, I know that TravisCI supports this and the creation of github releases to go along with it. You can trigger these when new tags are created or even with master is pushed to.
This is effectively giving all contributors to this project permissions to release the package to NPM, so I can understand not wanting to go with this suggestion.
Now that tests are being added, development is continuing, and the project has multiple maintainers, I think it would be good to make the release cycle of this project easier. This will offload the requirement of devongovett to step in a publish to NPM and will help get contributions out the door quicker.
Off the top of my head, I know that TravisCI supports this and the creation of github releases to go along with it. You can trigger these when new tags are created or even with master is pushed to.
This is effectively giving all contributors to this project permissions to release the package to NPM, so I can understand not wanting to go with this suggestion.