Call Information
Call Information and Agenda
- Welcome
- Actions from last meeting
- CDT 11.7.0 / 12.0 planning
- Should we skip 11.7 and make main branch 12.0 now for release in December?
- CMake improvements
- Any other business?
Connection Details
Join Zoom Meeting
https://eclipse.zoom.us/j/545364607
Meeting ID: 545 364 607
Passcode: 196590
Dial by your location find your local number: https://eclipse.zoom.us/u/acMY3kyoJW
Minutes
CDT 11.x and CDT 12.x Scheduling
We discussed and agreed to skip CDT 11.7 and start work on CDT 12.0 for release in December right away. To make this the most successful we will do this release schedule:
- CDT 11.6.1 (and future CDT 11.6.x) release as needed. The most recent of which will be included as part of SimRel 2024-09
- CDT 12.0.0 will use SimRel 2024-09 (Eclipse Platform 4.33) as target platform and have a release date of Nov 13, 2024
- The reason to release at this date is to allow time to develop and release against stable target platform so that ISVs can release their products based on SimRel 2024-09 + CDT 12.0.0
- CDT 12.1.0 will use SimRel 2024-12 (Eclipse Platform 4.34) as target platform and have release data on Dec 4, 2024 to align with SimRel 2024-12 release
- It is expected that the changes here compared to CDT 12.0.0 are minimal and to ensure 3rd party dependencies align with 2024-12 SimRel
To increase the likelihood of a successful CDT 12.0 release, the CDT project will release the following pre-release versions:
- CDT 12.0.0 M1 on Sep 13, 2024 shortly after the 2024-09 release
- CDT 12.0.0 M2 on Oct 11, 2024, approximately half way in between M1 and release data
- CDT 12.0.0 RCs as needed
Issues should be assigned to the CDT milestones in GitHub:
The exact version of CDT LSP that will be release is still to be determined, but it is expected that releases will align with the main CDT releases.
- Action @jonahgraham Investigate use of backport (as used by Tycho) for managing adding commits to CDT 11.6 branch
CDT 12.0 roadmap/planning
During the call we discussed high-level items that should be addressed for a successful release:
CDT LSP (clangd indexer)
The main purpose of the CDT 12.0 release is to migrate from CDT indexer to the clangd indexer which is integrated with the CDT LSP project.
- Change default for CDT LSP to be on for new projects
- Which project types, CMake nature/CPP Nature for example?
- FAQ needed for common CDT LSP issues, such as ensuring correct headers are opened, especially for cross-compilation scenarios
- Feature gap from CDT indexer, either fix or document/FAQ these differences
- Disabling the indexer when CDT LSP is in use
- Look and feel of the editor
- There was some discussion on this, but default the CDT LSP editor is visually very different than CDT editor as it inherits the LSP4E look and feel
- For the most part this was seen as a negative by the attendees at the meeting
- Help users with flow, especially in these two main areas:
- auto-installing clangd if no (or incompatible) clangd found
- switching from CDT Indexer to CDT LSP (and back) smoothly
CMake support
The other main topic for CDT 12 to be improved is CMake integration.
- Ensure clean flow for CMake users + CDT LSP
- Support for multiple executables is important
- Much of the complication of current CMake integration is driving CDT indexer from CMake, using CDT LSP means that complication is removed. Should there be a new project type?
- @ghentschke in their ISV solution did a new builder for CMake
- Also see #758 and others
Other areas
- CDT User manual is very dated
Roadmap actions
- Action Create and assign the above to the CDT 12.x milestones
Next Meeting
July 10 at 11am (Ottawa, Canada time)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
Message ID: <eclipse-cdt/cdt/repo-discussions/837@github.com>
