Hey everyone! Given that clobbers are sometimes a necessary and required part of our build process, we as a team need to do a better job communicating when they're required. IRC and the waterfall are one step, but for those that don't build on all platforms every day, a passing status message may go un-noticed. As a result, I'm asking folks to please send out an email to this list when a clobber is required.
Why is this a big deal? The way our build is configured (at least on windows), the solution doesn't stop building if it encounters errors. As a result, you can easily spend a full hour doing a depend build (that's how long it takes on my 3yrold PC, for example) on a tree that's not very old and at the end be left with nothing but an error somewhere in the build output. Sure, you still have to pitch the build and start over, but at least you didn't waste the hour to get to this point. When you're trying to build quickly to test on other platforms, the setback is annoying and wasteful of valuable developer time. Let me know if you can think of better ways to improve this communication for everyone's benefit. Thanks! -- Mike Pinkerton Mac Weenie [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~----------~----~----~----~------~----~------~--~---
