472 Branch Lockdown

1 view
Skip to first unread message

Jason Kersey

unread,
Aug 9, 2010, 8:47:24 PM8/9/10
to chromi...@chromium.org
If you're not working on anything you want released in Chrome 6, or on the 472 branch, you can stop reading now.

Starting today, we are going to start keeping the 472 branch under stricter control.  If you have changes you would like to merge, that are not release-block stable bugs, you are likely going to start to get turned away.  We have closed out all our release-block beta bugs, and we are on the path to stable.  What does this mean to you?  If you have changes you'd like to get on the branch at this point, prior to landing them you must speak directly with myself or another of the TPMs to get approval.  Once you have approval, you need to land them asap, so that we can keep track of where we are, and what's left to do.  This means you should be ready to land when you come to talk to us (this of course does not mean you can't talk to us before being ready to land, just that you're not guaranteed to get the OK until you're actually ready to land).  We are doing this so that we can be in control of when builds get kicked off, and not have people landing in the middle of them.  Thanks for your consideration.

Please let me know if you have any questions (or fixes to land!).

Jason
Reply all
Reply to author
Forward
0 new messages