Honestly -- haven't been actually doing anything in the past 3 weeks. Still an AI to write up a proposal :)
:DG< On Tue, Sep 29, 2009 at 1:08 PM, Marc-Antoine Ruel <[email protected]> wrote: > +Dimitri, who is doing that and didn't put Jeremy in the loop. > > On Tue, Sep 29, 2009 at 4:06 PM, Jeremy Orlow <[email protected]> wrote: >> On Tue, Sep 29, 2009 at 12:52 PM, Jeremy Orlow <[email protected]> wrote: >>> >>> On Tue, Sep 29, 2009 at 12:05 PM, Eric Seidel <[email protected]> >>> wrote: >>>> >>>> On Tue, Sep 29, 2009 at 11:53 AM, Yaar Schnitman <[email protected]> >>>> wrote: >>>> > 1. An internal webkit chromium port try bot: Will help test webkit-only >>>> > patches. At first stage, it will test build failures (saving many of us >>>> > the >>>> > need to manually test on 3 platforms), but later will also conduct >>>> > chromium >>>> > port layout tests and api unit tests. >>>> >>>> By "internal" do you mean that only Googlers can access it? >>>> >>>> Is there a command I could wire into bugzilla-toll post-diff which >>>> would post to this try-bot as well? Could you detail such a command? >>> >>> I believe that only people with @chromium.org accounts can currently use >>> try bots. I'm not aware of any discussion about whether or how we should >>> give access to @webkit.org people. >> >> Btw, I think it's fairly clear we should give access to WebKit developers; I >> just haven't seen/heard any discussions about it. And there might be >> security concerns that make it impossible to simply allow every WebKit >> contributor to use them without some additional sign up process. >> >> >> > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
