The commit https://gerrit.wikimedia.org/r/#/c/233723/ overwrote the localization files - both the updates in English that were done in the last few months and the existing translations.
This created a lot of mess in translatewiki - a lot of fuzzy messages that shouldn't be fuzzy, etc.
I don't know about the functional changes that that commit does, but the localization changes are definitely wrong and must be reverted and cleaned up ASAP.
Thanks for understanding.
Same problem with https://gerrit.wikimedia.org/r/#/c/233726/ (WikibaseQualityExternalValidation) and https://gerrit.wikimedia.org/r/#/c/233725/ (WikibaseQualityConstraints)
@Raymond I think we can do reverts for now but then we still need to sort out our branches on these extensions.
This is a student project and v1 was frozen, so that Chris could do security review and then was deployed.
They continued working on master, which has newer features, but we want to now push it to a feature branch, and then have v1 become the master version.
(imho, it was a mistake to do development in this way, with the branches and think we will try to avoid this with future student projects)
I suppose we can retry the merge, including en.json and qqq.json but excluding the other languages. (afaik translate wiki would update the other languages?)
Change 233932 had a related patch set uploaded (by Aude):
Revert "Make master be like v1 by a merge of master into v1 with strategy ours."
@aude: yes, please exclude all translations. they will be updated with the next export from translatewiki. Important is that en.json and qqq.json are correct as base for our translators.
Change 233932 abandoned by Aude:
Revert "Make master be like v1 by a merge of master into v1 with strategy ours."
Change 233945 had a related patch set (by Aude) published:
Revert i18n files to pre-merge status
Change 233965 had a related patch set uploaded (by Aude):
Revert i18n files to pre-merge status
Change 233959 had a related patch set uploaded (by Aude):
Revert i18n files to pre-merge status