Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "CDT/Archive/planning/9.0"
m (Jonah.kichwacoders.com moved page CDT/planning/9.0 to CDT/Archive/planning/9.0) |
|||
| (4 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| − | CDT 9.0 is our next major API breaking release schedule for June 2016. Time to clean up old APIs, especially the ones we've learned to hate over | + | |
| + | {{warning|Note: The contents of this page refer to planning documents of past Eclipse CDT releases. See [[CDT/planning]] for current information. }} | ||
| + | |||
| + | [[Category:CDT:Archive]] | ||
| + | |||
| + | CDT 9.0 is our next major API breaking release schedule for June 2016. Time to clean up old APIs, especially the ones we've learned to hate over the years. | ||
The main items include: | The main items include: | ||
| − | * | + | * Removal of the CDI debug interface |
| − | * [[ | + | * [[CDT/planning/9.0/build | New Build model]] to replace the confusing one we have. |
* More flexible template system so we can use things like freemarker instead of the confusing one we have. | * More flexible template system so we can use things like freemarker instead of the confusing one we have. | ||
| + | |||
| + | Details on API-breaking changes can be found [[CDT/APIBreakages | on this page]]. | ||
Latest revision as of 13:48, 22 January 2020
Note: The contents of this page refer to planning documents of past Eclipse CDT releases. See CDT/planning for current information.
CDT 9.0 is our next major API breaking release schedule for June 2016. Time to clean up old APIs, especially the ones we've learned to hate over the years.
The main items include:
- Removal of the CDI debug interface
- New Build model to replace the confusing one we have.
- More flexible template system so we can use things like freemarker instead of the confusing one we have.
Details on API-breaking changes can be found on this page.