Release Process

Decide on new version

Typically something like X.Y.Z

Update Dependencies

Do you need a new version of kuksa-client? Then possibly update requirements.in and then do

pip-compile -U requirements.in

Update Version in source code

• Update version in setup.py

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.

Create and push a tag

Use the form X.Y.Z

Trigger docker containers for that version

Trigger workflow mock-provider

Make sure that a container is published at https://github.com/eclipse-kuksa/kuksa-mock-provider/pkgs/container/kuksa-mock-provider%2Fmock-provider

Test with Docker

Start databroker

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

Start Mock service

user:~/kuksa-mock-provider$ docker run --net=host ghcr.io/eclipse-kuksa/kuksa-mock-provider/mock-provider:latest
INFO:mock_service:Initialization ...
INFO:mock_service:Connecting to Data Broker [127.0.0.1:55555]
INFO:kuksa_client.grpc:No Root CA present, it will not be possible to use a secure connection!
INFO:kuksa_client.grpc:Establishing insecure channel
INFO:mock_service:Databroker connected!

Create pre-release

Update Release notes

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

Contact project manager and ask for approval to publish the release