Closed jonahgraham closed 1 year ago
Because #674 is essentially a Java 17 regression we'll release 0.18.0 containing the fix in time for 2022-12. I have provisionally set it for Nov 8, which should give downstream projects time to adapt before the 2022-12 M3 build.
cc: @sebthom @cdietrich
@jonahgraham will you do the release somewhen this week?
Yes - I am hoping for a fix to https://github.com/eclipse/lsp4j/issues/680 before release as it is essentially the same issue as #674 as both of them are Java 17 issues.
Yes - I am hoping for a fix to #680 before release as it is essentially the same issue as #674 as both of them are Java 17 issues.
I decided that there is chance that #680 isn't in LSP4J, so I am going ahead with the 0.18.0 release, if more info comes to light we can have a 0.19.0 release with more reflection fixes.
All done with 0.18.0 - onto 0.19.0 in #681
This is the Release plan and TODO list for LSP4J release v0.18.0.
Steps for Release
Items at the beginning of development
s/0.17.0/0.18.0/g
,s/0.16.0/0.17.0/g
,s/0.15.0/0.16.0/g
and review changes.) Ensure that-SNAPSHOT
is restored in the gradle/versions.gradle and releng/pom.xmlsh './releng/deploy-build.sh'
in releng/build.JenkinsfileItems in the days ahead of Release day:
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 byreleng/runjapicmp.sh
Items on Release day:
-SNAPSHOT
from gradle/versions.gradle-SNAPSHOT
from releng/pom.xml entries in<dependencies>
section.sh './releng/deploy-build.sh'
in releng/build.Jenkinsfilev0.18.0
LSP4J_PUBLISH_LOCATION
->updates/releases/0.18.0
( <-- check version number)PROJECT
->lsp4j-multi-build/job/main
LSP4J_BUILD_NUMBER
-> the build that was just run aboveDRY_RUN
->false
v0.18.0
git tag -a v0.18.0 HEAD -m"LSP4J 0.18.0" && git push origin v0.18.0
-SNAPSHOT
need to be done right away.