Releasing a New Version

To release a new version of OSGiViz, the bundle and package versions of the Java code for the language server and Eclipse plugins, as well as for the VS Code extension need to be updated.

General

• check out the version that should be the new release on a new local branch named releases-YYYY-MM-x.y.z.

Java/Xtend Code

• run mvn org.eclipse.tycho:tycho-versions-plugin:2.7.3:set-version -DnewVersion="x.y.z.vyyyymmdd" in build/ and commit that change
• update the update site to reflect the release and commit the changes
• (TODO: automate this via GH Actions as well) locally build the generator, language server, and repository via Maven and test them. Remember to add these artifacts to the final release.
• Upload release update site to https://rtsys.informatik.uni-kiel.de/~kieler/updatesite/openkieler/release_osgiviz_x.y.z/
• after the sucessfull update, on the master run mvn org.eclipse.tycho:tycho-versions-plugin:2.7.3:set-version -DnewVersion="x.y.z+1.qualifier" and push that to origin.

JavaScript/TypeScript Code

• update the version of the extension to x.y.z and commit the change
• copy the language server from the Java/Xtend step to the extension/osgiviz/server/ folder and build the extension locally with yarn && yarn package
• test if the built osgiviz-x.y.z.vsix can be installed in VS Code and works as intended
• publish the VS Code extension to the marketplaces via yarn distribute May require PATs. TODO: let this be executed by GH Actions as well.
• after release, update the version of the extension on the main to x.y.z as well.

General Finalization

• afterwards, create a tag with git tag vx.y.z, and push the new commits and tag to the remote.
• draft a new release, attach all artifacts and create release notes.