Release checklist

Release Checklist

All changes to ClojureScript One must be made in a milestone, see How we work for an overview. Before making a new release, go through the following checklist and make sure you're not forgetting anything.

Testing

• All tests pass.
• Verify that things still work on all the browsers in the test matrix.
  • Latest Safari (OS X)
  • Latest Google Chrome (Windows, OS X, Linux)
  • Latest Firefox (Windows, OS X, Linux)
  • Internet Explorer 8+ (Windows) (production mode only)

Documentation

• Update the wiki ensuring that all documentation is accurate. Use the one-wiki project to make changes - we'll push them over to the main wiki when we deploy. https://github.com/brentonashworth/one-wiki/wiki.
• Update the website. https://github.com/brentonashworth/one.guide.
• Update the Change-log.
• Update the README

Unleash

• git merge milestone into master
• git merge or git rebase from master to pull-requests so that people have an up-to-date non-master target for pull requests
• Tag and push master. Use git describe --match v0.0 to get the number of commits on master. Use this number to tag the repository. If the number is 150 the use the tag r150.
• Deploy website
  • git push to the Heroku repo from one.guides
  • git tag the one.guides GitHub repo with the same release name as the code (e.g. r150 from the example above.
• Deploy wiki
  • git push from the one-wiki.wiki repo to the one.wiki repo on GitHub.

Publicize

• Tweet/Facebook/G+/etc.
• Send email to mailing list announcing changes
• Blog
  • Personal blogs
  • If the release is a particularly significant one, Clojure/core
• Think about doing a screencast showing off the new features

Set up for next release

• Create next Mxxx milestone
• Create milestone release template issues
  • Update documentation
• Delete old Mxxx branch