Closed jurgenvinju closed 2 years ago
All checks are marked except the rascal-eclipse-libraries dependency update. As these libraries are still in flux moving to Java11 I choose to ignore this particular checkmark and call it a day.
See usethesource/rascal-language-servers#150 for an open issue with .tpl files in the rascal standard library
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
rascal>1 + 1
on the REPLimport IO; println("Hello Rascal!");
RASCAL.MF
:Required-Libraries: |lib://otherProject|
, import a module and test the type-checker as well as the interpreter for correct resolutionimport demo::lang::Pico::Plugin; registerPico();
and test the editor of the example pico files (syntax highlighting, menu options)import demo::lang::Pico::Plugin; rascal>:edit demo::lang::Pico::Plugin
Actual release
update-site-nexus-link-script/refresh-nexus-data
to the released versionDownstream implications
The following items can be executed asynchronously, but are nevertheless not to be forgotten: