ReactOS Bugzilla Maintainer

Bugzilla Maintainer

This page describes the work of the bugzilla maintainer.

Now, Amine Khaldi is the Bugzilla Maintainer.

1. You check for new bugs (using ros-bugs, and deskzilla). New bugs found -> processing each bug:
- a. Check its description, if it looks valid. If it's some spam, you close the bug with resolution INVALID
- b. Check how much information is given, if it's a "ReactOS BSODs when I run Vista installer on it", further clarification is needed like providing a debug log, an environment (qemu, vmware, real hw, in case of real hw - what hw more exactly)
- c. If the above is not given - add a comment (keeping the bug unassigned and opened) asking for more information.
- d. When there is enough information, you look over it, and make a preliminary decision who of the devs would be responsible (according to the Developer Roles). That means, you perform an assign operation in bugzilla to a corresponding dev. It's not going to be a huge mistake if you assign to a wrong dev, since that dev is going to reassign to another if he doesn't feel he's closing this bug.

2. For bugs which are not touched for a long time (1 month and more), you review their contents, and add a comment about validity of the bug (if it still happens, maybe it's fixed in newer revisions)

3. For modified bugs you just look if they have an assigned owner, if not - assign one