Closed jonahgraham closed 2 years ago
The fix for #668 desires a new release sooner rather than later. Assuming it is merged soon....
@pisv @KamasamaK @cdietrich I am tagging all of your for input as to when this release should happen. I can spin a release out during the week next week if that works for you all, say Monday (as an starting option). Just not sure if that interferes with 2022-12 M1 that is also next week. Thoughts?
The fix for #668 desires a new release sooner rather than later. Assuming it is merged soon....
I'm reasonably confident in the fix, but would appreciate a peer review before merging. Also, I'm going to test a snapshot build in my local setting tomorrow. I would much appreciate the release next week, if possible.
would prefer a post m1 release as there is a public holiday on monday here in germany and thus already need to spend some spare time for Xtext M1, alternative could pick up the new release if available tuesday morning german time
Post M1 is OK to me, too.
Thanks folks. I will figure out a schedule the LSP4J towards the end of next week, probably Thursday as next weekend is a 4 day weekend for us.
All done with 0.16.0 - onto 0.17.0 in #671
@jonahgraham thanks. do you also plan to contribute this to simrel m2?
I did the gerrit already, I was just holding back on submitting until M1 was actually released (in an hour or two) - https://git.eclipse.org/r/c/simrel/org.eclipse.simrel.build/+/196235
This is the Release plan and TODO list for LSP4J release v0.16.0.
Steps for Release
Items at the beginning of development
s/0.15.0/0.16.0/g
ands/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.16.0
LSP4J_PUBLISH_LOCATION
->updates/releases/0.16.0
( <-- check version number)PROJECT
->lsp4j-multi-build/job/main
LSP4J_BUILD_NUMBER
-> the build that was just run aboveDRY_RUN
->false
v0.16.0
git tag -a v0.16.0 HEAD -m"LSP4J 0.16.0" && git push origin v0.16.0
-SNAPSHOT
need to be done right away.