Page History

...

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 

During the week before a Milestone1 or 2 weeks before the rampdown for a release, and during the week before other published milestones, we need to be extra careful about destabilizing the release. Changes can go in, but they require the approval of one of the Project Lead, Technical Lead(s) or Release Manager(s) (Kevin, Dave) along with a pre-commit review. Approval takes the form of '+1' in JIRA.Changes that do not affect the "bits that we ship" do not require approval.  For example, changes to example code that is not part of the deliverable or JavaDoc changes do not require approval.  Changes to things like config files, jfxrt.jar and the build process require approval.  The idea is to use common sense and ask if in doubt.During this time you will need additional approval prior to pushing the changeset.

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

Please see the 8u60 release page for more information about pushing changes into 8u-dev and the 9 release page for more information about pushing changes into 9-dev.

Fixing Bugs Found as a Result of Sanity Testing

...