Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Change in Eclipse SDK release cadence

Hi David

There is no big change to what we've done for years. We never broke an existing non-deprecated API in any release (even when going to e4),  but we do announce that we will remove deprecatedAPIs after a 2 year period, and when there is no objection we remove them. This is covered by The only change is that we will now do this every quarter (but still with 2 year period). This is necessary to keep the code maintainable.


From:        David Williams <david_williams@xxxxxxx>
To:        cross-project-issues-dev@xxxxxxxxxxx
Date:        04.12.2017 20:42
Subject:        Re: [cross-project-issues-dev] Change in Eclipse SDK release cadence
Sent by:        cross-project-issues-dev-bounces@xxxxxxxxxxx

No, no specific concerns or doubts. In fact I decided it was a silly question,
since it is the simultaneous release that has a policy of "no breaking API changes, off-cycle".

So, the original announcement must have meant "update releases".


On 12/03/2017 02:08 PM, Daniel Megert wrote:

Hi David

The plan is to apply

If you have any concerns or doubts, please open a bug report and post it here.


cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top