On 6/5/13, Andre Klapper <aklapper(a)wikimedia.org> wrote:
in December I mentioned the idea of having a "PATCH_AVAILABLE" or
"PATCH_TO_REVIEW" status in Bugzilla  and that we should re-evaluate
the idea once we have automatic notifications from Gerrit into Bugzilla
in place . This is now the case .
From the Amsterdam Hackathon I know that some developers would like to
filter on bug reports that have or don't have a patch in Gerrit, and
easier finding of bug reports with a corresponding patch && lack of
recent changes might provide another entry point for new developers
(pick up the existing patch and finish it).
Hence I propose
* to remove the manually set and error-prone Bugzilla keyword
"patch-in-gerrit": Every bug on its way to get RESOLVED FIXED
has to pass this stage anyway so a status feels more
* to make the "Gerrit Notification Bot" automatically change the
bug report status to "PATCH_AVAILABLE"/"PATCH_TO_REVIEW" in
Bugzilla when a patch for that bug report has been committed
(not: merged) to Gerrit.
PS: Making the Gerrit notification bot automatically close bug reports
in Bugzilla after merging a patch in Gerrit, or differentiating in
Bugzilla between "RESOLVED FIXED" (fix merged) and "RELEASED" (fix
deployed on the Wikimedia wikisites) are also interesting topics to
discuss at some point, but not in this thread. One step at a time.
Andre Klapper | Wikimedia Bugwrangler
Wikitech-l mailing list
Please Please Please :)
I've always wanted that to be a status, since it is a distinct stage
in a bugs life cycle (distinct from assigned imo, although others
disagree. In my opinion assigned means currently working on, and patch
in gerrit means already worked on and awaiting review by somebody