Actions

Difference between revisions of "Developer Area/Release Instructions"

From Mahara Wiki

< Developer Area
 
(22 intermediate revisions by 2 users not shown)
Line 1: Line 1:
Mahara creates 2 major releases per year (April: X.04.0, and October: X.10.0). We also create 'minor point' releases when we need to add urgent fixes and security updates (e.g. X.04.1, X.04.2 etc).
+
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.
  
This page contains links to details about the procedure to follow when building a release for general download, i.e. a zip file.
+
==Overview==
 +
{| class="wikitable mw-collapsible"
 +
!'''STAGES'''
 +
!'''Release Candidate'''
 +
!'''Major release'''
 +
'''(XX.XX.0)'''
 +
!'''Minor point release'''
 +
'''(XX.XX.1 etc)'''
 +
|-
 +
|'''1. Release prep'''
 +
|RC Prep
 +
|'''[[Developer_Area/Release_Instructions/Pre-release|Major Prep]]'''
 +
|Minor Prep
 +
|-
 +
|'''2. The Release''' - Outcome: zip file is on Launchpad (a major release + 3 minor points)
 +
|'''[[Developer_Area/Release_Instructions/Release_Candidate|RC Release]]'''
 +
|'''[[Developer_Area/Release_Instructions/Release_day|Major Release]]'''
 +
|[[Developer Area/Release Instructions/Minor Release|'''Minor Release''']]
 +
|-
 +
|'''3. Release follow-up admin'''  - forums, bug report updating, admin etc
 +
|'''[[Developer_Area/Release_Instructions/Release_Candidate_Follow_Up|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
 +
|}
  
Doing minor point releases is slightly different to doing a major release.
+
==Links to documentation==
  
For the purposes of these instructions, assume we are releasing version X.Y.Z of Mahara.
+
#A week before the release: [[Developer Area/Release Instructions/Comms|Comms]]
 +
#[[Developer Area/Release Instructions/Pre-release|Pre-release steps for developers]]
 +
#[[Developer_Area/Release_Instructions/Release_day|Release day steps for developers]]
  
On a major release, we apply any security and bug fixes that are included in a major release as a minor point update to other supported versions (backported). But we don't backport any new features.
+
====Extra info for devs====
  
Minor point releases are for security fixes or urgent bug fixes - these happen between major releases.
+
*[[Developer_Area/Release_Instructions/Creating_a_GPG_key|Creating a GPG key]]
 
+
*[[Developer Area/Version Numbering Policy|Version Numbering policy]]
'''Overview'''
+
*[[Developer Area/Release Policy|Release Policy]]
 
 
Release candidate - zip file is available on Launchpad (not for minor)
 
 
 
Release candidate testing (not for minor)
 
 
 
Release prep (yes for minor, but slight differences)
 
 
 
The Release - zip file is available on Launchpad (yes for minor)
 
 
 
Release follow-up - forums, bug report updating, admin etc (yes for minor, but slight differences)
 
 
 
Upgrade community sites (Clients have to pay for upgrades) (not for minor)
 
  
Do minor point updates are for all supported versions and clients who have paid for that support package (yes for minor)
 
  
Retro workshop (not for minor)
+
'''OLD DOCUMENTATION (Beware: only kept for posterity)'''
  
===Release steps===
+
*[[Developer Area/Release Instructions/Old Major Release|Old Major release]]
 
 
#[[Developer Area/Release Instructions/Pre-release|Pre-release steps]]
 
#[[Developer_Area/Release_Instructions/Release_day|Release day steps]]
 
 
 
Older pages kept for reference: (all the information in the pages below has been added to the pages above)
 
 
 
*[[Developer Area/Release Instructions/Major Release|Major release]]
 
*[[Developer Area/Release Instructions/Release Candidate|Release candidate]]
 
 
*[[Developer Area/Old release Instructions|Old release instructions]]
 
*[[Developer Area/Old release Instructions|Old release instructions]]
*[[Developer_Area/Release_Instructions/Release_script|Release script]]
+
*[[Developer Area/Release Instructions/Old Release script|Old Release script]]
 
 
====Helper pages====
 
 
 
*[[Developer_Area/Release_Instructions/Creating_a_GPG_key|Creating a GPG key]]
 
*[[Developer Area/Version Numbering Policy|Version Numbering policy]]
 
*[[Developer Area/Release Policy|Release Policy]]
 
  
 
[[category:Developer Area]]
 
[[category:Developer Area]]

Latest revision as of 16:40, 16 June 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 on Launchpad (a major release + 3 minor points) 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

  1. A week before the release: Comms
  2. Pre-release steps for developers
  3. Release day steps for developers

Extra info for devs


OLD DOCUMENTATION (Beware: only kept for posterity)