[x] Make sure any previous edits made to Endgame issues of previous releases are updated in RELEASING.md
[x] Update version numbers on master branch (after the release branch was created), this is generally the next minor version (or major version if that is what the committers on the project agree) and applies to the following types of files:
[x] feature.xml version
[x] pom.xml version
It does not apply to versions in MANIFEST.MF which follow API rules.
[ ] Ensure the CI build is stable - it is always better to release a "Green Dot" build
[ ] Fill in the Review Documentation -> New & Noteworthy URL with the CHANGELOG.md
[ ] Check CHANGELOG.md is up to date. The changelog should have a version entry, release date, API Breakages and other information consistent with current entries in the changelog.
This is the Release plan and TODO list for CDT LSP.
Steps for Release
Items at the beginning of development
feature.xml
versionpom.xml
versionItems in the days ahead of Release day:
1.0.0 (CDT LSP)
)Items on Release day:
git tag -a CDT_LSP_1_0_0 HEAD -m"CDT LSP 1.0.0" && git push origin CDT_LSP_1_0_0