[decouple] Notifications 0.5.0 #271
Description
When taking care of a task (and marking as done), please add your name to the task!
Reason
- Decouple release cycle from core
Tasks
- align master with stable10 so we can work solely on master in the future: Merge stable10 into master #270
- lock stable10 branch
QA
- Create QA Milestone
- Move items from
developmenttoqa - Create release branch with the format "release-$version"
- Create "$version Testplan"
Documentation
- Changes in the docs needed?
Marketing
- Ping RocketChat channel #marketing
- Check/adapt info.xml stuff
- Check/adapt screenshot
- Blog post or other communication if applicable
Build
All actions to be done on the release branch from here:
- Bump version in info.xml (no version suffix)
- Update CHANGELOG.md - Change CHANGELOG.md 'Unreleased' to '$version' (final release date unknown)
Beta/RC
- Create github tag for 'v${version}RC1' on release branch
- Build and sign RC tarball from github tag 'v${version}RC1' (see
handbook for how to build) - Upload as Github release using changelog entries
- 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
Final
- Create github tag for final 'v${version}' on release branch
- Build and sign final tarball from github tag 'v${version}' (see
handbook for how to build) - Upload as Github release using changelog entries
- Smoke test tarball (at least install + enable)
Publishing
- Send mail to release-coordination with link to this ticket and to the changelog
Post-release
- Rename QA milestone to '$version'
- Add a new 'Unreleased' section in CHANGELOG.md and add release date '$version - $currentDate' (ex: 3.1.5 - 2018-08-01)
- Create PR to merge changes back to the
masterbranch with
description "Closes #XYZ" with the release ticket number