LSP4J 0.19.0

[jonahgraham]

This is the Release plan and TODO list for LSP4J release v0.19.0.

Steps for Release

Items at the beginning of development

• [x] Create an Endgame Issue to track the release. As a starting point use documentation/releasing.md.
  • [x] Add the Endgame label and Milestone for the release
  • [x] Make sure any previous edits made to Endgame issues of previous releases are updated in documentation/releasing.md
• [x] Ensure all previous Endgame issues are done.
• [x] Create a New milestone for the release
• [x] 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.
• [x] Check README.md is up to date. In particular that the planned release and which versions of DAP and LSP are support is listed.
• [x] 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/0.18.0/0.19.0/g, s/0.17.0/0.18.0/g and review changes.) Ensure that -SNAPSHOT is restored in the gradle/versions.gradle and releng/pom.xml
• [x] Enable sh './releng/deploy-build.sh' in releng/build.Jenkinsfile
• [x] Ensure the CI build is stable - it is always better to release a "Green Dot" build

Items in the days ahead of Release day:

• [x] Create release on PMI
• [x] Schedule the release and if needed schedule a release review on the PMI. A release review is needed every 12 months, not with each release.
• [x] 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.
• [x] Check README.md is up to date. In particular that the planned release and which versions of DAP and LSP are support is listed.
• [x] Check all closed PRs and Issues to make sure their milestone is set. (Note: this was not until after 0.10.0 release so many old PRs and Issues have no milestone, therefore only consider items back to approx 5 Nov 2020). This search may be useful to identify such closed issues
• [x] Create and analyse a japicmp report and publish it as part of the build. Ensure that the API versions are incremented accurately based on the report. The reports are part of the build in japicmp-report and generated by releng/runjapicmp.sh
• [x] Update links in changelog for japicmp from the nightly to the final location

Items on Release day:

• [x] Prepare the repo for release by:
  • [x] removing -SNAPSHOT from gradle/versions.gradle
  • [x] removing -SNAPSHOT from releng/pom.xml entries in <dependencies> section.
  • [x] disabling sh './releng/deploy-build.sh' in releng/build.Jenkinsfile
  • see commit https://github.com/eclipse/lsp4j/commit/328ce8a4c89b0cd84fb62118f459b6cf79b09e90 for a past example
• [x] Push the above change
• [x] Run the CI build
• [x] Mark the build as Keep Forever and add to the description v0.19.0
• [x] Deploy the release by running the Release CI job with parameters:
  • LSP4J_PUBLISH_LOCATION -> updates/releases/0.19.0 ( <-- check version number)
  • PROJECT -> lsp4j-multi-build/job/main
  • LSP4J_BUILD_NUMBER -> the build that was just run above
  • DRY_RUN -> false
• [x] Add to the deploy job description v0.19.0
• [ ] Promote the staged repository to maven central
  • Login to Nexus
    • To obtain permission add request to OSSRH-26079
  • go to Staging Repositories, after a short delay the staged LSP4J release should appear (you may need to press Refresh)
  • click the staged LSP4J repo
  • press the Close button located in the toolbar. This runs activities, including checking various rules
  • once the rules are done (if successful), press the Release button (you may need to press Refresh to enable the Release button)
  • check https://search.maven.org/search?q=g:org.eclipse.lsp4j to make sure the latest release has arrived - this takes a while, 15 minutes for the files to be on the server and even longer for the search indexes to update
• [x] Update the meta-data on PMI downloads page
• [x] Tag the release. Example: git tag -a v0.19.0 HEAD -m"LSP4J 0.19.0" && git push origin v0.19.0
• [x] Contribute to Simrel. See Simrel contribution example
• [x] Create a release page on github
• [x] Link the Changelog to the release page
• [x] Make an announcement on lsp4j-dev based on the release page on github. Example on lsp4j-dev archives
• [x] Update documentation/releasing.md with any changes that may have been made to the release process.
• [x] Create the endgame for the next release right away, especially as version numbers and restoring -SNAPSHOT need to be done right away.

[jonahgraham]

I guess we should do a 0.19.0 release once we #682 resolved because of Bug 581039 that is fixed in #684

@cdietrich @pisv any thoughts or objections to me doing a release tomorrow assuming that we can get #682 resolved by then?

[pisv]

I would much appreciate this release. Thanks!

[cdietrich]

fine for me. then i can update Xtext on friday

[jonahgraham]

LSP4J 0.19.0 is released - onwards to 0.20.0 in #685

[cdietrich]

@jonahgraham the promotion to maven central is in the works, right?

the staging repo was closed, but was it released?

[jonahgraham]

I thought it was just the sync taking a while. Turns out I had closed but not released on ossrh.

I have now done that, so once sync scripts run on their end we should be good to go.

This is the only project that I release to maven central. Is there a way to automate that step? We don't do any testing of staged repo anyway.

[cdietrich]

@LorenzoBettini do you know if there is a way to avoid staging?

[cdietrich]

thx @jonahgraham it is available/working now

[LorenzoBettini]

@LorenzoBettini do you know if there is a way to avoid staging?

Sorry, I'm late: Yes, there's Nexus staging plugin that does the closing automatically. I'm not at the computer now, but you can find it in Xsemantics and Parsley