BugZappers/F9CleanUp/RunTime

From FedoraProject

< BugZappers | F9CleanUp
Revision as of 00:51, 19 May 2009 by Poelstra (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Contents

Fedora 9 Bug Clean Up Results

Note.png
This page contains the results and latest status of from running the changes from the F9 Cleanup Proposal

tracker bugs

  1. Run date: 2008-03-27
  2. Query all tracker and blocker bugs
  3. Change applicable bugs to carry Tracker keyword
  4. Status: DONE

EOL Phase 1

  1. Run date: 2008-04-03
  2. Query to capture qualifying bugs: http://preview.tinyurl.com/3cd97j
  3. Actions
    1. Add the following string to the 'Status Whiteboard' field: 'bzcl34nup'
    2. Change bug status to NEEDINFO
    3. Add fedora-triage-list@redhat.com to the CC list
    4. Add the following comment:
  4. Status:
    1. Actions run
    2. Need to finish reviewing all email confirmations and comments from fedora-triage-list

EOL Phase 2

  1. Run date:
  2. Query to capture qualifying bugs:http://preview.tinyurl.com/6j7ddm
  3. Actions:
    1. Change bug status to CLOSED:WONTFIX
    2. Add comment wording:
  4. Status: Completed May 2008

Stale Phase 1

  1. Run date: 2008-04-04
  2. Query to capture qualifying bugs: http://preview.tinyurl.com/2j6sua
  3. Actions
    1. Add the following string to the 'Status Whiteboard' field: 'bzcl34nup'
    2. Change bug status to NEEDINFO
    3. Add fedora-triage-list@redhat.com to the CC list
    4. Add the following comment wording:
  4. Status:
    1. Actions run
    2. Need to finish reviewing all email confirmations and comments from fedora-triage-list

Stale Phase 2

  1. Run date:
  2. Query to capture qualifying bugs: http://preview.tinyurl.com/46vpfv
  3. Actions:
    1. Change bug status to CLOSED:INSUFFICIENT_DATA
    2. Add comment wording:
  4. Status: Completed May 2008

Relevant

  1. Run date: 2008-04-04
  2. Query to capture qualifying bugs: http://preview.tinyurl.com/38l8wn
  3. Actions:
    1. Add the following string to the 'Status Whiteboard' field: 'bzcl34nup'
    2. Change 'version' to: '8'
    3. Add fedora-triage-list@redhat.com to the CC list
    4. Add comment
  4. Status:
    1. Actions run
    2. 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:
    1. only send one email notification
    2. NOT send mail to fedora-triage-list for initial change
  2. (2008-04-04) Using fedora-triage-list as CC to collect mail is working well
    • gives multiple people the ability to triage resulting updates
  3. (2008-04-07) Does fedora-triage-list bugzilla user need to have a Fedora Account and Fedora bug privs?
  4. (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
  5. (2008-04-07) In the context of Fedora and our inability to successfully maintain more than two releases
    1. Is there ever a situation where it makes sense to keep bugs open for an EOL release?
    2. Could there be a way for maintainers who desire to keep bugs open for EOL releases to do so?
  6. What should happen to bugs that are Features--FutureFeature keyword is set?
    1. Has FutureFeature been set on all applicable bugs? Is this a formal part of Fedora bug handling procedures?
    2. Should they remain rawhide?
    3. Should they be rebased at GA?
    4. Should they ever be auto-closed if a certain period of time goes by with no activity?