Hey all, As mentioned in [#757792] (again!), some master translations keep being preserved even if the strings actually being translated/reviewed at that point has changed through major releases (3.14, 3.16, 3.18..) and sent into string-freeze branches. This stops new translations from getting in, and since the strings actually being preserved for are sent into string-freeze branches, we should *transfer all the status and comments (so there is a status history) of that master into the frozen branch*. Therefore, master, with all those new things, can continue being worked on, and the old status can keep together with their old friends. Since in [#757792] Claude Paroz mentioned that some teams used persistent preserving to keep attributing some modules to the same person, this feature should be optional. Other possible proposals are appreciated, as long as there can be some kind of consensus. The damned lies system should have some capabilities to solve common jams in the workflow without a coordinator, I think. EXAMPLE ------- For a given module gnome-foo, at some commit 1234fed a string-frozen branch gnome-3-42 is forked: 1. All the status and comments on the previous master is moved into the archive for gnome-3-42. 2. The master branch resets to its default status "None", with no comments at all. 3. When people visits 'gnome-foo' at master, they may still see a 'ongoing activities' warning; this is intentional, and translators can continue their work on the previous ones. (link for those lazy ones:) [#757792]:https://bugzilla.gnome.org/show_bug.cgi?id=757792 -- Regards, Arthur2e5 (0x222D7BDA)
Attachment:
signature.asc
Description: OpenPGP digital signature