Release Process

How to create a kuksa-perf release

Update version in Cargo.toml

Update version number as needed in

[package]
name = "databroker-perf"
version = "0.3.1"

We use same versioning scheme as in kuksa-datrabroker

Update Cargo.lock

Do

cargo update

Build, test as needed, create a PR and get it merged

Tag and send to remote

Use same tag as in Cargo.toml. Make sure to check out the actual commit on remote, not the one you used to create the last PR. (Depending on how it was merged there could be minor differences)

user@debian6:~/kuksa-perf$ git tag 0.3.1
user@debian6:~/kuksa-perf$ git push upstream 0.3.1

Change to development version

If needed/wanted you can after release change version to a development version identifier like below, and then do cargo update. The advantage with this approach is that it will be obvious that you do not use a released version.

version = "0.6.0-dev.0"

Release cleanup

Go to the created release

• Change title to something like Eclipse Kuksa databroker-perf 0.3.1
• Write something about it, possibly generate release notes comparing with previous release
• Set as pre-release
• Then publish it

See also proposed changes in https://github.com/eclipse-kuksa/kuksa-databroker/pull/111

Notify Kuksa Project lead

So that he/she can decide if the "pre-release" tag can be removed