Skip to Content.
Sympa Menu

perfsonar-dev - Using bugzilla - effectively

Subject: perfsonar development work

List archive

Using bugzilla - effectively


Chronological Thread 
  • From: Loukik Kudarimoti <>
  • To: "" <>
  • Subject: Using bugzilla - effectively
  • Date: Tue, 11 Mar 2008 13:44:30 +0000

Dear all,

The status page below gives us an indication of the status of all bugs assigned to all products. I suggest we all bookmark it as it will be the basis for monitoring various tasks related to our products

Its here: http://tinyurl.com/yv2qo3

From problem management and release management point of view - Developers of their respective products should aim to apply correct status to the bugs as per the guidelines outlined in the problem management process documentation (which is yet to be published). While we await the full document, here is an extract from the document which briefly describes how to use bugzilla and the states.

Basically the bugs can be in one of the following states.

** *New* *- Bugs that have been reported but acknowledged

** *Assigned - A bug for which the developer has acknowledged that he has seen it and will investigate it (a bug has to enter this state)

** *Assigned – Request for Change – If a change is required and is currently being processed

* Resolved - A bug for which there is now one of the following resolutions is available.

/- Fixed/ (as workaround) - Provide workaround, provide pointer to FAQ entry

/- Fixed/ (by change) - Provide version number released which fixes the bug

/- Won't fix/ - Bug is present but for some reasons, we won't fix it for now - provide reasoning in the description

/- Duplicate/ - Bug is a duplicate of another bug - provide pointer to the other bug (which will be updated and should be referred to)

Reopened – A previously resolved bug has been reopened. The reason for reopening the bug will be included in the comments on the bug.

Verified* *– If the bug reporter and/or the testing process verifies that a bug is fixed (either by workaround or by change) then the bug enters this state*
*

Closed - A bug is closed either because its verified or because the verification process timed out.


A flow diagram which details how the states can change from one to another is in attachment. Please let me know if you have any questions related to this.

regards,

---------------------------------------------------------------
L o u k i k K u d a r i m o t i

* * Network Engineer
* * City House, 126 - 130, Hills Road
* Cambridge CB2 1PQ, United Kingdom
* WWW: http://www.dante.net
D A N T E Tel:+44 1223 371300 Fax:+44 1223 371371

JPEG image




Archive powered by MHonArc 2.6.16.

Top of Page