From Fedora Project Wiki

< BugZappers

Revision as of 14:13, 24 May 2008 by ImportUser (talk) (Imported from MoinMoin)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Fedora Bug Life Cycle

Background

This bug state flow came as a result of the bug triage relaunch that started in January 2008. This work flow was approved at the meeting on January 24, 2008 . As a work flow these are not hard and fast rules to impose on people. Instead it is intended to bring more uniformity and predictability to the life of a bug. If you have a good reason to break them, feel free. This is the process the triage team will follow.

Overview

[[Image:BugZappers_BugStatusWorkFlow_fedora-bug-lifecycle.png]

Source: File:BugZappers BugStatusWorkFlow fedora-bug-lifecycle.odg

NEW

When a reporter files a bug, the report automatically starts out in a NEW state. The triage team will be primarily looking at bugs in this state. From this state, the triage team will change the status to:

  • ASSIGNED--the bug is well defined and triaged
  • NEEDINFO--additional information is needed from the reporter
  • CLOSED--duplicate of an existing bug or another closure reason

ASSIGNED

The triage team believes that this is a complete actionable bug and contains enough information for the package maintainer to investigate the issue with upstream or fix the bug. For example the reporter has included one or more of the following:

  • clear steps describing how the bug occurred
  • clear steps describing how to reproduce the problem
  • stack trace for a crasher
  • various log files
  • AVC message for SELinux

MODIFIED

When a maintainer has a fix for a bug checked into CVS the bug should be placed in the MODIFIED state. This is an indication that the fix is checked into CVS and has potentially been submitted to be built in a new package. Adding a link to package in koji is very helpful for adventuresome testers and the original bug reporter to verify the fix.


ON_QA

A bug automatically transitions to this state when an updated package is submitted to bodhi for a particular bug and the package is in the testing repo. This tells the bug reporter that a fix for the bug is available and that they should test the package. After testing the package the bug tester or original reporter should put feedback in bodhi and add a comment to the Bugzilla.


CLOSED

Once a package update in Bodhi is moved to the stable (updates) repo, the bug will automatically be CLOSED-TBD by bodhi.


NEEDINFO

Bugs are placed in NEEDINFO by bug triagers when adequate information is missing to move the bug towards resolution. NEEDINFO bugs are eligible for closure (changed to CLOSED) by the triage team after all of the following have been met: 1. Bug was original placed in NEEDINFO by a triager or package maintainer 1. Requested information requested has not been provided 1. Bug has been in NEEDINFO for thirty (30) continuous days.

A stock message will be used by all triagers for bugs meeting this criteria. Stock bug triaging messages are found at: BugZappers/StockBugzillaResponses