From Fedora Project Wiki
(recreated under User space) |
mNo edit summary |
||
| Line 5: | Line 5: | ||
* Review and filter bug report submissions in BugZilla, for correct component, actionable information and duplication. | |||
* Re-assign components, mark duplicates or request further information when necessary. | |||
* Advance Bug Work Flow status to NEEDINFO, ASSIGNED or CLOSED when applicable. | |||
* Assign bugs to the blocker and tracker lists according to policy. (See Note) | |||
* Preform HouseKeeping necessary during release EOL (End-of-Life) transitions. | |||
* Communicate through relevant mailing lists and the Bugzilla comment system to keep the Fedora community informed of impending or current EOL transitions, version change, etc. | |||
Note: Not sure about this one, the word policy isn't correct. | Note: Not sure about this one, the word policy isn't correct. | ||
Revision as of 15:34, 24 January 2009
Possible changes for review- wording for BugZappers Role on https://fedoraproject.org/wiki/PackageMaintainers/Policy
Only the part about blockers and trackers would be beyond a new triager, while the rest works for both new triager and package maintainer.
- Review and filter bug report submissions in BugZilla, for correct component, actionable information and duplication.
- Re-assign components, mark duplicates or request further information when necessary.
- Advance Bug Work Flow status to NEEDINFO, ASSIGNED or CLOSED when applicable.
- Assign bugs to the blocker and tracker lists according to policy. (See Note)
- Preform HouseKeeping necessary during release EOL (End-of-Life) transitions.
- Communicate through relevant mailing lists and the Bugzilla comment system to keep the Fedora community informed of impending or current EOL transitions, version change, etc.
Note: Not sure about this one, the word policy isn't correct.