[webkit-dev] Cherry-Pick Bug Comments

Ademar Reis ademar.reis at openbossa.org
Mon May 30 06:07:27 PDT 2011


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?

Thanks,
  - Ademar


>
> On Fri, May 27, 2011 at 2:29 PM, James Robinson <jamesr at google.com> wrote:
>>
>> I find these cherry-pick bug comments annoying and hope that you will stop
>> generating them.  There are many ports that make releases based off of
>> WebKit trunk, and all of them have some notion of release branches that
>> contain cherry-picked revisions, reverts, etc.  As a developer it's nearly
>> always irrelevant to me whether a given patch is cherry-picked into a given
>> Qt release or not, just as it would be to know if that revision was
>> cherry-picked into a given Gtk, EFL, Safari, or Chromium release branch.
>>  When I do need to know the status of a specific branch, I look in the
>> port-specific location of the branch to see what happened.  For example, to
>> see what's in a given chromium release I look in the appropriate
>> subdirectory of http://trac.webkit.org/browser/branches/chromium.  For the
>> Safari 534
>> branch, http://trac.webkit.org/browser/branches/safari-534-branch etc.
>> I would recommend that the people who work on QtWebKit figure out a way to
>> track revisions in their release branches in a way that does not involve
>> spamming non-Qt bugs on bugs.webkit.org or developers who aren't working
>> directly on Qt.
>> - James
>>
>> On Fri, May 27, 2011 at 10:27 AM, Antonio Gomes <tonikitoo at gmail.com>
>> wrote:
>>>
>>>> An important question: besides the notification e-mails, does the rest
>>>> of our release process bothers someone?
>>>>
>>> Not me. It works fine and is very transparent.
>>>
>>>
>>> --
>>> --Antonio Gomes
>>>
>>> _______________________________________________
>>> webkit-dev mailing list
>>> webkit-dev at lists.webkit.org
>>> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
>>>
>>
>>
>> _______________________________________________
>> webkit-dev mailing list
>> webkit-dev at lists.webkit.org
>> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
>>
>
>
> _______________________________________________
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
>
>



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


More information about the webkit-dev mailing list