Bug Overview | Reporting a bug | Bugzilla roster | Instructions for Roster Duty |

All bugs are entered in the EDG Bugzilla Bug Tracking System.

WP2 Bug overview

|top|

Reporting a bug

Click HERE to report a new bug. You have to have an EDG Bugzilla accoung. Please click on one of the WP2 categories (see table above). Please contact hep-proj-grid-data-mgt-support@cern.ch if you need help.

|top|

WP2 Bugzilla Roster

The weekly Bugzilla responsible has to accept and assign new WP2 bugs and has to keep track of existing bugs, sending people reminders for open bugs that have been open for more than 2 weeks (P1, P2) more than 4 weeks (P3) more than 3 months (P4,P5).

Bugzilla responsibles 2003:

|top|

[Internal] Instructions for the Person on Roster Duty

1. When a mail arrives notifying of a bug, follow the link to the bugzilla web page.
2. Make sure that you are logged in as "hep-proj-grid-data-mgt-support@cern.ch". To do this go to the bottom of the bug page and select "Log in". If you are already logged in as another user, select "Log out" and log in again as "hep-proj-grid-data-mgt-support@cern.ch"
3. Make sure it is a real bug. Sometimes users (or us) have just misunderstood something so read the bug and check that what is reported really is what it claims to be. It may be that there is a problem but that the reason is not what the reporter thinks it is. i.e the user will usually see the problems in the client, and will report it as a client side problemm but in fact what is seen may be due to something else.
4. When you (think) you have understood the bug, first you must accept the bug in bugzilla. Click the accept button and submit. If you don't do this then the bug will remain in new state.
5. Decide who to assign to bug to to fix, and assign it to this person. See the roster below to help with your decision. You must assign the bug to a real person at this stage. This person may choose to assigne the bug to someone else who is more appropriate. If the bug is low priority and there is no-one to assign it to, its status may be changed to 'FIXED LATER'.
6. By the end of the week all bugs should be assigned to someone. They do not necessarily have to be fixed, but no new bugs should be in the "new" state.

|top|

[Internal] Primary assignment roster for each component

Each component should be maintainable by several people. Some are faster than others in fixing bugs, but it should not be the fastest who fixes everything othewise the rest of the people won't feel in charge and actually won't know the code base after a while. The assignment roster is a help for the person on roster duty. It is not 100%, people can as usual reassign bugs to others as usual. But everyone should try to fix their bugs themselves to get proper training on the code.