Developer Area/Release Instructions: Difference between revisions
From Mahara Wiki
< Developer Area
Line 21: | Line 21: | ||
|- | |- | ||
|'''3. Release follow-up admin''' - forums, bug report updating, admin etc | |'''3. Release follow-up admin''' - forums, bug report updating, admin etc | ||
| | |'''[[Developer_Area/Release_Instructions/Release_Candidate_Follow_Up|RC Follow up]]''' | ||
|✅ | |✅ | ||
|✅ | |✅ |
Revision as of 18:06, 6 Mayıs 2022
Mahara creates 2 major releases per year (April: XX.04.0, and October: XX.10.0). We also create 'minor point' releases when we need to add urgent fixes and security updates (e.g. XX.04.1, XX.04.2 etc). Doing minor point releases is slightly different to doing a major release. On a major release, we apply any security and bug fixes that are included in the release as a minor point update to other supported versions. Minor point releases are for security fixes or urgent bug fixes - these happen between major releases.
Overview
STAGES | Release Candidate | Major release
(XX.XX.0) |
Minor point release
(XX.XX.1 etc) |
---|---|---|---|
1. Release prep | RC Prep | Major Prep | Minor Prep |
2. The Release - Outcome: zip file is available on Launchpad | RC Release | Major Release | Minor Release |
3. Release follow-up admin - forums, bug report updating, admin etc | RC Follow up | ✅ | ✅ |
4. Community site upgrades | NA | ✅ | NA |
5. Minor point updates for all supported versions and clients who have paid for that support package | NA | ✅ | ✅ |
6. Retro workshop | NA | ✅ | NA |
Links to documentation
- A week before the release: Comms
- Pre-release steps for developers
- Release day steps for developers
Extra info for devs
OLD DOCUMENTATION (Beware: only kept for posterity)