Mantis

Using Mantis - 2008-12-03 11:39 - rusty [Announcement]

This summarizes how the MediaMonkey team uses the forum and Mantis for bug tracking.

1) Forum members raise an issue in the [Needs Help] or [Beta] Forum
2) Other members/Moderators help resolve the issue, if possible. If Moderators confirm that it's a bug, they add BUG#xxxx to the title, and enter it in Mantis, along with bi-directional links between the forum report and the bug.
   If the issue is reported bug but is determined not to be one, then NOTREP is added to the report title in the forum.

Here's description of the bug workflow once a bug is added to Mantis:

[State] - Action:
[None]- Bug report entered (Moderator/Tester or Dev team). If it is a regression from a previous version, then indicate '(regression)' in the title.
[New] - Bug is prioritized and Assigned or Resolved [Duplicate, Won't fix] (Product/Dev Manager).
      - 'Immediate' bugs must be resolved, 'Urgent' bugs should be resolved, any lower priority is nice to have.
[Assigned] - Bug is Resolved [Fixed, Cannot Reproduce] or transferred for more Feedback (Developer)
[Feedback] - Bug-related questions are clarified (Moderator/Tester, Product Manager, Developer) or Resolved (Developer)
[Resolved] - Bug tested and Closed with comment 'Verified in build xxxx' OR if the test fails, bug is Reopened:Feedback (Moderator/Tester).
      - If additional documentation is required, bug is tagged with 'todoc' (Moderator/Tester).
      - Also, bug description should be updated if necessary to ensure that it is clear and accurate since it will go directly to the changelog.
      - If the issue is resolved but there are associated issues that are somewhat independent of the original bug, then a new bug can be opened.
[Closed] - What's New is updated (Product Manager)

Note: our development environment also includes automated testing / test suite than is used independently of the above for quality verification.