Closed jurgenvinju closed 2 years ago
Do we have to bump to 0.3.0? Are there big semantic changes? 0.2.0 was already tracking rascal 0.22.1.
I have no idea yet; I have not been through the commit messages yet. If you think 0.2.1 is best then let's go for that.
https://github.com/usethesource/rascal-language-servers/compare/v0.2.0...main
I'm ignoring #151 for the current release.
Preliminaries
Pre-releasing dependent tools in unstable
First a "pre-release" of the supporting compiler/typechecker tools must be done, so we know we are releasing a consistently compiled standard library.
Manual version checks
Manual feature tests
The list below was copied from the rascal-eclipse release; have to adapt while we go:
Required-Libraries: |lib://rascal-lsp|
rascal>1 + 1
on the REPLimport IO; println("Hello Rascal!");
RASCAL.MF
:Require-Libraries: |lib://otherProject|
, import a module and test the type-checker as well as the interpreter for correct resolution, also test a new REPL and import a library modules from the imported library.import demo::lang::pico::LanguageServer;
anddemo::lang::pico::LanguageServer::main();
and test the editor of some example pico files::edit demo::lang::pico::LanguageServer
#151Actual release
cd rascal-lsp; mvn clean compile; mvn release:prepare
)-head
from the current versiongit commit -am "[release] set release version]"
git tag vNewVersion
git push --tags
head
suffix; e.g.v0.2.0-head
git commit -am "[release] prepare for next release