[webkit-dev] Cherry-Pick Bug Comments

Ademar Reis ademar.reis at openbossa.org
Tue May 31 06:58:54 PDT 2011

On Thu, May 26, 2011 at 7:54 PM, Eric Seidel <eric at webkit.org> wrote:
> I get a lot of these:
> Revision r86028 cherry-picked into qtwebkit-2.2 with commit 7e1bab1
> <http://gitorious.org/webkit/qtwebkit/commit/7e1bab1>
> as bug mail.  Probably because I'm CC'd on a zillion bugs (and actually read
> my bug mail).
> This is probably the pot calling the kettle black, since I wrote many of the
> bots which comment daily on bugs...
> ...but, I'm wondering if we can do better?
> Would it better serve the cherry-picker's needs if we instead had a separate
> server to track revision -> cherry-picks?  Or bug ids -> cherry-picks? (Like
> how the EWS bots store their status on queues.webkit.org and display it in
> little bubbles on bugs.webkit.org w/o commenting on the bugs.)
> I'm strongly supportive of all clients of webkit storing all of their
> bug-related data in bugs.webkit.org.  It's better than the alternative (lots
> of data buried in old Radars, or Chromium bugs, etc.)

Hi again.

Just so that this thread doesn't die. I think we have two good
proposals on the table:

1. Track cherry-pick info on an external server and add an iframe
inside bugzilla, the same way EWS bots do.
Pros: scalable, any vendor could add their own trackers (would it be
interesting to add rdar:// comments using this same mechanism?)

2. Configure/hack bugzilla to allow the addition of comments without
trigerring e-mails.
Pros: small change, appears to be easy to implement - specially on my side ;-)

Eric: how do we proceed from now?

In the meanwhile, please be patient with the cherry-pick e-mails... As
usual there will be a few of them this week (in average, something
like 20-30 cherry-picks per week).

  - Ademar

Ademar de Souza Reis Jr. <ademar.reis at openbossa.org>
Nokia Institute of Technology

More information about the webkit-dev mailing list