Skip to main content

Eclipse Neon Update 2 (4.6.2) Endgame Plan

Status

Working towards RC3.

Detailed Timeline

October 2016
Weekly maintenance builds
 
12 Wed 04:00 EDT Checkpoint build
14 Fri Submit to release train
 
November 2016
Weekly maintenance builds
 
8 Tue Feature and API Freeze
9 Wed 04:00 EST Release Candidate 1 build
11 Fri Submit to release train
 
16 Wed 04:00 EST Release Candidate 2 build
17 Thu 1-day test pass against RC2 and sign-off
18 Fri Submit to release train
 
23 Wed 04:00 EST Release Candidate 3 build
24 Thu 1-day test pass against RC3 and sign-off
25 Fri Submit to release train
 
30 Wed 04:00 EST Release Candidate 4 build [if required]
December 2016
2 Fri Submit to release train [if required]
 
9 Fri Simultaneous release train complete with RC4
9 to 20 Quiet week/buffer
21 Fri Simultaneous release train GA Neon.2
 

Here are some holidays during the freeze period to keep in mind:

  • October 31 - Bangalore, India
  • November 1 - Bangalore, India

Useful Links

What is the game plan?

The Eclipse Neon Service Release 2 ("Neon Update 2 (4.6.2)") endgame involves building a series of release candidates leading to the Eclipse project's contribution to the Neon Update 2 (4.6.2) release. The Eclipse project version number for this release is 4.6.2. By its nature, this update release contains fixes to a small number of serious problems found in the June 2016 Neon (4.6) release, , as well as carefully selected feature and API additions. The new feature and API additions must be low-risk by nature, as well as tested and proven in master before they can be backported. We make and verify each changes 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, Neon Update 2 (4.6.2) is supposed to work exactly like the initial Neon (4.6) release except for the problems we intended to fix. All problems fixed in Neon Update 2 (4.6.2) are in the Eclipse bugzilla database and flagged with Target Milestone "4.6.2" (query bugzilla for the complete list of bugs fixed in Neon Update 2 (4.6.2)). So we're most interested in identifying regressions where we've changed something that we did not intend to.

General announcements during the Neon Update 2 (4.6.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.

API change approval

No API changes are expected during a update release. Any exception must be approved by the PMC. No changes are to be released without prior approval and associated bug report. Please 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.

Feature work approval

Any feature work must be approved by the PMC. No changes are to be released without prior approval and associated bug report. Please send the request for approval to the eclipse-pmc mailing list.

RC1 - Feature and API Freeze

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 update stream builds must have a component lead or 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).
No new features or APIs are allowed after RC1.

RC2

Release candidate containing fixes for the majority of known outstanding defects that we intend to fix for Neon Update 2 (4.6.2). At the end of RC2 build, there should not be any open defects tagged 4.6.2. All fixes submitted to the maintenance stream builds must have a component lead or 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).

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 Neon Update 2 (4.6.2). 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 eclipse-pmc@eclipse.org 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 pass

Neon Update 2 (4.6.2) Release

The Neon Update 2 (4.6.2) release should be complete and available for download by the end of December 2016 as part of the Neon coordinated service release . If product teams intending to ship on Neon Update 2 (4.6.2) uncover further serious defects during the endgame, we may schedule additional release candidate builds to incorporate fixes.

Back to the top