Future-proofing: HTML5 and IPv6

1.20wmf12, the 12th release to Wikimedia wikis from the 1.20 branch, was deployed to its first wikis on September 17; if things go well, it will be deployed to all wikis by September 26. Its 200 or so changes – 111 to WMF-deployed extensions plus 98 to core MediaWiki code – include support for links with mixed-case protocols (e.g. Http://example.com) and the removal of the "No higher resolution available" message on the file description pages of SVG images.

Those responsible for overseeing this latest series of deployments to Wikimedia wikis will be hoping for a smoother ride with wmf12 than wmf11, which started its deployment cycle two weeks ago and has been causing problems ever since. First it was Wikimedia Commons, where bug #40018 (describing the duplication of the "This file is from Wikimedia Commons" page) forced a temporary reversion to wmf10 on September 5. Then it was a breakage in the "blue star" (watch) facility, reported as bug #40103 and which caused a reversion to wmf10 lasting some 40 hours.

The later bug (as well as other, more minor issues) stem from the decision to update the version of jQuery packaged with MediaWiki from 1.7.2 to 1.8. However, while some problems with LiquidThreads remain, both of the major issues have since been resolved, and as a result all Wikimedia wikis were running wmf11 in time for the wmf12 series to begin in earnest.

Despite these difficulties, this series of events may serve to demonstrate the robustness of the new regular deployment schedule: the disruption caused by the deploy–revert pattern undertaken with wmf11 (a package of some 250 changes) has been far less than for almost any problematic deployment under the previous release scheme, when thousands of revisions were deployed and reverted at the same time. But inevitably the completeness of the current JavaScript regression testing regime is likely to be questioned in light of the issues experienced.

In related news, work on a release from the 1.20 branch suitable for use on external wikis (whose system administrators often do not want the disruption of fortnightly updates) resulted in two beta-releases this week (wikitech-l mailing list). Former bugmeister Mark Hershberger has taken on the role of overseeing the creation of a release based on the 1.20wmf11 branch. It will now receive only a limited number of updates to avoid introducing new bugs, ensuring the emergence of a stable product suitable for general distribution. Hershberger, who is involved with one such external wiki, reported that he is targeting an early October release date for 1.20.

Signpost poll

iOS app

You can now give your opinion on next week's poll: What best sums up your view of the interaction between the Wikimedia Foundation and external sites?

Not all fixes may have gone live to WMF sites at the time of writing; some may not be scheduled to go live for several weeks.

• HTML5 coming to wikis: As previewed in last week's "Technology report", HTML5 mode was enabled Wikimedia-wide on September 17. Overall, no immediate change to users' browsing or editing experience was expected – rather, the update was built to "future-proof" existing features and allow new ones (such as better video handling) to be developed – but small visual deficiencies were projected. As of the time of writing, only one problem has been reported – with text alignment in table cells. Any further problems can be reported on bugzilla.wikimedia.org (free registration required). HTML5 had already been successfully enabled on MediaWiki.org for some time on a trial basis.
• Wikimedia wikis face no issues as European IPv4 space runs out: As widely reported across the world, the RIPE NCC became the second of the world's five regional internet registries (RIRs) to enter the final phase of the global scheme for handling IPv4 exhaustion. RIPE, which covers Europe and parts of the Middle East and Central Asia, joins APNIC (the Australasian registry) in the final stage of version 4 IP address distribution, whereby consumers of the addresses (of the form xxx.xxx.xxx.xxx) will only be able to register 1024 more, suggesting web providers should be prepared for a boom in the usage of version 6 addresses. Fortunately, as we reported in June, MediaWiki is more or less able to handle IPv6 addresses properly, and it is enabled on all Wikimedia wikis, though some users may want to update their user scripts and/or tools to accommodate the newer addresses as more providers adopt them. Other remaining issues include presentational concerns as well as the lack of a functional "range contributions" tool to facilitate the calculation of rangeblocks. Statistics suggest that IPv6 addresses account for some 50 million Wikimedia pageview requests daily.
• Limn gains extra datasets, new developer: It was announced this week that Cornell graduate Dan Andreescu will be joining the Foundation's analytics team. Andreescu, a builder at heart, he says, will work on Limn, the WMF's new data visualisation and dashboard building toolkit, as well as a frontend for Kraken, its sister program focussing on data collation. Limn also surfaced this week as the chosen framework for a new Gerrit stats module; the module currently provides four time-series relating to code review via Gerrit). The Signpost hopes to publish its own investigation into the code-review backlog in the near future, responding to a request by WMF engineering community manager Sumana Harihareswara.
• Wikipedia Redesigned, revisited: Following the publication of a controversial "redesign" of Wikipedia's main interface by brand consultancy NewIsNew back in early August, one Wikimedian has now turned the design into a rough-and-ready gadget on the German Wikipedia. The gadget is likely to spur renewed interest in the design, which was criticised at the time for a lack of attention to internationalisation and multilingual issues – considerations that factor heavily in current MediaWiki thinking.

← Previous "Technology report"

Next "Technology report" →

In this issue

17 September 2012 (all comments)

From the editor

WikiProject report

Featured content

News and notes

Technology report

+ Add a comment

Discuss this story

These comments are automatically transcluded from this article's talk page. To follow comments, add the page to your watchlist. If your comment has not appeared here, you can try purging the cache.

• If you guys are running scripts using jsMsg for interfaces, you can use this library to emulate the old interface. Give Tim a high five for writing this, which has already fixed the bug in several scripts. --Nathan2055^{talk - contribs} 18:39, 18 September 2012 (UTC)[reply]
• On Wikipedia Redefined: Magnus Manske also has a prototype running on the Toolserver. Jean-Fred (talk) 20:49, 18 September 2012 (UTC)[reply]
• RE next week's poll: what exactly do you mean by an "external site?" Is en.widkipeia an external site or is that concept more like Wikia? --agr (talk) 14:06, 19 September 2012 (UTC)[reply]
  • I assume it means any non-Wikimedia wiki. Powers ^T 01:59, 20 September 2012 (UTC)[reply]
• I'm a little surprised only 15% of respondents to last week's poll don't have an iOS device. Powers ^T 01:59, 20 September 2012 (UTC)[reply]
  • The poll question asks about adding a Signpost app "to your iOS device." People without one may not bother to look at the possible responses. Maybe we need some process for editorial review of these poll questions. This week's and last's seem poorly worded.--agr (talk) 04:35, 20 September 2012 (UTC)[reply]
• The questions are usually fairly clear, but I had trouble understanding this week's question. --Philosopher ^{Let us reason together.} 14:43, 20 September 2012 (UTC)[reply]

  +1 Philosopher. I assumed this was about folks who use MediaWiki freeware on their own websites, but it might be taken to be about whether any external site (such as "I hate Wikipedia" blogs and forums) deserves some consideration. ~ Ningauble (talk) 19:36, 20 September 2012 (UTC)[reply]

Sorry, yes, I think the meaning of this week's question is (in retrospect) more obvious from the answers than the question. It meant, generally, any reuser (or potential reusers) of MediaWiki development, which in practical terms means sites hosting non-Wikimedia wikis. I agree that non-iOS owners may not have clicked through, but I wanted to give those that did something to click in order to make it clear that we were, for once, excluding hypothetical answers. - Jarry1250 ^{[Deliberation needed]} 15:38, 23 September 2012 (UTC)[reply]