This article is available in other languages on mediawiki.org.
Wikimedia engineers are putting the final touches to the latest version of MediaWiki, the software that powers Wikipedia and its sister sites. This version, labeled “1.19wmf1″, will be deployed to Wikimedia sites in stages, starting next week.
We’ve recently set up a Beta cluster, replicating a selection of Wikimedia wikis, where Wikimedians have tested the new version and checked that it worked reasonably well with their local wiki’s specific customizations.
Things are looking good, and the current plan is to run the deployment in five stages between February 15th and March 1st, 2012. The schedule may change based on unexpected issues, so you should refer to the MediaWiki 1.19 roadmap for an up-to-date schedule of when your wiki will be affected.
Many new features and bug fixes brought by MediaWiki 1.19 are back-end, behind-the-scenes changes, for example infrastructure work to support our ongoing move to Swift as our media storage platform.
There are also more visible improvements, like better diff readability for colorblind people, and better support of the user’s gender and language in the interface. A list of all changes is available in the draft release notes.
Furthermore, a new version of ResourceLoader will be deployed later this year, that will bring improvements specific to gadgets, but will require gadgets to be made compatible with ResourceLoader.
Moving towards transparent upgrades
As we move towards more frequent software upgrades, we expect them to be less and less painful — and ideally, at some point they’ll go so smoothly that users won’t even notice them, except for the new features that will appear. We’re not completely there yet, but we’ve made progress in the past year or so, and we’re committed to continue our efforts, both for the benefits of developers and users.
In the meantime, please bear with us if, despite our efforts, you encounter issues due to the upgrade; we’ll try and fix them as soon as we can. It’s not too late to visit the Beta cluster and report issues there or in our bug tracker. The more people test beforehand, the smoother the deployment should go.
Technical communications manager