Page MenuHomePhabricator

Consider two core backports to 1.36.0-wmf.22 (for now untranslated `User contributions` on Special:Contributions)
Closed, ResolvedPublic

Description

Related to: T270543: User contributions page title italian translation bug.

Would it be possible to do a couple of backports to fix the title display in Special:Contributions across WMF wikis? I know we're in the code-freeze weeks and that's why I am asking. The commits would be:

After rMW7fff9280afee: Merge "Avoid reuse of message contributions for linking" got merged the title in Special:Contributions no longer uses tool-link-contributions but contributions. This has caused that User contributions in said Special:Contributions page appear untranslated at all wikis now which is causing confusion (see eswiki VP thread for example).

While localisation updates have happened, they've not been branched/deployed and therefore we're having an untranslated string in a very high-traffic page and in a prominent location.

To fix this we're creating local MediaWiki messages, which we'll need to have them deleted later. Double work.

Inconvenience of doing these backports are mostly that given that they're localisation updates a full scap and full localisation cache update is needed, which takes quite some time. But on the other hand given that the Deployments schedule is empty, it shouldn't conflict with other works. They are not PHP or other "dangerous" code, just translations updates which should be "safe" enough to do.

Considering that we're in the code-freeze weeks I am filing this task to ask Release-Engineering-Team to determine whether they'd be willing to do those two backports to fix this.

In any case, thanks for your attention to this matter.

Event Timeline

While this problem doesn't seem like a major loss of functionality, it does look like it's creating some work that could be avoided.

l10n isn't as safe of a deployment as I'd like it to be. A change in a single string means rebuilding all l10n and deploying it with no review and no way to rollback. Rebuilding l10n with fewer people than normal around in case something goes awry is not desirable.

Are there other options to mitigate this problem?

Is partially reverting 7fff9280afee an option (or adding a "hack" somehow) so Special:Contributions use the old message until RelEng is fully back in January? I'm no expert though.

Aklapper renamed this task from Please consider doing two core backports to 1.36.0-wmf.22 to Consider two core backports to 1.36.0-wmf.22 (for now untranslated `User contributions` on Special:Contributions).Dec 21 2020, 4:46 PM

Cherry-picking the following chain of L10n-bot commits works: 649497 649772 650035 650411 651021.

Mentioned in SAL (#wikimedia-operations) [2020-12-21T18:09:32Z] <dancy@deploy1001> Started scap: Backport of l10n changes for T270619

Thank you for your help @thcipriani and @dancy. Best regards.

Mentioned in SAL (#wikimedia-operations) [2020-12-21T18:30:38Z] <dancy@deploy1001> Finished scap: Backport of l10n changes for T270619 (duration: 21m 12s)

l10n updates have been rolled out. Lemme know how it looks.

l10n updates have been rolled out. Lemme know how it looks.

It looks good. I checked es.wikibooks and the message now appears translated. Same for it.wikipedia apparently (cfr. T270543: User contributions page title italian translation bug). What remains now is to restore Gender-Support for contributions which has been lodged as T113346: Add GENDER to username related strings on Special:Contributions.

If you and @thcipriani concurr as well, I'd say this is resolved.

Great! Closing.

Thank you again for you consideration and for making an exception for this. I appreciate your work.