Eclipse

Monday January 14, 2008 16:00 EDT Status: Builds toward Eclipse 3.3.2 occur every Wednesday at 8 am EST.

January 2008
		23	Wed 08:00 EDT	Release Candidate 1 build
		24	Thur 08:00 EDT	Start 1-day test pass against RC1
		30	Wed 08:00 EDT	Release Candidate 2 build
February 2008
				Release 3.3.2 available

Build Schedule - details on build times.

The Eclipse 3.3.2 maintenance release endgame involves building a series of release candidates leading to the official 3.3.2 release. By its nature, this maintenance release contains fixes to a small number of serious problems found in the 3.2.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.3.2 is supposed to work exactly like 3.2.1 except for the problems we intended to fix. All problems fixed in 3.3.2 are in the Eclipse bugzilla database and flagged with Target Milestone "3.3.2" (query bugzilla for the complete list of bugs fixed in 3.3.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.3.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.

Release candidate containing fixes for the majority of known outstanding defects that we intend to fix for 3.3.2. At then end of RC1 build, there should not be any open defects tagged 3.3.2. All fixes submitted to 3.3.2 stream builds must have a PMC vote on the bug report.

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.

Release candidate 2, if required, to fix problems detected during the test pass.

Release 3.3.2 should be complete and available for download by the end of February as part of the Europa coordinated maintenance release . If product teams intending to ship on 3.3.2 uncover further serious defects during the endgame, we may schedule additional release candidate builds to incorporate fixes.