Further discussion with Curtis and the team working on implementing disclosure has resulted in Curtis' list of conditions to be revised to remove the project roles clause. So a user will be allowed to change a branch to private if:
* The branch visibility policy allows it (for legacy support until BVP is removed)
* The user is special (admin or bzr expert)
* The branch is owned by a private team (The branch is already implicitly private)
* The branch is linked to a private bug (embargoed security, user data, proprietary) the user can access
"Change to private" means setting the information type to a private value (embargoed security, user data, proprietary). Otherwise, just the public values are allowed (public, unembargoed security).
Further discussion with Curtis and the team working on implementing disclosure has resulted in Curtis' list of conditions to be revised to remove the project roles clause. So a user will be allowed to change a branch to private if:
* The branch visibility policy allows it (for legacy support until BVP is removed)
* The user is special (admin or bzr expert)
* The branch is owned by a private team (The branch is already implicitly private)
* The branch is linked to a private bug (embargoed security, user data, proprietary) the user can access
"Change to private" means setting the information type to a private value (embargoed security, user data, proprietary). Otherwise, just the public values are allowed (public, unembargoed security).