Closed jonahgraham closed 2 years ago
In https://github.com/eclipse/lsp4j/pull/673#issuecomment-1278057672 @cherylking has requested a release to pick up #673.
@cdietrich - any objection to making a release that simply picks up these new dependencies?
If no objection I will do it ASAP as we have a green build now and no open issues targetting 0.17.0.
would be ok. is there more in the pipeline?
Not that I know of. Anyway I have gone pretty fast at doing a release, so having more releases isn't an undue burden on me. So if it isn't on you, I will go ahead with the release soon.
Have our prs already ready so no issue
I plan to release 0.17.0 tomorrow which will (compared to 0.16.0) have just the dependency change to fix #673
0.17.0 is now complete. Forwards on to 0.18.0 tracked in #676
This is the Release plan and TODO list for LSP4J release v0.17.0.
Steps for Release
Items at the beginning of development
s/0.16.0/0.17.0/g
ands/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.17.0
LSP4J_PUBLISH_LOCATION
->updates/releases/0.17.0
( <-- check version number)PROJECT
->lsp4j-multi-build/job/main
LSP4J_BUILD_NUMBER
-> the build that was just run aboveDRY_RUN
->false
v0.17.0
git tag -a v0.17.0 HEAD -m"LSP4J 0.17.0" && git push origin v0.17.0
-SNAPSHOT
need to be done right away.