Juno 4.2 SR1 Endgame Plan
August 28, 2012 - working towards SR1 RC2.
|July 1 - Aug 14|
|Weekly maintenance builds|
|15||Wed 08:00 EDT||Release Candidate 1 build|
|29||Wed 08:00 EDT||Release Candidate 2 build|
|30||Thu 08:00 EDT||Start 1-day test pass against RC2|
|5||Wed 08:00 EDT||Release Candidate 3 build|
|6||Thu 08:00 EDT||Start 1-day test pass against RC3|
|12||Wed 08:00 EDT||Release Candidate 4 build [if required]|
Here are some holidays during the freeze period to keep in mind:
- August 15 - Bangalore, India
- August 20 - Bangalore, India
- September 3 - Canada and United States
- Afternoon of September 10 - Zurich, Switzerland
- September 19 - Bangalore, India
What is the game plan?
The Eclipse Juno 4.2 Service Release 1 ("Juno 4.2 SR1") endgame involves building a series of release candidates leading to the Eclipse project's contribution to the Juno 4.2 SR1 release. The Eclipse project version number for this release is 4.2.1. By its nature, this maintenance release contains fixes to a small number of serious problems found in the June 2012 Juno 4.2 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, Juno 4.2 SR1 is supposed to work exactly like the initial Juno 4.2 release except for the problems we intended to fix. All problems fixed in Juno 4.2 SR1 are in the Eclipse bugzilla database and flagged with Target Milestone "4.2.1" (query bugzilla for the complete list of bugs fixed in Juno 4.2 SR1). So we're most interested in identifying regressions where we've changed something that we did not intend to.
General announcements during the Juno 4.2 SR1 endgame are posted to the firstname.lastname@example.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.RC1
Release candidate 1 is a warm-up build to ensure the release train build process is in place and all projects are making contributions. All fixes submitted to maintenance stream builds must have a component lead vote on the bug report.RC2
Release candidate containing fixes for the majority of known outstanding defects that we intend to fix for Juno 4.2 SR1. At the end of RC2 build, there should not be any open defects tagged 4.2.1. All fixes submitted to maintenance stream builds must have a component lead vote on the bug report, and the fix must be reviewed by an additional committer (any committer other than the one who made the fix).Test pass using RC2
Concerted 1-day testing effort using RC2 involving entire community including all component teams. The goal is to verify all the fixes and check for any regressions.RC3
Release candidate containing fixes for all known outstanding defects that we intend to fix for Juno 4.2 SR1. All fixes submitted to RC3 must have a PMC vote on the bug report, and the fix must be reviewed by an additional committer (any committer other than the one who made the fix). Ensure that all feature/plugin versions have been consistently incremented when needed.Test pass using RC3
Concerted 1-day testing effort using RC3 involving entire community including all component teams. The goal is to verify all the fixes, check for any regressions and sanity check our RC3 candidate.RC4
Release candidate 4, 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 email@example.com mailing list. All fixes submitted to RC4 must have a PMC vote on the bug report and be reviewed by an additional committer (any committer other than the one who made the fix).
No test pass is scheduled unless significant contributions occurred. If so, then Thursday would be elected for a one day test passAPI change approval
No API changes are expected during a maintenance release. Any exception must be approved by the PMC. No changes are to be released without prior approval and associated bug report. Send the request for approval to the eclipse-pmc mailing list. If a change is made to API to make it binary compatible with a previous release, technically this is still an API change, and thus it should be treated in the same way as any other API change requests.Juno 4.2 SR1 Release
The Juno 4.2 SR1 release should be complete and available for download by the end of September 2012 as part of the Juno coordinated service release . If product teams intending to ship on Juno 4.2 SR1 uncover further serious defects during the endgame, we may schedule additional release candidate builds to incorporate fixes.