Eclipse 2018-09 (4.9) Endgame Plan
September 19, 2018 - GA.
|29||Wed 20:00 EDT||API and feature freeze|
|29||Wed 20:00 EDT||Release Candidate 1 build|
|31||Fri||Submit to release train|
|5||Wed 20:00 EDT||Release Candidate 2 build|
|6||Thu||1-day test pass against RC2 and sign-off|
|7||Fri||Submit to release train|
What is the game plan?
The Eclipse 2018-09 (4.9) release endgame involves building a series of release candidates leading to the Eclipse project's contribution to the 2018-09 (4.9) release. The Eclipse project version number for this release is 4.9. As always, we welcome help from the community with testing the release candidates. By default, 2018-09 (4.9) is supposed to work exactly like the Photon (4.8) release. All new features and problems fixed in 2018-09 (4.9) are in the Eclipse bugzilla database.
General announcements during the 2018-09 (4.9) endgame are posted to the email@example.com 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 after RC1. 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
All fixes submitted must have a project 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).RC2
Release candidate containing fixes for the majority of known outstanding defects that we intend to fix for 2018-09 (4.9). At the end of RC2 build, there should not be any open defects tagged 4.9. All fixes submitted must have a project 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.2018-09 (4.9) Release
The 2018-09 (4.9) release should be complete and available for download by September 19, 2018 as part of the 2018-09 coordinated service release. If product teams intending to ship on 2018-09 (4.9) uncover further serious defects during the endgame, we may schedule additional release candidate builds to incorporate fixes.