File: how-to-release.md

package info (click to toggle)
monado 25.0.0%2Bdfsg-2
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 22,708 kB
  • sloc: cpp: 175,132; ansic: 141,570; python: 2,913; java: 753; xml: 735; sh: 403; javascript: 255; makefile: 58
file content (49 lines) | stat: -rw-r--r-- 976 bytes parent folder | download
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
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
# How to make a release {#how-to-release}

<!--
Copyright 2021, Collabora, Ltd. and the Monado contributors
SPDX-License-Identifier: BSL-1.0
-->

These instructions assumes that the version you are making is `24.0.0`.

## Generate changelog

Run proclamation in the `doc/changes`.

```sh
proclamation build 24.0.0
```

Commit changes.

```sh
git commit -m "doc: Update CHANGELOG" doc/CHANGELOG.md doc/changes
```

## Update versions

Edit the files below to update the version number embedded in them.

* `CMakeLists.txt`
* `vcpkg.json`

See previous commits for exact places.

```sh
git commit -m "monado: Update version" CMakeLists.txt vcpkg.json
```

## Tag the code

Do the tagging from git, do **not** do it from GitLab.
Also, make sure to prefix the version with `v` so that e.g. `24.0.0` becomes `v24.0.0`.
The `-s` flag signs the tag.

```sh
git tag v24.0.0 -m "v24.0.0" -a -s
```

## Do GitLab release

The GitLab UI has a friendly interface, follow the guide there.