-
Notifications
You must be signed in to change notification settings - Fork 145
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LSP4J 0.14.0 #628
Comments
Due to #630 we are going to release 0.14.0 right away. We are using 0.14.0 (as opposed to 0.13.1) because there are small but breaking API changes. Apologies to downstream community for the churn, hopefully LSP 3.17.0 really is "final" this time. |
Incompatible changes only told us about breaking changes that would normally require a major new version. This change will display changes that in Semantic Versioning would require a minor change too.
Incompatible changes only told us about breaking changes that would normally require a major new version. This change will display changes that in Semantic Versioning would require a minor change too.
@jonahgraham except notebook support :) |
Yes :) |
thx @jonahgraham |
0.14.0 is now done - https://github.com/eclipse/lsp4j/releases/tag/v0.14.0 - onto 0.15.0 tracked #631 |
This is the Release plan and TODO list for LSP4J release v0.14.0.
Steps for Release
Items at the beginning of development
s/0.13.0/0.14.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.14.0
LSP4J_PUBLISH_LOCATION
->updates/releases/0.14.0
( <-- check version number)PROJECT
->lsp4j-multi-build/job/main
LSP4J_BUILD_NUMBER
-> the build that was just run abovev0.14.0
git tag -a v0.14.0 HEAD -m"LSP4J 0.14.0" && git push origin v0.14.0
-SNAPSHOT
need to be done right away.The text was updated successfully, but these errors were encountered: