[OpenJDK 2D-Dev] Still waiting for review

[Martin von Gagern]

Dalibor Topic wrote:
> On a side note, it'd be nice to be able to find the different patches
> that seem to have fallen through the cracks more easily then by
> testing everyone's patience by requiring repeated pings from
> submitter - any way we could leverage gmane or markmail to do that?

How would you identify a patch that has "fallen through the cracks"? You
could compare it to repository changesets or current state and try to
see if it got applied. You could look for repository committ messages
mentioning the same bug and the sender. You could try to parse messages
from developers for keywords indicating a rejection.

For none of this I can see any gain in using gmane or markmail, so you
might as well do things on openjdk hardware, e.g. using the pipermail
archives http://mail.openjdk.java.net/pipermail/2d-dev/ or by
registering some mail-parsing tool as a recipient of list mails.

In general when dealing with patches I prefer issue trackes with web
frontends to mailing lists, for the following reasons:
* users can subscribe to individual issues, not only whole lists
* issues can be assigned to maintainers for review
* public status tracking
* easy searching for open issues

If Sun has some internal tool to track issues, maybe there could be some
way to automatically compare tracker and mailing list, so you can find
which mailed patches have an corresponding issue already opend and which
don't, and easily open issues for new patches to keep track of them
internally.

The combination of mailing list with patch status tracking makes me
think of the Bundle BUGGY tool the bazaar developers are using:
http://bundlebuggy.aaronbentley.com/
http://bundlebuggy.aaronbentley.com/help

As far as I understand it, that tool tracks a mailing list, looking for
patches exported by bazaar (called bundles) on the one hand and status
changing commands from maintainers on the other hand. It also performs
patch code coloring, a bit akin to webrev. I don't know if it would be
possible to modify that tool to work with hg instead of bzr.

I have the feeling that all these ideas should probably be discussed on
some list other than 2d-dev, as other parts of openjdk are affected as
well. If you open a corresponding thread somewhere else about this,
please cc me.

Greetings,
 Martin

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 260 bytes
Desc: OpenPGP digital signature
URL: <http://mail.openjdk.java.net/pipermail/2d-dev/attachments/20081208/a3002acd/signature.asc>