RELEASING

Releasing

1. git checkout development
2. Update files
3. Update CONTRIBUTORS.md - this is annoying, so eventually we might get rid of this part of the process. This is the process that gives us CONTRIBUTORS.md and also updates package.json with the contributor info. - Use contributor to automate this, though you might need to do some hand editing as well (email addresses, URLs, bonnici's name).
   • You need to merge development into master first, because contributors grabs info from the github api, and github only looks at the default/master branch. 1. git checkout master 1. git reset --hard @~5
   • There might be readme changes, etc; These should be in development, but they might be a different hash, so reset them. 1. git merge development 1. git push --force 1. git checkout development 1. contributor 1. mv contributors.md CONTRIBUTORS.md 1. nano CONTRIBUTORS.md package.json Fix bonnici's name in CONTRIBUTORS.md and the names/urls in package.json. 1. git add CONTRIBUTORS.md package.json
4. Update CHANGELOG.md
5. Update chatBot.js version number to X.Y.Z (no -dev tag)
6. git add chatBot.js
7. npm version X.Y.Z -m "vX.Y.Z" (set the new version in package.json and commit chatBot.js as well)
8. git checkout master
9. git merge development
10. git push
11. git checkout development
12. Update versions for development
13. git checkout development
14. Update chatBot.js version number to X.Y.Z-dev
15. npm version X.Y.Z-dev -m "X.Y.Z Development"
16. git push
17. Release on github.. Include the changelog since last release, or if it's too long include only the important stuff.
18. Wait 24 hours.
19. If no bugs have shown up, release on npm

• The easiest way to make sure the release is clean is to download the tarball from github (master) and release that:
• npm publish X.Y.Z.tar.gz --tag ReleaseName