MediaWiki operates on a "continuous integration" development model, where software changes are pushed live to Wikimedia web sites such as Wikipedia on a regular basis.
In theory, new major releases are issued on a half-year basis, and release branches continue to receive security updates for up to a year as of first release. Due to time constraints and rapid refactoring of the code base, we cannot support obsolete releases forever, and security and critical updates are not applied to releases which have reached their end of life status.
The release manager strongly recommends that wiki operators subscribe to the
mediawiki-announce mailing list, which receives notification of all releases, and ensure that their wiki runs the most up to date version of the software possible. These announcements are also posted to
Versions and their end-of-life[edit | edit source]
|1.26.x||future version||2015-11-25||November 2016|
|1.25.x||future version||2015-05-25||June 2016|
|1.24.x||current version||2014-11-26||November 2015|
|1.23.x (LTS)||legacy version||2014-06-05||May 2017|
|1.22.x||obsolete version||2013-12-06||December 2014|
|1.21.x||obsolete version||2013-05-25||June 2014|
|1.20.x||obsolete version||2012-11-07||November 2013|
|1.19.x (LTS)||legacy version||2012-05-02||May 2015|
|1.18.x||obsolete version||2011-11-28||November 2012|
Versions included in the above table that are marked as obsolete will not receive any security fixes. They may contain critical security vulnerabilities and other major bugs, including the threat of possible data loss and/or corruption. The release manager has also issued a strong recommendation that only versions listed above as current version or legacy version should be used in a production environment.
Important dates for future versions[edit | edit source]
This table sets out the plan for future MediaWiki releases, including the date the branch will be made.
|Version||Branch date||Release date||End-of-life|
Note: The branch dates may be incorrect, see Release notes for correct dates.
Release policy[edit | edit source]
- Point releases will be made at least monthly, on the last Wednesday of the month. Every point release will include updated i18n files as well as any bug fixes. No new features will be back-ported to point releases and support doesn't include extensions in general, see below (e.g. Extension:UniversalLanguageSelector doesn't support current LTS).
- A major release will be made every six months.
- A long term support release (LTS) will be made every two years. There will be a one-year overlap in LTS support. For example, 1.19 was supported until May 2015. 1.23 was released the year before that so that people had it available as an LTS to move to and a year to make the transition.
- Release notes will continue to be the basis for seeing what has changed. Because of the nature of a volunteer-driven project, it isn't possible to say with any certainty what will happen in the next 6-12 months.
- To mitigate the problem of release notes, we will publish a list of new features in the upcoming LTS relative to the last LTS six months before it comes out. This means that about the time when 1.22 came out, an announcement was made for 1.19 users letting them know what changes they could expect in 1.23.
Version timeline[edit | edit source]
Release timeline[edit | edit source]
This timeline is a schedule for what needs to happen before the release of a new version. The date of the actual release is given here as REL (for “release”) and the suffix -# (for “number of weeks prior to release”).
|REL-7||Announce that the release branch will be created in one week. Ask people to make sure that anything needed to complete in-progress features is merged before then. Create "MW-X.XX-release" in Phabricator.|
|REL-6||Create the branch for core and all extensions in Gerrit.|
|REL-5||Apply the X.XX-rc.0 tag and release the initial release candidate.|
|REL-4||Collect any bug reports and summarize them on the mailing list.|
|REL-3||Apply the X.XX-rc.1 tag and release the second release candidate. Any new extensions that are proposed for addition to the tarball should be in it by this point. No extension changes are made after this point.|
|REL-2||Collect any new bug reports, merge fixes, back out new, incomplete features accidently included, apply X.XX-rc.2 tag and release third release candidate.|
|REL-1||Repeat previous step, use X.XX-rc.final to tag and release. No backports are accepted after this point.|
|REL||TAG the code with X.XX and Make the release.|
Extension lifecycle management[edit | edit source]
Most MediaWiki installation include a significant number of extensions (WMF MediaWikis often around 80 extensions). Managing the maintenance bug fixing of extensions and choosing the right version of an extension in cases where the HEAD development version relies on features not yet available in stable or oldstable MediaWiki core, is a major challenge for all maintainers of MediaWiki installations.
Extension maintainers are therefore strongly encouraged to maintain a git tag or branch for their version corresponding to the release tag the stable and oldstable version. An initial version, that simply points to the state of the code at the time of the release may be created centrally. However, it is the responsibility of the extension maintainer to fix bugs not only in HEAD but also in the oldstable and stable versions. If the extension works with all of oldstable, stable and HEAD, this requires only to update the tags. However, if some changes are specific to later versions, the lifecycle rule require that branches are created and individual merges of the bugfix to each branch be made.
The goal of these rules is that people or organizations installing MediaWiki can rely on installing the newest release of a version and matching extensions by a simple method, e.g. for 1.20.x core by referring to REL1_20 in git.
[edit | edit source]
- Generators on WikiApiary - Statistics about the use of different versions of MediaWiki.