Monday September 15, 2008 15:00 EDT Status: The 3.4.1 RC3 build has been declared. No further 3.4.1 builds are planned.

August 2008
		27	Wed 20:00 EDT	Release Candidate 1 build
		28	Thurs 12:00 EDT	Start 1-day test pass against RC1
September 2008
		3	Wed 20:00 EDT	Release Candidate 2 build
		4	Thurs 12:00 EDT	Start 1-day test pass against RC2
		10	Wed 08:00 EDT	Release Candidate 3 build [if required]
		24	Wed 08:00 EDT	Release 3.4.1 available

Build Schedule - details on build times.

The Eclipse Ganymede Service Release 1 ("Ganymede SR1") endgame involves building a series of release candidates leading to the Eclipse project's contribution to the Ganymede SR1 release. The Eclipse project version number for this release is 3.4.1. By its nature, this maintenance release contains fixes to a small number of serious problems found in the June 2008 Ganymede 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,  Ganymede SR1 is supposed to work exactly like the initial Ganymede release except for the problems we intended to fix. All problems fixed in Ganymede SR1 are in the Eclipse bugzilla database and flagged with Target Milestone "3.4.1" (query bugzilla for the complete list of bugs fixed in Ganymede SR1). So we're most interested in identifying regressions where we've changed something that we did not intend to.

General announcements during the Ganymede SR1 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 Ganymede SR1. At the end of RC1 build, there should not be any open defects tagged 3.4.1. All fixes submitted to maintenance stream builds must have a component lead vote on the bug report.

Concerted 1-day testing effort using RC1 involving entire community including all component teams. The goal is to verify all the fixes and check for any regressions.

Release candidate containing fixes for all known outstanding defects that we intend to fix for Ganymede SR1. All fixes submitted to RC2 must have a PMC vote on the bug report. Ensure that all feature/plugin versions have been consistently incremented when needed.

Concerted 1-day testing effort using RC2 involving entire community including all component teams. The goal is to verify all the fixes, check for any regressions and sanity check our RC2 candidate.

Release candidate 3, if required, to fix problems detected during the test pass. We expect NO CHANGE at this point. If you find a show stopper, please notify ASAP the eclipse-pmc@eclipse.org mailing list. All fixes submitted to RC3 must have a PMC vote on the bug report.

No test pass is scheduled unless significant contributions occurred. If so, then thursday would be elected for a one day test pass

The Ganymede SR1 release should be complete and available for download by the end of September 2008 as part of the Ganymede coordinated service release . If product teams intending to ship on Ganymede SR1 uncover further serious defects during the endgame, we may schedule additional release candidate builds to incorporate fixes.