The job of the bug master is to keep the bug tracker up to date and clean so that it can be used more efficiently by the Cytoscape team to track bugs.

We use the [[http://www.mantisbt.org/|Mantis bug tracking software]] installed at http://cbio.mskcc.org/cytoscape/bugs/main_page.php

Maintainance involves the following tasks:
  * Remove bug duplicates
  * Transfers feature requests to the [[Future_Cytoscape_Features]] wiki page
  * Remove old bugs
  * Unassign bugs that were previously assigned to a developer and have not been dealt with in a long time
  * Roughly prioritize all bugs based on what the bug master thinks are the priorities of the group
  * Test bugs that are in 'resolved' status and closes them if appropriate (or delegates this task)
  * Assign bugs to Cytoscape software developers based on knowledge of what each person's expertise is. Ideally, people get assigned bugs that appear in their own code. Though, some code was written by former developers, so new people will have to be assigned these bugs. If it is difficult to find someone to assign a bug to, e-mail the cytostaff list to look for volunteers. During testing and bug fixing mode before a release, when developers are focusing on fixing bugs, it is best to assign bugs to people if they have time to work on bugs.

During the testing phase, prior to a new version release, core developers are expected to fix bugs (while user testing is in progress).
 * It is important to make sure the bug tracker is cleaned, using the maintenance tasks above, prior to this heavy bug tracker use period.
 * Once clean, the bug master announces that the bug tracker is ready for use and core developers should log in and start assigning themselves bugs that they are interested in.  Ideally bug fixers assign themselves bugs that they are interested in working on.  High priority bugs that are not self assigned will later be assigned to developers by the bug master.
 * Cytoscape development groups are encouraged to provide feedback on bug prioritization either to the bug master, or by assigning a new priority to an existing bug.

Using the bug tracker assumes that all developers are registered and have been assigned "developer" status in Mantis so that they have the permission to edit bugs. Note: See [[How_to_set_up_a_new_core_developer]] for instructions about how to set up your bug tracking user account for the first time.  Additionally, the bug master could be made and "administrator", which would allow them to add and change user permissions (ask Ethan or Gary if you want this status).

Possible future Mantis maintenance tasks:
 * Separate cPath from Cytoscape Mantis bug tracking
 * It is useful for the bug master to receive notification of all bugs posted. This can be done by configuring Mantis to send notices to users with a specific role, like Administrator, and then make sure the bug master is an "adminsitrator".