Bugs are found in MediaWiki all the time. Some of these bugs are pretty high priority for the Wikimedia Foundation (eg: security-related or they break needed functionality by the Wikimedia community) and need special care to ensure all of the right users get the fix in the appropriate amount of time. There are three main classes of backports:
- Those that are security related and thus need to be disseminated as widely as possible as quickly as possible;
- Those that need to be applied to any stable or released (and supported) version of MediaWiki
- And those that need to be applied to the Wikimedia Foundation server cluster that hosts the wikis for Wikimedia-related projects.
- If you find a security flaw in MediaWiki, please email email@example.com directly with details. Please give us a couple days to fix the issue and roll out new releases for third-party users before public disclosure.
- These are filed as tickets in Phabricator, but are marked Security and thus are not public before the fix has been released.
- The issue is diagnosed and a solution is created.
- A 'hotfix' is deployed to the WMF Cluster, where all of the Wikimedia Wikis are hosted.
- After this hotfix is deployed a security tarball release of MediaWiki is made for all currently supported versions and made available for download.
Backports to stable/supported release
Not strictly in this order:
- A bug is found that is causing problems to users of released versions of MediaWiki.
- The bug is fixed in the development version of MediaWiki and tested there.
- Someone proposes it to be backported to the Stable/Supported versions of MediaWiki by adding the task to the appropriate MW release project in Phabricator, eg #MW-1.26-release
- The WMF Release Engineering Team determines if the bug is important enough to backport the fix. If not the project is removed again.
- This decision is based on criteria such as: number of users affected, severity of the issue, and complexity of the fix.
- The fix is applied to the Stable version of MediaWiki (ie: cherry-pick'd) with additional tests there and approved by the release manager or anyone else with +2 rights. After the change is approved, the flag is set to "+" to clarify that all is done. See Gerrit/Advanced usage#Submitting a change to a branch for review ("backporting") for more on how to submit the change to the stable branch.
- The RELEASE_NOTES file should be updated for any backports. The RELEASE_NOTES file may cause problems for cherry picking in git, so the MediaWiki Release Manager may ask you to update the RELEASE_NOTES file if you are involved in the backport.
- A new tarball release of MediaWiki may be created and announced at some point.
- There are no clear rules for this. Chris Steipp makes releases only for security reasons. The number of approved changes in the stable branch is also looked at when deciding if a new release is needed.
Backports to WMF cluster
The cluster serving WMF wikis runs pre-release 1.NNwmfXX versions of the MediaWiki software.
- Make sure there is a bug registered in Phabricator for the issue.
- On that bug, associate the "WMF-Server-Backports" project.
- Note: This sends the WMF Release Manager an email.
- The WMF Release Manager determines if the fix for this bug is worthy of being backported to the currently deployed code.
- If yes, they will add a comment
- If no, they will remove the project again
- If yes, then the WMF Release Manager will schedule a deployment window for this fix (depending on when the bug is fixed, of course).
- NB: Do not set the bug to "resolved" until after the fix has been deployed.
- NB: Also, see Gerrit/Advanced usage#Submitting a change to a branch for review ("backporting") for more on how to submit the change to the deployed branches.
For the avoidance of doubt, these fixes should be cherry-picks to reduce the chances of unrelated bugs being deployed.
- During that window, the fix will be deployed to all currently in use wmfXX branches (see the Roadmap for which versions those are).