8 Releasing
Lorenz Hübschle-Schneider edited this page 2016-01-18 20:45:41 +01:00

Summary

We have two principal branches:

Once in a while we want to do a release of the project by deploying master on gh-pages

Actions

Before releasing

  • If the release contains new features we should announce our intention of releasing on #glowing-bear to give potential testers enough time to test
  • We should make sure that the automatic tests are passing
  • Some manual testing should be done as well

When releasing

  • On branch master, bump versions in index.html (settings dialog), manifest.json, package.json, manifest.webapp, and bower.json
  • Commit the changes
  • Tag the commit
  • Merge master into gh-pages
    • Make sure to resolve potential conflicts in the JavaScript includes from minification. This requires rebasing use-minification onto master (and force-pushing the result).
  • On branch gh-pages, minify the JavaScript files with npm run minify and commit min.js and min.map
  • Push to origin (and don't forget to push the tags as well)

After releasing

  • Write the release notes
  • Bugs that are linked to a particular release should be treated in priority