[webkit-dev] Cherry-Pick Bug Comments

Ojan Vafai ojan at chromium.org
Mon May 30 10:35:20 PDT 2011

On Mon, May 30, 2011 at 6:07 AM, Ademar Reis <ademar.reis at openbossa.org>wrote:

> On Sun, May 29, 2011 at 8:38 PM, Ojan Vafai <ojan at chromium.org> wrote:
> > I think we should be able to make everyone happy if we handle these the
> same
> > way we handle the EWS and style bots.
> > The data lives on another server (appengine in this case) and is brought
> > into the bugzilla page via an iframe. We could have an iframe for the Qt
> > release that is empty by default, but shows a link to the release when
> that
> > patch has been integrated into a branch.
> Hi Ojan.
> I'm not sure I understand what you mean... Could you give me an example?

Take a look at https://bugs.webkit.org/show_bug.cgi?id=61727. Under "Review
Patch <https://bugs.webkit.org/attachment.cgi?id=95342&action=review> |
Details <https://bugs.webkit.org/attachment.cgi?id=95342&action=edit>
| Formatted
Diff <https://bugs.webkit.org/attachment.cgi?id=95342&action=prettypatch> |
Diff <https://bugs.webkit.org/attachment.cgi?id=95342&action=diff>", there
is an iframe that contains the results from the various queues that patch
has been run through. We could similarly have an iframe dedicated to the qt
release process.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-dev/attachments/20110530/28b4ad0b/attachment.html>

More information about the webkit-dev mailing list