Skip to content

Release Process

Erik Jaegervall edited this page Mar 8, 2024 · 3 revisions

At the moment the release process is quite lightweight

Decide on new version

Typically something like X.Y.Z

Create and push a tag

Use the form X.Y.Z

Trigger docker containers for that version

Run seat-service and hvac-service

Perform Testing

At the moment not that well defined what tests to perform. Minimum requirements:

  • Make sure all docker container builds successfully. Merge/push the version update and make sure build succeeds for main for all of them
  • Make sure Docker containers can be started.

docker run --net=host ghcr.io/eclipse/kuksa.val/databroker:latest

docker run --net=host ghcr.io/eclipse-kuksa/kuksa-incubation/hvac_service:latest

docker run --net=host ghcr.io/eclipse-kuksa/kuksa-incubation/seat_service:latest

Create pre-release

For now run release workflow.

It can be discussed if anyone actually needs images

Update Release notes

  • Generate automated release notes (select previous release as reference)
  • Add short summary on top
  • Set as "pre-release" and publish

Verify that things looks like this

image

Contact project manager and ask for approval to publish the release