Bug management/Bug report life cycle/zh

本页描述了中一项任务（包括而不限于错误报告、功能请求等）的生命周期.


 * 对于新建的任务，其的状态为Open（开放）.
 * 有人正在尝试完成一项任务时，其的状态可以修改为In Progress（进行中）.
 * 当特定的开发者计划完成或正在进行某一项任务时，请尽可能地将这名开发者设定为此任务的assignee.
 * 当某项任务有对应的-{zh-hans:补丁;zh-hant:修補程式}-上传至Gerrit代码审阅工具时，项目Patch-For-Review会自动添加至此任务. （参见）
 * 关闭一项任务：
 * 一项任务对应的代码修改已在Gerrit上合并时，任务会以Resolved（已解决）状态关闭. 这并不意味着修复将会立即在维基媒体下属网站上生效——您可能需要等待至多两周的时间.
 * 当任务中所指出的问题无法复现、未能提供缺失的信息，或是已经存在一个与请求的功能类似的解决方案时，任务会以Declined（拒绝）状态关闭. 当已达成共识，认为这一任务是一个坏主意时，任务也会以本状态关闭.  例如，当某一任务与其对应的项目的范围或原则相矛盾时，这一项目的维护者（或产品经理，如有）将拒绝此修复. 根据实际情况，可以不以“拒绝”状态关闭任务，而通过用户设置、全域配置变量、某一功能的重新实现或代码分叉结案.
 * 当任务并未实际描述一项错误表现，或是其超出了组件开发者的范围时，任务会以Invalid（无效）关闭. 例如，对第三方软件或第三方网站的设定修改的请求，或是违反了法律或合同义务的请求将被标记为“无效”.
 * 当一项任务描述的问题已在另一个任务中提出，无论后者是否已被解决，前者将被合并至后者，并以Duplicate（重复）状态关闭.
 * 当QA测试人员或任务提出者确认代码变更在Gerrit上合并，并已部署完毕时，她们可以选择添加Verified（已验证）关键词.
 * If a task was marked as Resolved and it turns out that this was incorrect, the task's status can be changed back to Open.
 * If a task is waiting for further input (e.g. from the task author or a third party like upstream) and can currently not be acted on, the Stalled status is temporarily given. The Stalled status can also be given when a task is waiting for its subtask(s) to be resolved first.

Completing tasks
Different teams complete the work on tasks differently, see. Some move it to a Done column on a project workboard after QA and product management have reviewed the change, and only change the task status to Resolved when they complete the current "sprint" or when the code is available in production. Others change the task status to Resolved the moment a code change that completes a task is merged, leaving its tags and workboard column unchanged.

这一修复将在何时可用？
The short answer for Wikimedia websites is: Somewhere between a week and three weeks after the task has been closed as Resolved. For details, see Deployments.