2.0 Freeze/Test/Fix
Master Schedule

Updated frequently to reflect current status

Freeze Status

The eclipse team now in the 2.0 "lockdown" process which involves a sequence of freeze/test/fix passes. We welcome everyone to help us test and fix eclipse in these final stages before we finish 2.0. To participate, you need to track to the same schedule we do, test when we do, and get your bugs logged in time for them to be considered before the next freeze. It is critical that we all test at the same time. At each freeze the "bar" is raised on what is allowed to be changed, so windows of opportunity for fixing problems are narrow. It is virtually impossible to track exactly to a plan this detailed, so we will update this schedule continuously to indicate current status, and what we are testing. Be warned - this plan *will* change - check back frequently if you are participating with us. Bug reports to bugzilla. Process comments should be flagged on eclipse-dev.

Test Scenarios - test scenarios to help drive testing.

June 28 Status: Since version 1.0, eight months of hard work by the entire Eclipse community has culminated in the release of version 2.0 of Eclipse. It is ready for download here. Without the support and enthusiasm of the entire Eclipse community we could not have achieved this. A big thank you to everyone in the newsgroups, on the mailings lists and especially everyone who reported bugs in Bugzilla.

How does it work?

Freeze - Freeze time indicated is when the build starts. Target is to have freeze candidate build available within 24 hours of freeze. Getting a good, testable build may require multiple attempts in rapid succession. Although we may have a build, it will not be declared "the" freeze until the team validates the build and declares it good for testing. We will keep respinning the build until freeze can be declared. It is critical that we have enough time to do test passes. We will slide schedule and use weekends as necessary if there are delays of more than 24 hours in getting good freezes.

Test - After a freeze is declared, the full test pass begins on the freeze build. Each full test pass lasts 3 days. Each component team must have a test plan to ensure adequate coverage of function and platforms and to ensure everyone knows what to do. Each team is expected to have at least 75% of the team testing during every test pass. The rest of the team will be triaging bugs, preparing candidate fixes for critical problems coming in, or working on documentation. Everyone is encouraged to participate in test passes and log bug reports to bugzilla! If you uncover what you believe could be a serious or stop-ship problem, or a regression from a previous build, please make this very clear in the bug report.

Fix - At each successive freeze, the rules for what changes are allowed to the codebase, and what checks are required, become more restrictive. NOTE: The rules apply to both fixes and feature work - any changes to the code. All committers for a component have the right to veto a change (with an explanation) even after it has been released into the codebase. If such a veto occurs, the change automatically comes out unless the explanation is shown to be invalid or the vetoing committer's concerns are addressed. An Architecture Team member who approves work, or a Committer who checks a change and does not veto it, takes joint responsibility for the change with the Committer who releases it, and is implicitly agreeing to personally help fix any problem caused by the change. Any Committer for any Eclipse Project component can perform the checking duties.

Detailed Schedule
Tue May 21, 8:00am EST -- Freeze 1 (F1)
 

Full Test pass:

Wed May 22, 8:00am EST - Fri May 24, 5:00pm EST
  Fix rule after F1: Component Lead must approve all work - no changes released without approval
  Notification requirements: N/A
  Check required on changes: N/A - However code check recommended at Component Lead discretion

Fri May 31, 8:00am EST -- Freeze 2 (F2)
 

Full Test pass:

Mon Jun 3, 8:00am EST - Wed Jun 5, 5:00pm EST
  Fix rule after F2: Component Lead + 1 Arch Team member must approve all work - no changes released without approval
  Notification requirements: Intent to change must be announced to component mailing list
  Check required on changes: 2nd Committer code check required, reporter verifies fix (where possible)

Wed Jun 12, 8:00am EST -- Freeze 3 (F3)
 

Verification Test pass:

Thu Jun 13, 8:00am EST - Mon Jun 17, 5:00pm EST
  Fix rule after F3: Architecture Team must approve all work
  Notification requirements: Intent to change must be announced to component mailing list
  Check required on changes: 2nd and 3rd Committer code check required, reporter verifies fix (where possible)

Monday Jun 24, 8:00am EST -- Golden Master Candidate (GM/F4) - Final code and doc
 

Verification Test pass:

Tue Jun 25, 8:00am EST - Thu Jun 27, 5:00pm EST
  Fix rule after GM: NO CHANGES UNLESS A SERIOUS REGRESSION IS FOUND
  Notification requirements: Intent to change must be announced to component mailing list
  Check required on changes: 2nd and 3rd Committer code check required, reporter verifies fix (where possible)

Fri Jun 28, 8:00am EST -- Golden Master Release (R2.0) - Final code and doc
 

Verification Test pass:

N/A
  Fix rule after R2.0: NO CHANGES. FIXES AFTER THIS POINT ARE RELEASED WITH THE NEXT SERVICE UPDATE.
  Notification requirements: N/A
  Check required on changes: N/A

Please see our privacy policy and website terms of use.