Releases: Difference between revisions
From Mahara Wiki
mNo edit summary |
m (Catadmin moved page Release Notes to Releases without leaving a redirect) |
(No difference)
| |
Revision as of 14:45, 4 Haziran 2019
Release cycle and version support
A new major version of Mahara is released every 6 months, in April and October. The version numbers reflect the year and the month in which a version was released. See Version Numbering Policy for more details.
| Release cycle | Nov - Apr | May - Oct |
|---|---|---|
| Feature freeze | Early February | Early August |
| UI freeze | Early March | Early September |
| Release candidate | Mid March | Mid September |
| Official release | Late April | Late October |
- Each release has 16 weeks before feature freeze.
- For each release, We've put feature freeze at a month before the release candidate. Only non-feature bug fixes will be committed after this
- The week before the release candidates is a UI freeze. This is a freeze to string changes and theme changes. String or UI fixes will need to be at least high importance.
The standard support lifetime of a major version is 18 months (3 release cycles):
- Receives bug fixes and security fixes for the first 6 months
- Receives security fixes only, for an additional 12 months
In the event that a major release substantially breaks backwards compatibility, we may declare the previous release to be an extended support release which will receive security fixes for 30 months (5 release cycles), in order to give sites more time to upgrade.
Older releases (pre Mahara 1.6)
Prior to Mahara 1.6, Mahara major versions were released as needed, according to no particular schedule. During the transition period to the 6 month release cycle, support for the older releases was provided for 2 release cycles.
Current and upcoming releases
The latest stable version of Mahara is 19.04, released on 30 April 2019.
Note: this page is updated manually, and sometimes falls behind. For 100% up-to-date information, look for the release labelled "Current Stable Release" on our Launchpad release page, or use the "Download" link on the front page of https://mahara.org
| Unsupported | Currently in support | Not yet released |
Launchpad release page: https://launchpad.net/mahara/+series
| Major release | Minor release | Release date | End of support |
|---|---|---|---|
| 19.10 |
|
October 2019 |
April 2021 |
| 19.04 | 30 April 2019 |
October 2020 | |
| 18.10 | 25 October 2018
|
October 2019 (security updates only) | |
| 18.04 | 6 April 2018
|
October 2019 (security updates only) | |
| 17.10 | 30 October 2017
|
30 April 2018 (no longer supported) | |
| 17.04 | 27 April 2017
|
25 October 2018 (no longer supported) | |
| 16.10 | 21 October 2016
|
06 April 2018 (no longer supported) | |
| 16.04 | 28 April 2016
|
30 October 2017 (no longer supported) | |
| 15.10 | 23 October 2015
|
26 April 2017 (no longer supported) | |
| 15.04 | 23 October 2015
|
30 October 2017 (no longer supported) | |
| 1.10 | 21 October 2014
|
2 May 2016 (no longer supported) | |
| 1.9 | 15 April 2014
|
27 October 2015 (no longer supported) | |
| 1.8 | 24 October 2013
|
20 April 2015 (no longer supported) | |
| 1.7 | 19 April 2013
|
21 October 2014 (no longer supported) | |
| 1.6 | 19 October 2019
|
29 April 2014 (no longer supported) | |
| 1.5 | 17 April 2012
|
29 October 2013 (no longer supported) | |
| 1.4 | 13 June 2011
|
(no longer supported) | |
| 1.3 | 10 September 2010
|
(no longer supported) | |
| 1.2 | 16 November 2009
|
(no longer supported) | |
| 1.1 | 25 February 2009
|
(no longer supported) | |
| 1.0 | 9 March 2009
|
(no longer supported) |
Definition of support
Being "supported" means:
- The release team is committed to making available updates to Mahara that are security related. See Security to find out how to report security bugs to us.
- Occasionally, some other serious bug fixes will be included, but these are not guaranteed. If you find another type of bug, please let us know by reporting it on the mahara.org forums or directly on Launchpad: https://bugs.launchpad.net/mahara/+filebug
Specific backporting rules
When deciding which bugs to backport to supported branches, these are the general principles:
- Security bugs
- All Critical and High priority security bugs should be backported.
- Nearly all Medium and Low priority security bugs should be backported. At the maintenance team's discretion, these might not be backported if:
- Backporting would be technically difficult due to differences between Mahara versions.
- The bug fix requires database upgrades or dataroot manipulations.
- The bug fix otherwise introduces a high risk of regressions.
- Non-security bugs
- All Critical bugs should be backported.
- Most High priority bugs should be backported. At the maintenance team's discretion, these might not be backported if:
- Backporting would be technically difficult due to differences between Mahara versions.
- The bug fix requires database upgrades or dataroot manipulations.
- The bug fix otherwise introduces a high risk of regressions.
- No Medium or Low priority non-security bugs are backported.
- No Wishlist bugs are backported. Wishlist items are only added to the current development branch.
If you want to backport certain bug fixes or new features to your own instance of Mahara, you can do so on your own as the code is available.
See Bug Status:Importance for the guidelines on how we decide whether a bug is Critical, High, Medium, or Low.