Currently the "development" repository group includes repos such as mozilla-central, mozilla-inbound etc (which is fine), but also includes the releng rentable repos such as cedar, ash, oak. In addition there are teams that have semi-active team repos that perhaps don't belong alongside mozilla-inbound etc. I'm thinking that it would be good to distinguish between mozilla-central et al and cedar/ash/... for the purposes of: * making the repos menu clearer (ie having a separate list for both) * assigning permissions (when we have more granular treeherder permissions in the future) * assigning job exclusion profiles to one group but not the other I'm thinking perhaps we could call the new repo group "project", ie: development: * mozilla-central * mozilla-inbound * fx-team * gaia-master ... project: * ash * cedar * services-central ... @sheriffs: Thoughts?
Summary: Use a separate repository group for the rentable twig repos → Repo menu: Use a separate repository group for the rentable twig repos
Created attachment 8486607 [details] [review] Move twigs and other project branches into their own category In theory, this splits all of the twigs and a few other project repos out to their own category. I haven't tested this at all, but it looked right to me.
Attachment #8486607 - Flags: review?(cdawson)
Attachment #8486607 - Flags: review?(cdawson) → review+
Assignee: nobody → kwierso
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.