Closed jonahgraham closed 1 year ago
@jonahgraham do we have an eta for this release?
It is not scheduled. I assume since you are asking we should do one soon? How about May 16th, a few days before 2023-06 M3 +0 date.
yes this would be nice. this would help to roll out the xtend/xbase/guava free version
I had to move it by one day, to the 17th, so we have time to do the release review. Please let me know if that causes any hardship.
no that is still fine, will try to prepare as much as possible beforehand
The review has not completed as it normally would have. I assume it is an admin issue so I will proceed with all but the final couple of steps of the release in case there is an issue.
@jonahgraham what is the issue in gitlab for the review. where is it stuck?
Release Review concluded successfully. I am now proceeding with final release steps.
0.21.0 done - onto 0.22.0 tracked in #732
This is the Release plan and TODO list for LSP4J release v0.21.0.
Steps for Release
Items at the beginning of development
s/0.19.0/0.21.0/g
,s/0.18.0/0.19.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.21.0
LSP4J_PUBLISH_LOCATION
->updates/releases/0.21.0
( <-- check version number)PROJECT
->lsp4j-multi-build/job/main
LSP4J_BUILD_NUMBER
-> the build that was just run aboveDRY_RUN
->false
v0.21.0
git tag -a v0.21.0 HEAD -m"LSP4J 0.21.0" && git push origin v0.21.0
-SNAPSHOT
need to be done right away.