Difference between revisions of "SupportedVersions"

From Mahara Wiki
Jump to navigation Jump to search
m
m
(47 intermediate revisions by 4 users not shown)
Line 1: Line 1:
= Definition of support =
+
== Current and upcoming releases ==
  
Being supported means:
+
{| class="mw_metadata" style="font-size: 1em;" 
 
+
| style="background:#ba2025; color:#fff" | Unsupported
* The release team is committed to making available updates to Mahara that are security related.
+
| style="background:#566d31; color:#fff" | Currently in support
* Occasionally, some other serious bug fixes will be included, but these are not guaranteed.
+
|Not yet released
 +
|}
  
 +
A new major version of Mahara is released [[6MonthlyCycle|every 6 months]], around April and October. From Mahara 1.0 to 1.10, these were numbered using a type of semantic versioning. Starting with the 15.04 release (after 1.10), they are numbered to reflect the date the release is scheduled (so "15.04" means "2015, April"). See [[Developer_Area/Version_Numbering_Policy|Version Numbering Policy]] for more details.
  
= Release schedule =
+
The standard support lifetime of a major version is '''18 months''' (3 release cycles):
  
{| class="mw_metadata" style="font-size: 1em;" 
+
* Receives bug fixes and security fixes for the first 6 months
| style="background:IndianRed" | Unsupported
+
* Receives security fixes only, for an additional 12 months
| style="background:lightgreen" | Currently in support
 
|Not yet released
 
|}
 
  
== Current and upcoming releases (Mahara 1.5+)==
+
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. 15.04 is our first extended support release, due to a complete overhaul of the Mahara theme system in 15.10 breaking compatibility for existing custom themes. Currently, there are no extended support releases planned.
  
As of Mahara 1.5 and the adoption of the [[6MonthlyCycle|6-month release cycle]], Mahara is supported for the duration of 3 release cycles.
 
  
 
{| class="mw_metadata" style="font-size: 1em;"
 
{| class="mw_metadata" style="font-size: 1em;"
Line 24: Line 22:
 
| style="background:#ccc" | End of support
 
| style="background:#ccc" | End of support
 
|-
 
|-
|1.6
+
| 19.04
|October 2012
+
| April 2019
|April 2014
+
|
 +
|-
 +
| style="background:#566d31; color:#fff" | 18.10
 +
| style="background:#566d31; color:#fff" | October 2018
 +
| style="background:#566d31; color:#fff" | April 2020
 +
|-
 +
| style="background:#566d31; color:#fff" | 18.04
 +
| style="background:#566d31; color:#fff" | April 2018
 +
| style="background:#566d31; color:#fff" | October 2019
 +
|-
 +
| style="background:#566d31; color:#fff" | 17.10
 +
| style="background:#566d31; color:#fff" | October 2017
 +
| style="background:#566d31; color:#fff" | April 2019
 +
|-
 +
| style="background:#ba2025; color:#fff" | 17.04
 +
| style="background:#ba2025; color:#fff" | April 2017
 +
| style="background:#ba2025; color:#fff" | October 2018
 +
|-
 +
| style="background:#ba2025; color:#fff" | 16.10
 +
| style="background:#ba2025; color:#fff" | October 2016
 +
| style="background:#ba2025; color:#fff" | April 2018
 +
|-
 +
| style="background:#ba2025; color:#fff" | 16.04
 +
| style="background:#ba2025; color:#fff" | April 2016
 +
| style="background:#ba2025; color:#fff" | October 2017
 +
|-
 +
| style="background:#ba2025; color:#fff" | 15.10
 +
| style="background:#ba2025; color:#fff" | October 2015
 +
| style="background:#ba2025; color:#fff" | April 2017
 +
|-
 +
| style="background:#ba2025; color:#fff" | 15.04
 +
| style="background:#ba2025; color:#fff" | April 2015
 +
| style="background:#ba2025; color:#fff" | October 2017 ('''extended support release''' due to 15.10 theme overhaul)
 +
|-
 +
| style="background:#ba2025; color:#fff" | 1.10
 +
| style="background:#ba2025; color:#fff" | October 2014
 +
| style="background:#ba2025; color:#fff" | April 2016
 +
|-
 +
| style="background:#ba2025; color:#fff" | 1.9
 +
| style="background:#ba2025; color:#fff" | April 2014
 +
| style="background:#ba2025; color:#fff" | October 2015
 +
|-
 +
| style="background:#ba2025; color:#fff" | 1.8
 +
| style="background:#ba2025; color:#fff" | October 2013
 +
| style="background:#ba2025; color:#fff" | April 2015
 +
|-
 +
| style="background:#ba2025; color:#fff" | 1.7
 +
| style="background:#ba2025; color:#fff" | April 2013
 +
| style="background:#ba2025; color:#fff" | October 2014
 
|-
 
|-
| style="background:lightgreen" | 1.5
+
| style="background:#ba2025; color:#fff" | 1.6
| style="background:lightgreen" | April 2012
+
| style="background:#ba2025; color:#fff" | October 2012
| style="background:lightgreen" | September 2013
+
| style="background:#ba2025; color:#fff" | April 2014
 
|}
 
|}
  
== Older releases (pre Mahara 1.5)==
+
== Older releases (pre Mahara 1.6)==
  
