Eclipse 2020-12 (4.18) Endgame Plan
Status
Released
Detailed Timeline
| November 2020 | |||||
| Two daily I-builds towards RC1 | |||||
| 25 | Wed 18:00 EST | API and feature freeze | |||
| 25 | Wed 18:00 EST | Release Candidate 1 build | |||
| 27 | Fri | Submit RC1 to release train | |||
| December 2020 | |||||
| 2 | Wed 18:00 EST | Release Candidate 2 build | |||
| 3 | Thu | 1-day test pass against RC2 and sign-off | |||
| 4 | Fri | Submit RC2 to release train | |||
| 16 | Wed | GA |
Useful Links
- Build Schedule - details on build times.
- Eclipse Release Checklist - lists various things that need to be checked before each release.
- Eclipse Project 4.18 Plan
- 2020-12 Simultaneous Release
What is the game plan?
The Eclipse 2020-12 (4.18) release endgame involves building a series of release candidates leading to the Eclipse project's contribution to the 2020-12 (4.18) release. The Eclipse project version number for this release is 4.18. As always, we welcome help from the community with testing the release candidates. All new features and problems fixed in 2020-12 (4.18) are in the Eclipse bugzilla database.
General announcements during the 2020-12 (4.18) 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 approvalNo 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 approvalAny feature work after RC1 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.
RC1All 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). A positive review from a project lead or PMC member means implicit approval and no vote is needed on the bug report. Ongoing changes to documentation, tests or examples do not require approval.
RC2Release candidate containing fixes for the majority of known outstanding defects that we intend to fix for 2020-12 (4.18). At the end of RC2 build, there should not be any open defects tagged 4.18. 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). A positive review from a project lead or PMC member means implicit approval and no vote is needed on the bug report. Ongoing changes to documentation, tests or examples do not require approval.
Test pass using RC2Concerted 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.
2020-12 (4.18) ReleaseThe 2020-12 (4.18) release should be complete and available for download by December 16, 2020 as part of the 2020-12 Simultaneous Release. If product teams intending to ship on 2020-12 (4.18) uncover further serious defects during the endgame, we may schedule additional release candidate builds to incorporate fixes.