Eclipse Project 3.3.1
Draft Endgame Plan
Updated frequently to reflect current status
Status

Friday Sept 28, 2007 12:00 EDT Status: Eclipse 3.3.1 now available!

Detailed Timeline
August 2007 
 15 Wed 08:00 EDT  Release Candidate 1 build    details  
 22Wed 08:00 EDT  Release Candidate 2 build    details  
 29Wed 08:00 EDT  Release Candidate 3 build    details  
31 Fri. 8:00 EDT  Release Candidate 4 Warm-up build   details  
September 2007 
5 Wed. 8:00 EDT  Release Candidate 4 build   details  
6 Thu. 08:00 EDT  Start 1-day test pass against RC4    details  
12 Wed. 8:00 EDT  Release Candidate 5 build   details  
  Release 3.3.1 available    details  
Useful Links

Build Schedule - details on build times.

What is the game plan?
The Eclipse 3.3.1 maintenance release endgame involves building a series of release candidates leading to the official 3.3.1 release. By its nature, this maintenance release contains fixes to a small number of serious problems found in the 3.3.0 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.3.1 is supposed to work exactly like 3.3.0 except for the problems we intended to fix. All problems fixed in 3.3.1 are in the Eclipse bugzilla database and flagged with Target Milestone "3.3.1" (query bugzilla for the complete list of bugs fixed in 3.3.1). So we're most interested in identifying regressions where we've changed something that we did not intend to.

General announcements during the 3.3.1 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 fixes for the majority of known outstanding defects that we intend to fix for 3.3.1.
RC2
Release candidate containing fixes for all known outstanding defects that we intend to fix for 3.3.1.
RC3
Release candidate containing fixes for all known outstanding defects that we intend to fix for 3.3.1.
RC4
Release candidate containing fixes for all known outstanding defects that we intend to fix for 3.3.1.
Test pass using RC5
Concerted 1-day testing effort using RC5 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.
RC5
Release candidate 5, if required, to fix problems detected during the test pass. There is no formal test pass for RC5 and beyond, other than a careful check for last minute regressions.
Release 3.3.1
Release 3.3.1 should be complete and available for download by the end of the September. If product teams intending to ship on 3.3.1 uncover further serious defects during the endgame, we may schedule additional release candidate builds to incorporate fixes.