For Mahara 1.4 and earlier, support has been provided for 2 release cycles.
+
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.
  
 
{| class="mw_metadata" style="font-size: 1em;"
 
{| class="mw_metadata" style="font-size: 1em;"
Line 42: Line 88:
 
| style="background:#ccc" | End of support
 
| style="background:#ccc" | End of support
 
|-
 
|-
| style="background:lightgreen" | 1.4
+
| style="background:#ba2025; color:#fff" | 1.5
| style="background:lightgreen" | June 2011
+
| style="background:#ba2025; color:#fff" | April 2012
| style="background:lightgreen" | October 2012
+
| style="background:#ba2025; color:#fff" | October 2013
 +
|-
 +
| style="background:#ba2025; color:#fff" | 1.4
 +
| style="background:#ba2025; color:#fff" | June 2011
 +
| style="background:#ba2025; color:#fff" | October 2012
 
|-
 
|-
| style="background:IndianRed" | 1.3
+
| style="background:#ba2025; color:#fff" | 1.3
| style="background:IndianRed" | Sept 2010
+
| style="background:#ba2025; color:#fff" | Sept 2010
| style="background:IndianRed" | April 2012
+
| style="background:#ba2025; color:#fff" | April 2012
 
|}
 
|}
  
 +
== Definition of support ==
  
= Extended support =
+
Being "supported" means:
  
We upload packaged versions of Mahara to Debian and Ubuntu, which can be installed via the repositories.
+
* 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
  
This means that we provide '''security fixes only''' for these packages until the "End of life" dates. Only versions installed from the universe repositories are given security fixes beyond the official Mahara end of support date.
+
=== Specific backporting rules ===
  
== Ubuntu ==
+
When deciding which bugs to backport to supported branches, these are the general principles:
  
LTS versions of Ubuntu (Marked in '''bold''' text in the table) are supported for 5 years, normal releases are supported for 18 months.
+
* '''[[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 [https://en.wikipedia.org/wiki/Software_regression regressions].
  
{| class="mw_metadata" style="font-size: 1em;"
+
* '''Non-security bugs'''
| Version
+
** '''All''' Critical bugs should be backported.
| Code name
+
** '''Most''' High priority bugs should be backported. At the maintenance team's discretion, these might not be backported if:
| Mahara version
+
*** Backporting would be technically difficult due to differences between Mahara versions.
| End of life date
+
*** The bug fix requires database upgrades or dataroot manipulations.
|-
+
*** The bug fix otherwise introduces a high risk of [https://en.wikipedia.org/wiki/Software_regression regressions].
| Ubuntu 12.10
+
** '''No''' Medium or Low priority non-security bugs are backported.
| Quantal Quetzal
+
** '''No''' Wishlist bugs are backported. Wishlist items are only added to the current development branch.
| 1.5.1
 
| April 2014
 
|-
 
| style="background:lightgreen;font-weight:bold;" | Ubuntu 12.04 LTS
 
| style="background:lightgreen" | Precise Pangolin
 
| style="background:lightgreen" | 1.4.2
 
| style="background:lightgreen" | April 2017
 
|-
 
| style="background:lightgreen" | Ubuntu 11.10
 
| style="background:lightgreen" | Oneiric Ocelot
 
| style="background:lightgreen" | 1.4.0
 
| style="background:lightgreen" | April 2013
 
|-
 
| style="background:lightgreen" | Ubuntu 11.04
 
| style="background:lightgreen" | Natty Narwhal
 
| style="background:lightgreen" | 1.2.7
 
| style="background:lightgreen" | October 2012
 
|-
 
| style="background:IndianRed" | Ubuntu 10.10
 
| style="background:IndianRed" | Maverick Meerkat
 
| style="background:IndianRed" | 1.2.5
 
| style="background:IndianRed" | April 10, 2012
 
|-
 
| style="background:lightgreen;font-weight:bold;" | Ubuntu 10.04.4 LTS
 
| style="background:lightgreen" | Lucid Lynx
 
| style="background:lightgreen" | 1.2.4
 
| style="background:lightgreen" | April 2015
 
|}
 
  
 +
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.
  
== Debian ==
+
See [[Developer_Area/Bug_Status#Importance|Bug Status:Importance]] for the guidelines on how we decide whether a bug is Critical, High, Medium, or Low.
  
Debian releases are supported until one year after the next version is released.
+
== See also ==
  
{| class="mw_metadata" style="font-size: 1em;"
+
* [[6MonthlyCycle]]
| Version
+
* [[Developer Area/Version Numbering Policy]]
| Code name
 
| Mahara version
 
| End of life date
 
|-
 
| Debian 7
 
| Wheezy
 
| TBA
 
| TBA
 
|-
 
| style="background:lightgreen;font-weight:bold;" | Debian 6
 
| style="background:lightgreen" | Squeeze
 
| style="background:lightgreen" | 1.2.6
 
| style="background:lightgreen" | TBA
 
|}
 

Revision as of 09:03, 26 February 2019

Current and upcoming releases

A new major version of Mahara is released every 6 months, around April and October. From Mahara 1.0 to 1.10, these were numbered using a type of semantic versioning. Starting with the 15.04 release (after 1.10), they are numbered to reflect the date the release is scheduled (so "15.04" means "2015, April"). See Version Numbering Policy for more details.

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. 15.04 is our first extended support release, due to a complete overhaul of the Mahara theme system in 15.10 breaking compatibility for existing custom themes. Currently, there are no extended support releases planned.


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.

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.

See also