< BugZappers | F9CleanUp
Fedora 9 Bug Clean Up Results
tracker bugs
1. Run date: 2008-03-27 1. Query all tracker and blocker bugs 1. Change applicable bugs to carry Tracker keyword 1. Status: DONE
EOL Phase 1
1. Run date: 2008-04-03 1. Query to capture qualifying bugs: http://preview.tinyurl.com/3cd97j 1. Actions a. Add the following string to the 'Status Whiteboard' field: 'bzcl34nup' a. Change bug status to NEEDINFO a. Add fedora-triage-list@redhat.com to the CC list a. Add the following comment: 1. Status: a. Actions run a. Need to finish reviewing all email confirmations and comments from fedora-triage-list
EOL Phase 2
1. Run date: 1. Query to capture qualifying bugs:http://preview.tinyurl.com/6j7ddm 1. Actions: a. Change bug status to CLOSED:WONTFIX a. Add comment wording: 1. Status: Scheduled for 2008-05-08
Stale Phase 1
1. Run date: 2008-04-04 1. Query to capture qualifying bugs: http://preview.tinyurl.com/2j6sua 1. Actions a. Add the following string to the 'Status Whiteboard' field: 'bzcl34nup' a. Change bug status to NEEDINFO a. Add fedora-triage-list@redhat.com to the CC list a. Add the following comment wording: 1. Status: a. Actions run a. Need to finish reviewing all email confirmations and comments from fedora-triage-list
Stale Phase 2
1. Run date: 1. Query to capture qualifying bugs: http://preview.tinyurl.com/46vpfv 1. Actions: a. Change bug status to CLOSED:INSUFFICIENT_DATA a. Add comment wording: 1. Status: Scheduled for 2008-05-08
Relevant
1. Run date: 2008-04-04 1. Query to capture qualifying bugs: http://preview.tinyurl.com/38l8wn 1. Actions: a. Add the following string to the 'Status Whiteboard' field: 'bzcl34nup' a. Change 'version' to: '8' a. Add fedora-triage-list@redhat.com to the CC list a. Add comment 1. Status: a. Actions run a. Need to finish reviewing all email confirmations and comments from fedora-triage-list
Notes & Observations on Change Process
1. (2008-04-04) We have to change subsequent processes to: a. only send one email notification a. NOT send mail to fedora-triage-list for initial change 1. (2008-04-04) Using fedora-triage-list as CC to collect mail is working well
- gives multiple people the ability to triage resulting updates
1. (2008-04-07) Does fedora-triage-list bugzilla user need to have a Fedora Account and Fedora bug privs? 1. (2008-04-07) Suggestion from notting that a bug not be included in the cleanup effort more than once
- we could probably key off of bzcl34nup for this
- for example if a bug has been moved from FC6 to rawhide, do not rebase it to Fedora 9 at GA of Fedora 9--let it get picked up during the F10 rebase
1. (2008-04-07) In the context of Fedora and our inability to successfully maintain more than two releases a. Is there ever a situation where it makes sense to keep bugs open for an EOL release? a. Could there be a way for maintainers who desire to keep bugs open for EOL releases to do so? 1. What should happen to bugs that are Features--FutureFeature keyword is set? a. Has FutureFeature been set on all applicable bugs? Is this a formal part of Fedora bug handling procedures? a. Should they remain rawhide? a. Should they be rebased at GA? a. Should they ever be auto-closed if a certain period of time goes by with no activity?