Thread:Talk:Git/Workflow/Bugzilla/reply (2)


 * Push a commit that fixes a ticket (or rather, claims to fix - since it is not reviewed yet).
 * Should mention the ticket ID in the commit-msg ("(bug 0000) Did foo and bar, made quux work again").
 * Comment on the ticket saying a proposed patch for this bug has been pushed to the review queue (mention gerrit change-id number or hash. Hash is probably better since numbering is less stable).
 * A fix is reviewed/merged into the repo
 * Mark related tickets as resolved/fixed.

Optionally:
 * Somebody using master verified that it works for him. This includes testing on a live Wikimedia project after deployment (since we deploy from master now - be it in a temporary branch, but those are always based on the latest master at that time). The user may mark it VERIFIED?

What the meaning of CLOSED isn't really relevant, since we don't use it and don't have it enabled.