Difference between revisions of "Bug Squad"
From Joomla! Documentation
m (Categorisation.) |
Dextercowley (talk | contribs) (fix links for wiki article consolidation) |
||
Line 2: | Line 2: | ||
The Joomla! Bug Squad is the second team within the development work group. Their main responsibilities are: | The Joomla! Bug Squad is the second team within the development work group. Their main responsibilities are: | ||
− | * Scan the forum | + | * Scan the [http://forum.joomla.org/viewforum.php?f=199 Joomla! Bug Reporting Forum] for reported issues and help community members with solving these issues. |
− | * Maintaining the [[Tracker]]. | + | * Maintaining the [[http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=32 Tracker]]. |
− | * | + | * Fix reported bugs and resolve reported issues according to the [[Bug Tracking Process]]. |
As described in the [[Joomla! Maintenance Procedures]] the Bug Squad will be in the lead when a development branch is in maintenance mode. Beside this, the Bug Squad is also supporting with testing and quality assurance when a new major or minor version is developed. Generally speaking the bug-squad is in the lead when a version switches from beta-stage to the stable-stage within the [[Development Cycle]] of Joomla! | As described in the [[Joomla! Maintenance Procedures]] the Bug Squad will be in the lead when a development branch is in maintenance mode. Beside this, the Bug Squad is also supporting with testing and quality assurance when a new major or minor version is developed. Generally speaking the bug-squad is in the lead when a version switches from beta-stage to the stable-stage within the [[Development Cycle]] of Joomla! | ||
Line 10: | Line 10: | ||
The Bug Squad has been created in the last week of December 2007. No specific structure within the team has been determined yet, but as this team will grow it is to be expected the following main structure as described below will evolve. Remember this is a structure that not necessarily represents an hierarchical structure, and also the positions are not limited to one person. One person can for example perfectly be team leader of the Joomla! 1.0 branch, but also be tester who has commit access to the code-base. | The Bug Squad has been created in the last week of December 2007. No specific structure within the team has been determined yet, but as this team will grow it is to be expected the following main structure as described below will evolve. Remember this is a structure that not necessarily represents an hierarchical structure, and also the positions are not limited to one person. One person can for example perfectly be team leader of the Joomla! 1.0 branch, but also be tester who has commit access to the code-base. | ||
− | |||
<noinclude>[[Category:Development Working Group]][[Category:Bug Squad]]</noinclude> | <noinclude>[[Category:Development Working Group]][[Category:Bug Squad]]</noinclude> |
Revision as of 15:15, 7 June 2009
The Joomla! Bug Squad is the second team within the development work group. Their main responsibilities are:
- Scan the Joomla! Bug Reporting Forum for reported issues and help community members with solving these issues.
- Maintaining the [Tracker].
- Fix reported bugs and resolve reported issues according to the Bug Tracking Process.
As described in the Joomla! Maintenance Procedures the Bug Squad will be in the lead when a development branch is in maintenance mode. Beside this, the Bug Squad is also supporting with testing and quality assurance when a new major or minor version is developed. Generally speaking the bug-squad is in the lead when a version switches from beta-stage to the stable-stage within the Development Cycle of Joomla!
The Bug Squad has been created in the last week of December 2007. No specific structure within the team has been determined yet, but as this team will grow it is to be expected the following main structure as described below will evolve. Remember this is a structure that not necessarily represents an hierarchical structure, and also the positions are not limited to one person. One person can for example perfectly be team leader of the Joomla! 1.0 branch, but also be tester who has commit access to the code-base.