Tracker issue labels: Difference between revisions
From MoodleDocs
Helen Foster (talk | contribs) labels thanks to Eloy (copied from http://moodle.org/mod/cvsadmin/view.php?conversationid=8834#c312666 ) |
Helen Foster (talk | contribs) patch and partner added |
||
| Line 2: | Line 2: | ||
;triaged: When something has been analyzed and adjusted / prepared for development / printable. Usually done by the [[Bug triage|triaging team]]. | ;triaged: When something has been analyzed and adjusted / prepared for development / printable. Usually done by the [[Bug triage|triaging team]]. | ||
;patch: When a suggested bug fix is provided. The development manager will look for them periodically. | |||
;partner: When an issue is of particular importance to clients of a Moodle Partner. The development manager will look for them periodically. | |||
;mdlqa: When one issue is caused by some MDLQA. Devs/testers/integrators should add it, because reset or MDLQA is needed on close of the MDL. | ;mdlqa: When one issue is caused by some MDLQA. Devs/testers/integrators should add it, because reset or MDLQA is needed on close of the MDL. | ||
; | ;mdlqa_required: When one issue is considered to need covering by one MDLQA. QA people will look for them periodically. | ||
;docs_required: When one issue is considered to need work in documentation, such as changes, creation, add to release notes. Docs people will look for them periodically. | ;docs_required: When one issue is considered to need work in documentation, such as changes, creation, add to release notes. Docs people will look for them periodically. | ||
Revision as of 09:20, 17 November 2011
Please use the following labels to identify tracker issues requiring further attention:
- triaged
- When something has been analyzed and adjusted / prepared for development / printable. Usually done by the triaging team.
- patch
- When a suggested bug fix is provided. The development manager will look for them periodically.
- partner
- When an issue is of particular importance to clients of a Moodle Partner. The development manager will look for them periodically.
- mdlqa
- When one issue is caused by some MDLQA. Devs/testers/integrators should add it, because reset or MDLQA is needed on close of the MDL.
- mdlqa_required
- When one issue is considered to need covering by one MDLQA. QA people will look for them periodically.
- docs_required
- When one issue is considered to need work in documentation, such as changes, creation, add to release notes. Docs people will look for them periodically.