Release Checklist - OXYGEN-MARKET/oxygen-market.github.io GitHub Wiki
All the things to tick off when doing a new release:
- Complete? - make sure all tickets completed
- CHANGELOG - updated, including version and date? Remove any
DONE
orWIP
notes. - Documentation - any urgent documentation changes release at the same time as the new version; any lower priority changes, file a ticket in the snowplow repo
- Configuration file templates - easy to forget. Have these been updated?
- Hosted assets - any new ones, add to the hosted assets page. Also, remove any
-TEST-rX
suffixes on the filenames of the new hosted asset versions - References to hosted assets - e.g. in HTML files or in config files. Make sure to update these
- Cut the release - merge
master
->develop
, mergefeature/new-release
->develop
, all okay? Then mergedevelop
->master
andpush
- Tag - always tag like so:
git tag -a '0.6.2' -m 'Version 0.6.2'
. Thengit push --tags
- Issues - close any issues fixed in this release
- Roadmap - update the overall roadmap (delete the just-released release)
- Delete feature branch -
git branch -D feature/whatever
andgit push origin :feature/whatever
- Blog post - always write a blog post
- Add release - in GitHub
- Update the version matrix - in Google Spreadsheets
- Ticket to Ihor to update upgrade guide
- Tweet - put
#opensource
in the tweet - Thread on Discourse - final step