OpenLiberty / OpenLiberty/liberty-tools-eclipse
3Q release checklist - 26.0.9
Open
@mezarin is already working on this.
Since Sep 16, 2026.
3Q2026
- Dominant language
- Java
- Stars
- 16
- Forks
- 20
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 16
Description
Checklists
(From https://github.com/OpenLiberty/liberty-tools-eclipse/wiki/Fix-Release-Checklist)
Dependencies
- Update LCLS Dep?
- Update LSP4MP? - LSP4MP - (https://github.com/eclipse-lsp4mp/lsp4mp/releases/)
- Update LSP4Jakarta?
- Update JDT-LS (use latest version that supports the target platform (see [JDT-LS changelog] JDT-LS -(https://github.com/eclipse-jdtls/eclipse.jdt.ls/blob/main/CHANGELOG.md)(https://github.com/eclipse-jdtls/eclipse.jdt.ls/blob/main/CHANGELOG.md))
- Update lsp4e/lsp4j deps? This may not be necessary, but we have lsp4j defined in our target-platform and in category.xml. This is included with the Eclipse IDE and our strategy is to stay current with what is shipped with the IDE. LSP4E had been manually defined in our plugin in the past since we needed a specific version, but no longer. For now, let's keep lsp4j defined and just update it to what is shipped with Eclipse.
- Update other Category.xml / feature.xml deps?
Issue Tracking
- All items completed for this release? (Check Project Board) - (https://github.com/OpenLiberty/liberty-tools-eclipse/milestone/16)
- Epic issue (this issue)
Test Level
- target platform file (copy from last version, update URLs, Ctrl+Space to populate new versions, try to align version with target Eclipse install like with Mend scan contents)
- default level in POM
- default level GHA
- default level Jenkins
- Manual test against latest Eclipse release (N+1) to catch issues ahead of time for next release
Other releng
(See https://github.com/OpenLiberty/liberty-tools-eclipse/wiki/Release-build-process)
- Mend OSS dependency and app scans
- Update NOTICES file after dep scan
- Update URL list in AMA-DT repo for updated LTE dependencies.
- Doc updates
- Eclipse Marketplace entry
- Update CHANGELOG.md. (Try GH 'compare', e.g. this.)
- FINALLY - tag/release in Git/GitHub
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.