GNOME Bugzilla – Bug 619124
ability to lock a branch
Last modified: 2018-05-22 12:09:11 UTC
It'd be interesting to have the ability to lock some branches for translation. For instance: Brazilian team don't translate master branch until we get string announcement period. But unfortunately new translators don't know that and start translating the branch. So, the team coordinator could lock a branch. This branch would be in 'read-only' mode, and a big banner would appear in all pages inside a locked branch telling it's locked.
Here is my answer to Henrique who wants to try to address this issue and who asked me about the best approach: a) Add a locked boolean field in the statistics table (+ locked_comment?) as this might be used for other use cases as well (maybe a coordinator wants to arbitrarily lock some branch for a particular reason). b) Add a function to lock all branches of a release (from the /languages/<locale>/<release>/<domain>/ page, with an intermediary form allowing to specify the reason of the lock. All this will take some work, but can be done step by step: 1. Add the new fields in statistics table 2. Adapt the display according to the new fields (3. Add a form for coordinators to set/unset lock at individual branch level) 4. Add a form for coordinators to set/unset lock at release level (that is for each statistics object in branches of the release). I would appreciate having separate patches for each step.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/damned-lies/issues/19.