Managing Bugs

This is how we manage bugs. It is here to help bring some transparency while the project Subversion commit status only resides with ZacWare.

Checklist (for bugtracker managers)

• Make use of the status, priority, severity and resolution fields. If you have checked a bug report, mark it acknowledged, or feedback if the original bug poster should elaborate on the issue. If a bug is a duplicate, add the duplicate ID and resolve it.
• Only assign a bug to yourself or someone else if you know that it can and will usually be fixed in a reasonable time frame, say two weeks. Don't assign bugs to the developers for inclusion unless you have a patch ready.
• If you don't get to fix a bug assigned to you, release it and revert the status to "confirmed". This makes re-assigning tasks a lot easier.
• Only bugs in the current stable version will be fixed, which means we have to check if older bug still exists in the current version. Otherwise people should just upgrade.
• Make better use of the infrastructure Bugzilla offers: custom filters, email notifications, etc.
• Don't hesistate to discuss feature requests and related stuff on the bugannounce(at)openfreeway.org list.
• Once a bugfix is in Subversion, change the bug status to "resolved" with resolution "fixed".
• Resolved bugs that have been published in a Freeway release can be "closed".