Page History

...

Code will be frozen every Monday at 1:00 AM Pacific Time. The repo will remain effectively locked for most changes until 1:00 PM Pacific Time. During that time, only fixes for "stopper" bugs or test failures found during sanity testing are permitted. For some committers that are not located in the US time zones, this may result in "no push Mondays" where changesets will need to wait until the very late in the day or the next day (Tuesday) to be pushed.

Monday 1:00 AM Pacific -- repo is locked, testing can begin as soon as a build is available (or you can build it yourself) 
Monday 1:00 PM Pacific -- repo is unlocked, changesets can be pushed normally again 

...

The idea behind ramping down during a milestone is to stabilize the code base but not stop all changes and disrupt work.  It is important for the leads to understand which changes are going into a milestone in order to manage risk.  As you might expect, we will be more restrictive as we approach the ship date.

Fixing Bugs Found as a Result of Sanity Testing

Serious bugs found during sanity testing are almost always regressions.  When a "stopper" bug is found, the default action is that the change set that caused the problem will be reverted.  Obviously, each particular case needs to be evaluated and the engineer who made the change will be consulted.  If reverting the fix is likely to make things more unstable, then reverting is not the best answer.  If it is a milestone week, then extra care will need to be taken when any changes are made (either reverting or fixing).  

Monday 10:00 AM Pacific - the deadline for fixing a bug, if no plan is in place for a fix, the change set will be reverted

Bugs found as a result of sanity testing that are not stoppers are expected to be fixed before the next sanity test pass.

Assignments

The following table describes sanity test assignments:

...