Eclipse Project 3.1.2
Endgame Plan
Updated frequently to reflect current status
Status

Thursday January 26, 2006 16:00 EST Status: Success! Build M20060118-1600 has been promoted to the official Eclipse 3.1.2 release.

Detailed Timeline
January 4, 2005 
 9  Mon 08:00 EST   Release Candidate 1 build      details   
10 Tues 08:00 EST   Start 1-day test pass against RC1      details   
 11  Wed 08:00 EST   Release Candidate 2 build      details   
  Release 3.1.2 available      details   
January 31, 2005 
Useful Links

Build Schedule - details on build times.
What is the game plan?
The Eclipse 3.1.2 maintenance release endgame involves building a series of release candidates leading to the official 3.1.2 release. By its nature, this maintenance release contains fixes to a small number of serious problems found in the 3.1.1 release. We make and verify each fix carefully, so that we do not need to tie up the entire development team in time-consuming test passes. As always, we welcome help from the community with testing the release candidates. By default,  3.1.2 is supposed to work exactly like 3.1.1 except for the problems we intended to fix. All problems fixed in 3.1.2 are in the Eclipse bugzilla database and flagged with Target Milestone "3.1.2" (query bugzilla for the complete list of bugs fixed in 3.1.2). So we're most interested in identifying regressions where we've changed something that we did not intend to.

General announcements during the 3.1.2 endgame are posted to the platform-releng-dev@eclipse.org developer mailing list. Anyone participating in the endgame should be subscribed to this list, and should direct any general questions and comments about the process there as well.
Details
RC1
Release candidate containing all fixes for the known outstanding defects that we intend to fix for 3.1.2.
Test pass using RC1
Concerted 1-day testing effort using RC1 involving entire community including all component teams. Since this is the only test pass scheduled for this maintenance release, the goal is to verify all the fixes and check for any regressions.
RC2
Release candidate 2, if required, to fix problems detected during the test pass. There is no formal test pass for RC2 and beyond, other than a careful check for last minute regressions.
Release 3.1.2
Release 3.1.2 should be complete and available for download by the end of the January. If product teams intending to ship on 3.1.2 uncover further serious defects during the endgame, we may schedule additional release candidate builds to incorporate fixes.