1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
|
# Release process
This document describes how to release a new oomd version.
## Branching model
Every change goes directly onto master. Releases will simply tag a commit
from master.
## Semantic versioning
We choose to follow semantic versioning. Note that this doesn't matter much for
major version < 1 but will matter a lot for >= 1.0.0 releases.
## Tagging a release
1. Make sure master builds and passes all tests.
1. Update the `version` field in `meson.build`. The format is
`v<MAJOR>.<MINOR>.<PATCH>`.
1. Tag a release. We do this in the github UI by clicking "releases" (on same
line as "commits"), then "Draft a new release". The tag should be the same
as in `meson.build`. The title should be in `X.Y.Z` format. The tag
description should include some high level notes and a link to the
appropriate commit log. Please see previous releases for an example.
|
