@siebrand we are in the middle of rebuilding the UI/UX of the app - so are not merging localization updates until the UI is completed since the string requirements will be different than the current shipping app.
Expect us to loop back around to this later this month.
Also when you need to file a bug, please use the product board here: https://phabricator.wikimedia.org/project/board/782/
This board is one for work that has been groomed, speed, and estimated. Thanks!
we are in the middle of rebuilding the UI/UX of the app - so are not merging localization updates until the UI is completed since the string requirements will be different than the current shipping app.
I don't understand what this means. This is l10n for the latest code, you want it now not later.
Also, "merging l10n when the UI is complete" is a practice which got old in the 1980s. Please join us in the 21st century. :)
Localizations aren't the only thing that are on hold, and we realize it's not an ideal situation. We're working hard to get the app ready for release, and hope to get everything back to normal soon.
I spoke briefly with @Nikerabbit who mentioned it would be feasible to push localization changes directly to master on GitHub. Here's what I'm thinking:
- Manually "merge" localization changes from current Gerrit patch
- Remove TWN pages related to .strings files that were removed on master (localizations ported to another file)
- Reconfigure TWN to push future updates directly to our master branch
I can take care of #1, could one of you help me with #2 if I tell you the files that need to be removed? If so, we could re-establish sync and resolve this issue now.