Privileges required for release nomination approval/declination are relaxed to those of the lowest involved component

Bug #125994 reported by William Grant on 2007-07-14
2
Affects Status Importance Assigned to Milestone
Launchpad itself
High
Unassigned

Bug Description

This is probably intimately related to bug #110195. I was looking through +nominations, and saw some entries there that I shouldn't have. Bug #77442 is one of them. It has proposed Gutsy tasks on 3 source packages. Further investigation showed all the source packages to be in main (or not, after realising bug #93293 was at work). vnc was demoted to universe, but that shouldn't grant me permissions to approve tasks over two packages in main!

Henrik Nilsen Omma (henrik) wrote :

Nominations and approved target lists separated by component (main, universe) would be very useful for those of us focusing on mainly one component.

The stable release process is slightly different for main and universe: in main the Ubuntu release team requires a strict adherence to the SRU policy to minimise breakage in supported parts of the stable release. In universe it is more up to individual MOTU developers whether a bug should be fixed with an update.

The motu-sru team would tend to focus exclusively on the nominated and approved bugs for universe, while the core QA team focuses on main, so separate lists would help both teams.

Changed in malone:
importance: Undecided → Medium
status: New → Triaged
Robert Collins (lifeless) wrote :

Probably still relevant in a packageset world :(

Changed in launchpad:
importance: Medium → High
Curtis Hovey (sinzui) on 2012-09-17
tags: added: bug-nomination
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers