Hi Jörg,
the answer here comes in a couple of facets:
For one, now that we have cross-channel, a file rename isn't actually a
rename, but a copy. You use a new file for 61, but continue to use the
old file for 60 and older. Once 60 goes EOL, the old file will be removed.
During that time, fixes that localizers want to land across channels
need to land in each copy.
Now to the tooling side: Pontoon doesn't have copy or move detection in
its vcs sync algorithms. That means, if we want to follow the copy in
the localizations, we need to handle this like we handle other migrations:
- we take the regular updates to gecko-strings-quarantine
- we create a scheduled time to sync
- in that sync
-- switch of sync on pontoon
-- migrate and push all localizations
-- push quarantine to gecko-strings
-- switch pontoon sync back on
-- some validation that sync got the right strings back into pontoon
As you can see, that's quite a bit of work. For Firefox, that work's
mostly on flod and matjaz.
Axel
Am 25.03.18 um 03:08 schrieb Jorg Knobloch: