Release Process

Welcome to the kuksa-common wiki!

Release Process

Kuksa-common use the same release process as kuksa-actions. That is no github releases are created but instead a tagging schema is used

Note: For now we prefix with v

• If backward compatible change then release a new minor tag (for example v2.4) and then move the major tag (for example v2) to the new commit.
• If no backward compatible change then release a new minor tag (for example v3.0) and new major tag (for example v3).