Page MenuHomePhabricator

Sunset the LocalisationUpdate extension
Closed, ResolvedPublic2 Estimated Story Points

Description

Context

Language team has enabled translation backports as a service in 2022. This is for most parts the same thing that Localisation Update (LU) extension does. By doing it "as a service", people using MediaWiki releases do not need to setup LU to get updated translations.

Wikimedia has stopped using LU long time ago. To our knowledge, even though LU is shipped with MLEB and bundled with MediaWiki tarballs, there are no or very few users of the LU extension, because it needs to be enabled separately.

The goal is for the Language team to stop maintaining the Localisation Update extension.

Differences

Translation backports run on a weekly schedule. Wikis get updates either by following the stable release branch in git, or by updating to maintenance release of MediaWiki.
Localisation Update can be configured to run on any schedule, not dependent of other updates.


Translation backports supports MediaWiki core, extensions and skins hosted on Gerrit. There isn't yet support for extensions or skins hosted elsewhere.
Localisation Update can in theory support any hosting, but requires special configuration.


Translation backports does not require any setup.
LocalisationUpdate is slow (when using GitHub mirrors) and require special configuration.

Proposed plan

Event Timeline

Yes, but the Language team is still interested in working with release engineering to achieve more frequent translation updates. The solution is unlikely to include the LocalisationUpdate extension.

@Lens0021 You have an open patch for this extension. I'm curious to hear your thoughts on this proposal.

@Lens0021 You have an open patch for this extension. I'm curious to hear your thoughts on this proposal.

A major MediaWiki release contains many new messages and there are commonly not translated before the release, especially for extensions not deployed by Wikipedia. As maintenance releases have no regular schedule to release, I prefer LU. With translation backports, foreign users on not-WMF wikis might have to encounter many not-yet-translated messages for a random period.

But I respect the decision of your team. Thank you for asking my thoughts.

Nikerabbit set the point value for this task to 2.Mar 31 2022, 11:09 AM

As maintenance releases have no regular schedule to release, I prefer LU.

Maintenance releases are released on a schedule, every three months. See the release policy.

Change 790356 had a related patch set uploaded (by Jforrester; author: Jforrester):

[mediawiki/tools/release@master] [DNM] Stop branching LocalisationUpdate for the MediaWiki tarball

https://gerrit.wikimedia.org/r/790356

Change 792222 had a related patch set uploaded (by Nikerabbit; author: Nikerabbit):

[translatewiki@master] Remove LocalisationUpdate from MLEB

https://gerrit.wikimedia.org/r/792222

Change 792222 merged by jenkins-bot:

[translatewiki@master] Remove LocalisationUpdate from MLEB

https://gerrit.wikimedia.org/r/792222

I think it's okay to move forward and mark the extension unmaintained as next step. @Lens0021 are you planning to keep using the extension? In that case we are not going to request archiving.

@Lens0021 are you planning to keep using the extension? In that case we are not going to request archiving.

I removed my usage earlier this month. Thank you, anyway.

I guess Miraheze wikis use LU? At least it seems to be installed currently. CC @Universal_Omega

I guess Miraheze wikis use LU? At least it seems to be installed currently. CC @Universal_Omega

Thanks for the ping, Miraheze has now uninstalled it.

Change 790356 merged by jenkins-bot:

[mediawiki/tools/release@master] Stop branching LocalisationUpdate for the MediaWiki tarball

https://gerrit.wikimedia.org/r/790356

I created an archival request task, but for practical purposes I don't think it can be completed until late 2023. People still have time until that to step up and oppose archival or claim maintainership.