Bug tracker: usage of "PatchAvailable" keyword vs. "[PATCH] " prefix on bug reports' summary and patch review process

[Helder Magalhães <he...@gmail.com>]

Hi Batik developers,

In the past few months I've been slowly reviewing Batik's open issues
[1]. Between updating the bug's status and performing tests, I've been
marking bugs with attachments with the "PatchAvailable" keyword and
also adding the "[PATCH] " prefix on the bug reports' summary. I've
done like this taking previous issues which already used the "[PATCH]
" prefix, although the "PatchAvailable" keyword seemed more
appropriate [2] and retrievable also [3]. Should both be used or
should one be preferred over the other? I'd vote for only using the
"PatchAvailable" keyword, although I admit that performing a text
search for the "[PATCH] " prefix within the bug list [1] is pretty
convenient. ;-)

Regarding the patch review process, is there any? I mean, if one has
the opportunity to submit and/or review a patch, possibly testing it,
should some comment be added to the bug report stating it? Something
like "reviewed and ready for commit/approval" or just 'ping' to call
for attention? Maybe there's a more formal process I'm not aware
of...?

Regards,
  Helder

[1] https://issues.apache.org/bugzilla/buglist.cgi?query_format=specific&bug_status=__open__&product=Batik
[2] https://issues.apache.org/bugzilla/describekeywords.cgi
[3] https://issues.apache.org/bugzilla/buglist.cgi?query_format=specific&bug_status=__open__&product=Batik&keywords_type=allwords&keywords=PatchAvailable

---------------------------------------------------------------------
To unsubscribe, e-mail: batik-dev-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: batik-dev-help@xmlgraphics.apache.org