Version lifecycle/ru

MediaWiki действует согласно модели развития «непрерывной интеграции», где изменения программного обеспечения на регулярной основе «выталкиваются» жить на веб-сайты Викимедиа, такие, как Википедия.

В теории, новые крупные релизы выпускаются на ежеквартальной основе, и побочные ответвления и наследуемые версии продолжают получать обновления безопасности в течение года с первого релиза следующей версии. Из-за нехватки времени и быстрого рефакторинга базы кода, мы не можем бесконечно поддержать устаревшие релизы, обновления безопасности и критические обновления не применяются к версиям, которые достигли завершения жизненного цикла.

Релиз-менеджер настоятельно рекомендует операторам вики-проектов подписаться на список рассылки, чтобы получать уведомления обо всех релизах, и обеспечить свои вики-проекты самой свежей версией программного обеспечения. Эти объявления также размещаются в  и.

Текущие версии и их жизненный цикл
Versions included in the above table that are marked as obsolete as well as versions not listed at all 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.

Политика выхода релизов

 * 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. doesn't support current LTS).
 * Большой релиз будт сделан каждые шесть месяцев.
 * Версия с долгосрочной поддержкой (LTS) будет разрабатываться каждые два года. There will be a one-year overlap in LTS support. For example, 1.23 was supported until мая 2017 года. 1.27 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.26 came out, an announcement was made for 1.23 users letting them know what changes they could expect in 1.27.

Release timeline
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 T (for "time" of release) and the suffix -# (for “number of weeks prior to release”).

Управление жизненным циклом расширений
Most MediaWiki installations include a significant number of extensions (Wikimedia wikis often have around 140). 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, can be challenging.

Extension maintainers are therefore strongly encouraged to maintain a git branches for each extension version corresponding a MediaWiki version. (See Compatibility for details.) For extensions hosted in Wikimedia's git repos, such branches (with names such as  for MediaWiki 1.30) are created automatically from master when a new MediaWiki version is branched (on the assumption that the extension master is compatible with MediaWiki master at all times). However, it's preferable for the extension maintainer to fix bugs not only in HEAD but also in the oldstable and stable versions (by backporting the fix to the old branches if necessary).

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.

Ссылки

 * Generators on WikiApiary - Statistics about the use of different versions of MediaWiki.