[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[cross-project-issues-dev] Change in Eclipse SDK release cadence
- From: Aleksandar Kurtakov <akurtako@xxxxxxxxxx>
- Date: Fri, 1 Dec 2017 13:47:25 +0200
- Delivered-to: firstname.lastname@example.org
After the Eclipse Photon release, a change in the Eclipse SDK release
cadence is coming: Releases will happen every 3 months from master.
This will reduce the huge waiting time that happens now for people
contributing early in the development cycle, who had to wait for up to
almost a year to see their feature or fix become available. Given the
ever increasing pace of software development this is needed to keep
the Eclipse SDK competitive, and to eliminate the burden on
maintainers of doing backporting.
Maintenance releases will no longer happen and people requiring a fix
will simply update to the next release.
Regarding the release train, each of the quarterly releases will be
contributed to the respective release train version.
The API removal policy remains the same, including giving 2 years
notice before removing deprecated API. API removals can be announced
in all four releases, and as a consequence API removals can also
happen in all releases.