Version lifecycle/ja

MediaWiki は「継続的なインテグレーション」の開発モデルを実践しており、そのソフトウェアの変更は定期的にウィキメディアのウェブサイト (ウィキペディアなど) に反映されて実際に使用できるようになります.

理論上は、新たなメジャーリリースは四半期ごとに行われ、各リリースのブランチは最初のリリースから1年間はセキュリティ上の更新を受け付けます. 時間的に制約があるため、またコードベースの迅速なリファクタリングのために、それより古くなったリリースについては対応できませんし、ライフサイクルを過ぎたリリースにはセキュリティ上あるいは重要な変更でも適用しません.

リリースマネジャーの Tim Starling をはじめとする MediaWiki の開発者は、ウィキ運用者が メーリングリストに登録することを強く推奨します. これに参加してすべてのリリースの告知を受け取れるため、自分のウィキを確実に最新のバージョンのソフトウェアで実行し続けることができます. 同じアナウンスが  と   の各メーリングリストにも投稿されます.

バージョンとライフサイクル終了時期
For the planned upcoming release cycles see this page.

Versions included in this table that are marked as obsolete will not receive any security fixes. The release manager has also issued a strong recommendation that versions not listed above as  or   should not be used in a production environment. They may contain critical security vulnerabilities and other major bugs, including the threat of possible data loss and/or corruption.

Release Policy

 * 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 is supported until May 2015. 1.23 will be released the year before that so that people will have 1.23 available as an LTS to move to and a year to make the transition.


 * Releases 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 comes out, we'll have an announcement for 1.19 users letting them know what changes they can expect in 1.23.


 * Point releases will be made periodically. 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).

Extension lifecycle management
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.