On Thu, Feb 19, 2009 at 10:22 AM, Dan Kegel <[email protected]>wrote:
> > On Thu, Feb 19, 2009 at 9:57 AM, Ian Fette <[email protected]> wrote: > > At some point, we're going to have to support a newer version of GCC, no? > It > > seems like tackling these errors as they creep up is more manageable than > > trying to sometime later switch to supporting a more recent release of > GCC > > and then realizing that we've got 50,000 errors to work through... > > my $0.02 > > New contributors often have a newer gcc, and are surprised by the errors. > > So I think it's worth having both a trybot and a buildbot running gcc-4.3. I don't think we need a trybot for this. We already test too much stuff on the trybot, which make it slower to get results, and a bunch of people don't even wait for it. Trybot should be used only for stuff that, if red, will block a lot of people from working (i.e. broken compile, major tests broken). Even if the new GCC is broken for a couple of hours, the productivity of the team won't go down, so we should not have a trybot for that. A build slave might be a good idea though. Nicolas > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
