There are two bugs against 152.0 that block releasing it into the dev channel. I've created a label (dev-release-block) for release blockers; here is a query: http://code.google.com/p/chromium/issues/list?can=2&q=label:dev-release-block&sort=&colspec=ID+Pri+Area+Status+Owner+Summary+Modified&nobtn=Update .
The two bugs are 2044: [CRASH]Renderer crashes when zoomed into street level on maps.yahoo.com (assigned: ojan)<http://code.google.com/p/chromium/issues/detail?id=2044&q=label:dev-release-block&colspec=ID%20Pri%20Area%20Status%20Owner%20Summary%20Modified> 2045: "view source" is broken on the trunk (assigned: eroman)<http://code.google.com/p/chromium/issues/detail?id=2045&q=label:dev-release-block&colspec=ID%20Pri%20Area%20Status%20Owner%20Summary%20Modified> If there are other bugs that you think should block a dev release, please add the dev-release-block label. I'm mostly interested in regressions from the current Beta state. I want to get a dev channel release out ASAP, and I'm willing to release it with the numerous P1 bugs we've found in 149.29. Thanks, Mark [Note to those of you wondering what a dev channel release is: we'll be offering a way for people to sign up for more frequent updates of Google Chrome so that we can iterate features and give developers advance access to what's coming. Features and fixes will be deployed into the dev channel first before we roll them out to the rest of the world (a.k.a, the Beta channel). More details to come once we get a releasable build off the trunk. ] --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
