[jbosstools-dev] Fwd: [eclipse.org-planning-council] Fw: [cross-project-issues-dev] Change in Eclipse SDK release cadence

[Nick Boldt]

FYI, a new world order is coming to Eclipse. :)

---------- Forwarded message ----------
From: Daniel Megert <daniel_megert at ch.ibm.com>
Date: Fri, Dec 1, 2017 at 9:18 AM
Subject: [eclipse.org-planning-council] Fw: [cross-project-issues-dev]
Change in Eclipse SDK release cadence
To: Eclipse Planning Council private list <
eclipse.org-planning-council at eclipse.org>


----- Forwarded by Daniel Megert/Zurich/IBM on 01.12.2017 15:17 -----

From:        Aleksandar Kurtakov <akurtako at redhat.com>
To:        "issues, Cross" <cross-project-issues-dev at eclipse.org>
Date:        01.12.2017 12:48
Subject:        [cross-project-issues-dev] Change in Eclipse SDK release
cadence
Sent by:        cross-project-issues-dev-bounces at eclipse.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.


-- 
Eclipse PMC
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev at eclipse.org
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://urldefense.proofpoint.com/v2/url?u=https-3A__dev.
eclipse.org_mailman_listinfo_cross-2Dproject-2Dissues-2Ddev&d=DwICAg&c=jf_
iaSHvJObTbx-siA1ZOg&r=1UITCR5rxUZHSFczvfaNFK4ymEbEiccRX7VKchpqz0Y&m=
bOq2JMgwUDU4yDIEdARClTtDL6Vyy7j-4HxHDITBQgM&s=CVdGW5JDKaU_
WdWXHFeWx52ZW47jVYQK9_YxSMxGLaE&e=




_______________________________________________
eclipse.org-planning-council mailing list
eclipse.org-planning-council at eclipse.org
https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council

IMPORTANT: Membership in this list is generated by processes internal to
the Eclipse Foundation.  To be permanently removed from this list, you must
contact emo at eclipse.org to request removal.



-- 

Nick Boldt

Senior Software Engineer, RHCSA

Productization Lead :: JBoss Tools & Dev Studio

IM: @nickboldt / @nboldt / http://nick.divbyzero.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
@ @redhatnews <https://twitter.com/redhatnews>      Red Hat
<https://www.facebook.com/RedHatInc>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20171201/4d16e6bb/attachment-0001.html