On Thu, Apr 23, 2009 at 11:16 AM, Sverrir Á. Berg <[email protected]> wrote: > C) Used bugs to track releases. Since bugs are pretty good at tracking > lifetime you can in one place check status of testing and see what issues > (tracked through blocking bugs) have come up. Builds are then marked as > will-not-fix or fixed depending on if they are released or not.
While I tend to preach this process when I can, and practice it in other projects, we have two platforms that still have a significant amount of remaining work ahead of them. To dump *everything* into the bug system at this point may be a bit premature as it leads to "bug slog" where everyone eventually gets demoralized from just fixing bugs all day, every day, bugs bugs bugs! Nothing on the horizon but more and more bugs. I've seen it happen on other projects. I'm not sure when that right point is, but I think we've still got plenty of "big rocks" on each platform to keep us busy without everything being a bug. Spreadsheets aren't always 4-letter words, and they can have pretty colors!!! :-) -- Mike Pinkerton Mac Weenie [email protected] --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
