Sponsors
This page contains information about how to manage bugs. It is only interesting for members of the bug fixing team who have "developer" access to the bugtracker (e.g. being able to assign or resolve bugs).
Checklist (for bugtracker managers)
- Make use of the status, priority 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 devs for inclusion unless you have a patch ready.
- If you don't get to fix a bug assigned to you, just 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 that you have to check if some older bug still exists in the current version. Otherwise people should just upgrade.
- Make better use of the infrastructure Mantis offers: custom filters, email notifications, etc. Don't hesistate to discuss feature requests and related stuff on the bug fixing list.
- Once a bugfix is in CVS, change the bug status to "resolved" with resolution "fixed".
- Resolved bugs that have been published in a TYPO3 release can be closed finally.
