Launchpad Janitor's behavior interferes with the Feature Freeze Exception process
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Won't Fix
|
Undecided
|
Unassigned | ||
Bug Description
Launchpad Janitor changes bug statuses to 'Confirmed' when the bug is marked as affecting multiple users. Normally this is fine, but it interferes with Ubuntu's Feature Freeze Exception process.
People who would like to see the FFe granted will "vote" for the bug causing janitor to set it as Confirmed. This shouldn't happen to FFe bugs as the release team wants those bugs to stay New until they have been reviewed by a release team member. From the policy:
"The bug should be set to status of "New" when requesting a freeze exception, to ensure the release team sees the request."
https:/
Normally, these bugs will have titles starting with "FFe:" or "[FFe]" and have ~ubuntu-release subscribed. Could they be special cased in janitor?
| William Grant (wgrant) wrote | #1 |
| Changed in launchpad: | |
| status: | New → Won't Fix |
Bug autoconfirmation is an experimental feature that was requested by Ubuntu's bug managers, and it is already a special case for Ubuntu. We won't additionally special case it on the bug summary -- in fact we'd prefer to remove the autoconfirm feature entirely. You should dicuss this with Ubuntu's bug management teams.