Re: [webkit-dev] Cherry-Pick Bug Comments

On Mon, Jun 6, 2011 at 11:13 AM, Ademar Reis wrote: > On Sun, Jun 5, 2011 at 2:03 AM, Eric Carlson wrote: >> >> On Jun 3, 2011, at 2:30 PM, Adam Barth wrote: >> >> Either (1) or (2) is fine.  Please pick one and do it.  The status quo >> is very annoying. >> >>   Yes, please! > > I'll post these

Re: [webkit-dev] Cherry-Pick Bug Comments

On Sun, Jun 5, 2011 at 2:03 AM, Eric Carlson wrote: > > On Jun 3, 2011, at 2:30 PM, Adam Barth wrote: > > Either (1) or (2) is fine.  Please pick one and do it.  The status quo > is very annoying. > >   Yes, please! I'll post these comments only on [Qt] bugs until we implement a solution. Sorry

Re: [webkit-dev] Cherry-Pick Bug Comments

On Jun 3, 2011, at 2:30 PM, Adam Barth wrote: > Either (1) or (2) is fine. Please pick one and do it. The status quo > is very annoying. > Yes, please! eric > > > On Tue, May 31, 2011 at 6:58 AM, Ademar Reis > wrote: >> On Thu, May 26, 2011 at 7:54 PM, Eric Seidel wrote: >>> I get a

Re: [webkit-dev] Cherry-Pick Bug Comments

Either (1) or (2) is fine. Please pick one and do it. The status quo is very annoying. Adam On Tue, May 31, 2011 at 6:58 AM, Ademar Reis wrote: > On Thu, May 26, 2011 at 7:54 PM, Eric Seidel wrote: >> I get a lot of these: >> Revision r86028 cherry-picked into qtwebkit-2.2 with commit 7e1bab

Re: [webkit-dev] Cherry-Pick Bug Comments

On Thu, May 26, 2011 at 7:54 PM, Eric Seidel wrote: > I get a lot of these: > Revision r86028 cherry-picked into qtwebkit-2.2 with commit 7e1bab1 > > as bug mail.  Probably because I'm CC'd on a zillion bugs (and actually read > my bug mail). >

Re: [webkit-dev] Cherry-Pick Bug Comments

On Mon, May 30, 2011 at 6:07 AM, Ademar Reis wrote: > On Sun, May 29, 2011 at 8:38 PM, Ojan Vafai 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 i

Re: [webkit-dev] Cherry-Pick Bug Comments

On Fri, May 27, 2011 at 6:29 PM, James Robinson 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-pi

Re: [webkit-dev] Cherry-Pick Bug Comments

On Sun, May 29, 2011 at 8:38 PM, Ojan Vafai 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

Re: [webkit-dev] Cherry-Pick Bug Comments

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

Re: [webkit-dev] Cherry-Pick Bug Comments

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

Re: [webkit-dev] Cherry-Pick Bug Comments

> 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@lists.webkit.org http://list

Re: [webkit-dev] Cherry-Pick Bug Comments

On Fri, May 27, 2011 at 1:12 PM, Antonio Gomes wrote: > Use-case: years from now someone finds a particular bug report on > >> bugzilla. It's useful for them to know that it was fixed in >> QtWebKit-2.2. >> >> > Well, comment could go to the meta bug? Or maybe your cherry-pick reports > would be

Re: [webkit-dev] Cherry-Pick Bug Comments

Use-case: years from now someone finds a particular bug report on > bugzilla. It's useful for them to know that it was fixed in > QtWebKit-2.2. > > Well, comment could go to the meta bug? Or maybe your cherry-pick reports would be google'able, as you said below. > To know the list of bug(fix) in

Re: [webkit-dev] Cherry-Pick Bug Comments

Hi Eric. On Fri, May 27, 2011 at 1:37 AM, Eric Seidel wrote: > It seems that whole discussion resolves around the same problem of > cherry-picking causing too much bug noise. :) With the recent spike in my cherry-picking activity, it was just a matter of time until someone would complain. :-) B

Re: [webkit-dev] Cherry-Pick Bug Comments

It seems that whole discussion resolves around the same problem of cherry-picking causing too much bug noise. :) It would be very easy to store the "is this on the branch" bit off on a separate server. If someone could describe in greater detail the Qt release process, I suspect we could easily d

Re: [webkit-dev] Cherry-Pick Bug Comments

We had this exactly discussion in qtwebkit mailing list days ago: https://lists.webkit.org/pipermail/webkit-qt/2011-May/001555.html . It is worth reading through if you are interested in this topic! We would really like to reduce the noise of "management bugmails", but without a clear good solutio

Re: [webkit-dev] Cherry-Pick Bug Comments

On Thu, May 26, 2011 at 3:54 PM, Eric Seidel wrote: > I get a lot of these: > Revision r86028 cherry-picked into qtwebkit-2.2 with commit 7e1bab1 > > as bug mail.  Probably because I'm CC'd on a zillion bugs (and actually read > my bug mail). >

[webkit-dev] Cherry-Pick Bug Comments

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 w