You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is the New & Noteworthy page for CDT 12.4 which is part of Eclipse 2026-03 Simultaneous Release
4
+
5
+
---
6
+
7
+
# Release Notes
8
+
9
+
10
+
# API Changes, current and planned
11
+
12
+
13
+
## Breaking API changes
14
+
15
+
Please see [CHANGELOG-API](CHANGELOG-API.md) for details on the breaking API changes in this release as well as future planned API changes.
16
+
17
+
# Noteworthy Issues and Pull Requests
18
+
19
+
See [Noteworthy issues and PRs](https://github.com/eclipse-cdt/cdt/issues?q=is%3Aclosed+label%3Anoteworthy+milestone%3A12.4.0) for this release in the issue/PR tracker.
20
+
21
+
# Bugs Fixed in this Release
22
+
23
+
See GitHub milestone for CDT [](https://github.com/eclipse-cdt/cdt/milestone/22?closed=1) and CDT LSP [](https://github.com/eclipse-cdt/cdt-lsp/milestone/9?closed=1)
Copy file name to clipboardExpand all lines: RELEASING.md
+19-9Lines changed: 19 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,14 +20,23 @@ Prepare main branch for next release
20
20
- in the root pom.xml update comparator.repo, api-baseline.repo, api-baseline.repo.simrel, help-docs-eclipserun-repo, and simrel-site with the correct URLs based on what was used above in the target files/setup files
21
21
- Update versions to CDT.
22
22
- Do a global find/replace, for example:
23
-
- 12.1.0-SNAPSHOT -> 12.2.0-SNAPSHOT
24
-
- 12.1.0.qualifier -> 12.2.0.qualifier
23
+
- 12.3.0-SNAPSHOT -> 12.4.0-SNAPSHOT
24
+
- 12.3.0.qualifier -> 12.4.0.qualifier
25
25
- the above two can be done quickly as the chance of a false positive is very low, after applying them, search for remaining 12.1.0 and 12.1 strings in the codebase and update them - being careful as some of those search results should not be changed. Version ranges in dependencies can be done now, or handled with "update dependency version" as above
26
26
- Usefule commands for performing these updates:
27
27
```
28
-
find $CDT_ROOT -type f -name pom.xml -exec sed -i s/12.2.0-SNAPSHOT/12.3.0-SNAPSHOT/g {} \;
29
-
find $CDT_ROOT -type f -name feature.xml -exec sed -i s/12.2.0.qualifier/12.3.0.qualifier/g {} \;
30
-
find $CDT_ROOT -type f -name MANIFEST.MF -exec sed -i s/12.2.0.qualifier/12.3.0.qualifier/g {} \;
28
+
# Once updated, run the now updated commands:
29
+
CDT_ROOT=$PWD # update if you are not in CDT's root
30
+
find $CDT_ROOT -type f -name pom.xml -exec sed -i s/12.3.0-SNAPSHOT/12.4.0-SNAPSHOT/g {} \;
31
+
find $CDT_ROOT -type f -name feature.xml -exec sed -i s/12.3.0.qualifier/12.4.0.qualifier/g {} \;
32
+
find $CDT_ROOT -type f -name MANIFEST.MF -exec sed -i s/12.3.0.qualifier/12.4.0.qualifier/g {} \;
- run check_code_cleanliness to make sure that everything looks good `docker run --rm -it -v $(git rev-parse --show-toplevel):/work -w /work/$(git rev-parse --show-prefix) quay.io/eclipse-cdt/cdt-infra:latest releng/scripts/check_code_cleanliness.sh` - if version bumps are needed, see "bump bundle versions" below
33
42
- create a PR with the above and push it to main when it succeeds.
@@ -41,7 +50,7 @@ find $CDT_ROOT -type f -name MANIFEST.MF -exec sed -i s/12.2.0.qualifier/12.3.0.
41
50
- Add new committers (send them private email with draft nomination statement, then start election, trying to time it around a CDT call to ensure maximum engagement on the voting)
42
51
- Retire inactive committers - this happens on occasion, not with each release (past example https://github.com/eclipse-cdt/cdt/issues/1183)
43
52
- Make sure CDT build is green (https://ci.eclipse.org/cdt/job/cdt/job/main/)
44
-
- Create and push a branch of CDT (e.g. `git fetch origin && git checkout origin/main -b cdt_12_1 && git push origin cdt_12_1`)
53
+
- Create and push a branch of CDT (e.g. `git fetch origin && git checkout origin/main -b cdt_12_4 && git push origin cdt_12_4`)
45
54
- On the branch, update cdt.target to the stable/final location for dependencies
46
55
- this is not always possible, especially when we depend on I-builds from platform, in that case use provisional or RC2 I-build and update it again after they release
47
56
- The contents of the `aggrcon` files in https://github.com/eclipse-simrel/simrel.build is useful to know latest p2 URLs for dependencies
@@ -55,11 +64,12 @@ find $CDT_ROOT -type f -name MANIFEST.MF -exec sed -i s/12.2.0.qualifier/12.3.0.
55
64
- Then in the launched bash (we stay in the bash shell so that we don't have to download dependencies repeatedly):
56
65
- update dependency version `mvn org.eclipse.tycho.extras:tycho-version-bump-plugin:update-manifest`
57
66
- bump bundle versions for compare and replace `mvn verify org.eclipse.tycho:tycho-versions-plugin:bump-versions -Dtycho.bump-versions.increment=100 -DskipDoc=true -DskipTests=true -P baseline-compare-and-replace -fae -Djgit.dirtyWorkingTree-cdtDefault=warning` <-- simply running this over and over again sometimes doesn't work and a manual version bump may be needed
67
+
- one way to run it again and again is to surround with `while true; do mvn ... && break; done`
58
68
- "unbump" `org.eclipse.cdt.native.serial`'s dependency on `org.eclipse.cdt.core.native` unless the dependency really needs updating - if it really needs updating `releng/scripts/do_rebuild_natives.sh` will probably fail because the script tries to run just the one bundle, so sees an older version of `org.eclipse.cdt.core.native`.
59
69
- create a PR with all the above against the new branch - see https://github.com/eclipse-cdt/cdt/pull/1184 for a past example
60
70
- merge the PR once it is clean
61
-
- wait for the build on the branch to complete that has this change https://ci.eclipse.org/cdt/job/cdt/job/cdt_12_1/
62
-
- test that the build works with simrel (See https://github.com/eclipse-simrel/ for details of simrel) by pointing cdt.aggrcon to the just-built p2 repo (e.g. https://download.eclipse.org/tools/cdt/builds/cdt/cdt_12_1/), updating versions and running validate aggregation
71
+
- wait for the build on the branch to complete that has this change https://ci.eclipse.org/cdt/job/cdt/job/cdt_12_4/
72
+
- test that the build works with simrel (See https://github.com/eclipse-simrel/ for details of simrel) by pointing cdt.aggrcon to the just-built p2 repo (e.g. https://download.eclipse.org/tools/cdt/builds/cdt/cdt_12_4/), updating versions and running validate aggregation
63
73
- Ensure release entry on [PMI](https://projects.eclipse.org/projects/tools.cdt) "Release Date" section it says the appropriate "This release is part of Eclipse IDE ??????".
64
74
- Make sure documentation is part of simrel's [help](http://help.eclipse.org).
65
75
- Review closed issues and merged PRs to make sure labels and milestones are accurate
@@ -69,7 +79,7 @@ find $CDT_ROOT -type f -name MANIFEST.MF -exec sed -i s/12.2.0.qualifier/12.3.0.
69
79
70
80
### Items on Release day:
71
81
72
-
- Tag the release. Example: `git tag -a CDT_12_1_0 sha1ofpromotedbuild -m"CDT 12.1.0" && git push origin CDT_12_1_0`
82
+
- Tag the release. Example: `git tag -a CDT_12_4_0 sha1ofpromotedbuild -m"CDT 12.4.0" && git push origin CDT_12_4_0`
73
83
-[Promote a cdt build from jenkins](https://ci.eclipse.org/cdt/job/promote-a-build/) to releases
74
84
- Description is automatically added to the promote-a-build job and the job it promoted.
75
85
- Add description to the promoted job and ensure it is marked as keep
0 commit comments