(→工具和流程) |
|||
| Line 17: | Line 17: | ||
== 工具和流程 == | == 工具和流程 == | ||
* [[BugsAndFeatureRequests|Bugzilla 入门书]] : 更好地理解Bugzilla | * [[BugsAndFeatureRequests/zh-cn|Bugzilla 入门书]] : 更好地理解Bugzilla | ||
* [[BugZappers/StockBugzillaResponses|Stock Responses]] : Know the Bugzilla terminology | * [[BugZappers/StockBugzillaResponses|Stock Responses/zh-cn]] : Know the Bugzilla terminology | ||
* [[BugZappers/BugStatusWorkFlow|Bug Lifecycle]] : From bug-report to closed | * [[BugZappers/BugStatusWorkFlow/zh-cn|Bug Lifecycle]] : From bug-report to closed | ||
* [[BugZappers/Tools]] : Contains several tools and scripts that are of use to BugZappers, including Greasemonkey scripts to make triaging quicker and easier. | * [[BugZappers/Tools/zh-cn|相关工具]] : Contains several tools and scripts that are of use to BugZappers, including Greasemonkey scripts to make triaging quicker and easier. | ||
* [[BugZappers/Components and Triagers|Components and Triagers]] : Tracking progress and who's working on what | * [[BugZappers/Components and Triagers/zh-cn|Components and Triagers]] : Tracking progress and who's working on what | ||
* [[BugZappers/FindingBugs| | * [[BugZappers/FindingBugs/zh-cn|如何找到Bug]] : Help including finding duplicate bugs | ||
* [[BugZappers/How to Triage|How to Triage]] : Includes checklists for use when triaging bugs | * [[BugZappers/How to Triage/zh-cn|How to Triage]] : Includes checklists for use when triaging bugs | ||
* [[BugZappers/HouseKeeping|Housekeeping]] : Processes tied to the Fedora release cycle | * [[BugZappers/HouseKeeping/zh-cn|Housekeeping]] : Processes tied to the Fedora release cycle | ||
* [[How to test updates|如何测试更新]] : 按步骤创建更新环境 | * [[How to test updates|如何测试更新]] : 按步骤创建更新环境 | ||
Revision as of 08:43, 20 January 2012
什么是Bug分拣者?
我们是Bug分拣者，由社区活跃人士以及Red Hat公司的雇员组成。我们的主要任务是检查并分类已提交的Bug(这些Bug位于RedHat错误收集系统)。这个角色就像是一座连接用户和开发人员的桥梁，起到尽快解决Bug的作用。
Help Wanted
Triaging bugs helps package maintainers spend more time on actually fixing bugs, and provides needed assistance to other Fedora users. No programming knowledge is necessary, and triagers don't necessarily need to understand the bugs they are working on - just help others communicate about them. To find out more about why and how to become a BugZapper, see Joining.
我们的责任
- 分类所有有关Fedora的Bug，通常它们位于：Bugzilla错误收集系统。您可以请求缺失信息、验证相关问题组件是否对应以及关闭重复的Bug。
- Nominate "target" and "blocker" bugs (tracked here) that should be fixed before the next release, according to the release criteria.
- Perform housekeeping during release EOL ("End of Life") transitions in coordination with ReleaseEngineering.
- Identify and Document Common Bugs.
工具和流程
- Bugzilla 入门书 : 更好地理解Bugzilla
- Stock Responses/zh-cn : Know the Bugzilla terminology
- Bug Lifecycle : From bug-report to closed
- 相关工具 : Contains several tools and scripts that are of use to BugZappers, including Greasemonkey scripts to make triaging quicker and easier.
- Components and Triagers : Tracking progress and who's working on what
- 如何找到Bug : Help including finding duplicate bugs
- How to Triage : Includes checklists for use when triaging bugs
- Housekeeping : Processes tied to the Fedora release cycle
- 如何测试更新 : 按步骤创建更新环境
Communication
BugZappers meetings are held on every other Tuesday at 2100 UTC (4 PM EST/1 PM PST) in #fedora-meeting on freenode. See the UTC Howto for instructions to convert UTC to your local time. Everyone is welcome, and we invite you to come and participate. Topics of discussion for the next meeting as well as IRC transcripts of previous meetings can be found here BugZappers Meetings.
You can also find us on #fedora-bugzappers, stop by and say hello and feel free to ask any questions you have. Also, you can keep up to date with what is going on in the BugZappers by subscribing to the test mailing list. Alternatively, the test-announce list carries only important event announcements, if you do not want the traffic of the full list.