My thoughts were confused yesterday and I could not find or recreate the script that showed which bug supervisors need APGs and structural subscriptions. You might want to declare this bug complete and treat this as bug 1008538. I will update that bug too.
-- Under the old rules the default person to get private bug mail
-- is the maintainer. The maintainer may set the bug supervisor to
-- himself (a no-op) or to a team that he belongs to.
-- Under the new rules, the maintainer gets full access by default,
-- but the bug supervisor gets no access because the role exists
-- to deletegate bug triage, so the team can be inclusice.
-- We only want to share USERDATA with exclusive bug supervisor teams
-- for active projects that use Lp Bugs.
-- these team need a structural subscription for with a USERDATA filter.
select p.name, bs.name
from product p
join person bs on p.bug_supervisor = bs.id
where
p.active is true
and p.official_malone is true
and bs.teamowner is not null
and bs.subscriptionpolicy in (1, 3)
and p.owner != p.bug_supervisor
-- and p.driver = p.bug_supervisor
order by bs.name
;
-- (758 rows) on staging.
-- common practive is to set the driver team as the bug supervisor to
-- ensure the people who plan releases can see the bgus.
-- (378 drivers get proper access which includes all Canonical projects)
Hi Ian.
My thoughts were confused yesterday and I could not find or recreate the script that showed which bug supervisors need APGs and structural subscriptions. You might want to declare this bug complete and treat this as bug 1008538. I will update that bug too.
-- Under the old rules the default person to get private bug mail policy in (1, 3)
-- is the maintainer. The maintainer may set the bug supervisor to
-- himself (a no-op) or to a team that he belongs to.
-- Under the new rules, the maintainer gets full access by default,
-- but the bug supervisor gets no access because the role exists
-- to deletegate bug triage, so the team can be inclusice.
-- We only want to share USERDATA with exclusive bug supervisor teams
-- for active projects that use Lp Bugs.
-- these team need a structural subscription for with a USERDATA filter.
select p.name, bs.name
from product p
join person bs on p.bug_supervisor = bs.id
where
p.active is true
and p.official_malone is true
and bs.teamowner is not null
and bs.subscription
and p.owner != p.bug_supervisor
-- and p.driver = p.bug_supervisor
order by bs.name
;
-- (758 rows) on staging.
-- common practive is to set the driver team as the bug supervisor to
-- ensure the people who plan releases can see the bgus.
-- (378 drivers get proper access which includes all Canonical projects)