I'm working on documenting the normal schedule for release milestones and how we track that in the bug tracker. I still have some issues to work out around when a particular feature is ready and qualified for Beta and Stable channel releases.
For the Dev channel, however, we have a well-established weekly rhythm. See http://sites.google.com/a/chromium.org/dev/release-schedules for the beginnings of public documentation of our schedule. Basically: 1. The release manager for the week cuts a dev channel build Monday morning (Pacific) from the LKGR at that time. 2. Our test team does a 1-day pass on that build while we create an official Google Chrome release build. 3. Any showstoppers found in testing need to be filed as Pri-0 ReleaseBlock-Dev bugs and addressed before we release (go to step 2). 4. Barring showstoppers in test, we run ChromeBot on Monday night. 5. On Tuesday morning, check the ChromeBot crash rates. Goto step 3 if they're bad :) 6. Sign the build and submit to QA for install and download testing. 7. Release the build to the Dev channel Tuesday afternoon. Things frequently get delayed by a day or two because of regressions, but this is the basic schedule. We should generally have a Dev channel release on Tuesday or Wednesday afternoon. If we also have a Beta or Stable release to push (less frequent), that will take priority in the test team's queue and will delay a Dev channel release. --Mark --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
