Closed jonahgraham closed 2 years ago
Do you have a broad Eta for this already? I'd like to depend on the notebook bits
There is no ETA for this - it will be based on when there is value releasing it. Have you tried out the snapshot builds to see if they meet your needs? If so we can release.
@KamasamaK - any thoughts on releasing now that you have done a bunch of work recently? I can do it first week of August if everything is in place.
i think we also should solve the gson thing. unfortunately there is no stable orbit with it yet.
i think we also should solve the gson thing. unfortunately there is no stable orbit with it yet.
Is there an I-build with it solved in Orbit?
yes. but i am not sure how stable the version numbers it produces are
I can resolve that - can you update to use the I-build and before release I will do an Orbit S-build and update to that? The Orbit 2022-09 M2 S-build is scheduled for 26 July.
@jonahgraham Yeah I'm already successfully using the snapshot, so I'd be happy with a release like this.
@jonahgraham i meanwhile updated to to sbuild. so we are ready to go
I plan on doing the 0.15.0 release tomorrow (4 Aug).
0.15.0 is now released: https://github.com/eclipse/lsp4j/releases/tag/v0.15.0
The maven artifacts should show up soon, once the nexus cron jobs have a chance to run.
thx @jonahgraham
This is the Release plan and TODO list for LSP4J release v0.15.0.
Steps for Release
Items at the beginning of development
s/0.14.0/0.15.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.15.0
LSP4J_PUBLISH_LOCATION
->updates/releases/0.15.0
( <-- check version number)PROJECT
->lsp4j-multi-build/job/main
LSP4J_BUILD_NUMBER
-> the build that was just run aboveDRY_RUN
->false
v0.15.0
git tag -a v0.15.0 HEAD -m"LSP4J 0.15.0" && git push origin v0.15.0
-SNAPSHOT
need to be done right away.