CDT 11.1.1

[jonahgraham]

This is the Release plan and TODO list for above mentioned bug fix release of CDT.

Steps for Release

Items before Release day:

• Discuss with the community a plan and announce it to cdt-dev.
• Create release on PMI
• Update New and Noteworthy page for the bug fix release
  • Add any release notes that are applicable
  • Update bug list search at end of the N&N to include all versions that the N&N applies to
• Update cdt.target to point to new dependency versions
  • This means having cdt.target point at what ever was in the last release. E.g. for CDT 10.6 which requires Eclipse 2022-03, the cdt.target should have the shipped dependencies of 2022-03
  • TODO: Consider making branch versions of CDT simply use https://download.eclipse.org/releases/2022-03/ + any bits that aren't in simrel. That may make this easier.
• Update API baseline to last release and resolve any API errors
  • This means cdt-baseline.target needs have basically the same contents as cdt.target + all the CDT features listed.
• Increment version of all feature.xml, pom.xml and any other place full version is used. (Easiest way is global find and replace, e.g. s/9.9.0/9.10.0/g and review changes.) (See this gerrit for a past example)
• Update comparator.repo in root pom.xml to last release and if there have been any changes since the branch, bump versions of MANIFEST.MFs
• On a branch there should be no Major or Minor version bumps
• Ensure the build is stable - it is always better to release a "Green Dot" build
• Ensure all previous Endgame issues are done.
• Add Target Milestone to GitHub milestones

Items on Release day:

• Promote a cdt build from jenkins to releases
  • CDT Standalone is not released for patches, so STANDALONE should be unchecked
• Smoke test the release by installing it into platform's SDK build.
• Smoke test the release by upgrading from the last C/C++ EPP (Add the new repo into Available Software Sites and then Check for Updates)
• Add description to the promote-a-build job and the job it promoted.
• Mark promoted job as Keep forever
• Unmark as keep all old Milestone and RC jobs
• Update composites in releng in preparation for going public on release day
• Promote the files to download - this makes the release public
• Tag the release. Example: git tag -a CDT_9_4_2 2cdc63eae52c8952c0d2543e1e31ca6e25225c4a -m\"CDT 9.4.2\" && git push origin CDT_9_4_2
• Update https://github.com/eclipse-cdt/cdt/blob/main/Downloads.md
• NOTE: Marketplace entries do not need updating for bug fixes as the Marketplace entries are already pointing at the composite release
• Check metadata on PMI (e.g. did release date change?)
• Create a new release entry using the GitHub tooling: https://github.com/eclipse-cdt/cdt/releases/new
• Make an announcement on cdt-dev by forwarding the release entry created above. Example on cdt-dev archives

[jonahgraham]

CDT 11.1.1 has now been released.