[ ] Blog post or other communication if applicable
Build
All actions to be done on the release branch from here:
[x] Bump version in info.xml (no version suffix)
[x] Update CHANGELOG.md - Change CHANGELOG.md 'Unreleased' to '$version' (final release date unknown)
Beta/RC
[x] Create github tag for 'v${version}RC1' on release branch
[x] Build and sign RC tarball from github tag 'v${version}RC1' (see
handbook for how to build)
[x] Upload as Github release using changelog entries
[x] Test and document in testplan => Final "Go" from QA (set 'QA-ready' label) => else do another RC after fixing issues in the "release-$version" branch @individual-it
Final
[x] Create github tag for final 'v${version}' on release branch
[x] Build and sign final tarball from github tag 'v${version}' (see
handbook for how to build)
[x] Upload as Github release using changelog entries
[x] Smoke test tarball (at least install + enable) @individual-it
Publishing
[x] Upload tarball to marketplace (see handbook for details)
[x] Publish tarball for customers (see handbook for details)
[x] Send mail to release-coordination with link to this ticket and to the changelog
Post-release
[x] Rename QA milestone to '$version'
[x] Add a new 'Unreleased' section in CHANGELOG.md and add release date '$version - $currentDate' (ex: 3.1.5 - 2018-08-01)
[x] Create PR to merge changes back to the master branch with
description "Closes #XYZ" with the release ticket number
Reason
QA
developmenttoqaDocumentation
Marketing
Build
All actions to be done on the release branch from here:
Beta/RC
Final
Publishing
Post-release
masterbranch with description "Closes #XYZ" with the release ticket number