Right now when a revision is locked down to members of a project (representing a bugzilla security group) a custom policy is used for the revision. It's hard to inspect what exactly this custom policy does (you must edit the revision, click to change the policy, then re-click custom policy and the details are shown in the editor). We should add the bmo-* project as a tag to the revision as well to make it more obvious what is going on.
Assignee: nobody → dkl
Status: NEW → ASSIGNED
See no reason for this to be private.
Merged into master.
Status: ASSIGNED → RESOLVED
Last Resolved: 9 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.