Ciclo da Duração de Versão
O MediaWiki opera num modelo de desenvolvimento de "integração contínua", onde as alterações de software são enviadas live para os sites da Web da Wikimedia, tal como a Wikipédia, regularmente.
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
Versões e o seu ciclo de duração
|1.39.x (LTS)||current long-term support version|
|1.35.x (LTS)||versão de suporte de longo prazo legada||setembro de 2023|
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 the current “stable version”, "legacy version" or “long-term support version” be used in a production environment.
- Alpha development
- Release development
- Stable release
- Long-term support release
Política de lançamento
- 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 does not necessarily include bundled extensions and skins in general.
- Será efetuado um lançamento mais importante a cada seis meses.
- A minor release (including security patches, message translation back-ports, and general bugfixes) will be made every quarter.
- 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.23 was supported until May 2017. 1.27 was released the year before, so that people have 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.
Calendário de lançamento
Esta cronologia é uma agenda para o que precisa de acontecer antes do lançamento de uma nova versão. A data do lançamento atual é dada aqui como T (para "tempo" do lançamento) e o sufixo -# (para o “número de semanas antes do lançamento”).
|T - 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.|
|T - 6||Create the branch for core and all extensions in Gerrit.|
|T - 5||Apply the X.XX-rc.0 tag and release the initial release candidate.|
|T - 4||Collect any bug reports and summarize them on the mailing list.|
|T - 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. Não é efetuada nenhuma alteração de extensão depois deste ponto.|
|T - 2||Collect any new bug reports, merge fixes, back out new, incomplete features accidentally included, apply X.XX-rc.2 tag and release third release candidate.|
|T - 1||Repita o passo anterior, utilize X.xx-rc.final para etiquetar e lance. Não são aceites backports depois deste ponto.|
|T||TAG o repository com X.XX e crie a versão.|
Gestão do ciclo de duração da extensão
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 to a MediaWiki version.
(Consulte Compatibilidade#Extensões do MediaWiki para detalhes.)
For extensions hosted in Wikimedia's git repos, such branches (with names such as
REL1_30 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.
And it avoids tarballs and zip files with non-relevant and unpredictable names.
Since Version 1.36, MediaWiki only commits to supporting upgrades from two major long-term support releases (LTS) ago (see phab:T259771). Upgrades from older versions of MediaWiki will have to be performed in multiple steps.
- Compatibility information for MediaWiki, most importantly PHP and MySQL
- Stable interface policy
- Geradores em WikiApiary - Estatísticas sobre a utilização de versões diferentes do MediaWiki.