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
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
|
# Releasing guide - Snoopy Command Logger
## Changing the release process / Editing this document
This document contains the overall releasing process description, but hints
for what to do after each step are scattered around the related scripts in the
[dev-tools/](../dev-tools/) directory, to speed up the process.
Therefore, when changing the release process and documenting the changes in
this file, replicate the changes into the `Next step(s):` sections at the end of
each releasing-related script in the [dev-tools/](../dev-tools/) directory.
## (Before the release) QA
Run through the Quality Assurance-related steps in the [HACKING-QA.md](HACKING-QA.md) document
and work out any kinks that get pointed out.
## (Before the release) Assumptions
The following assumptions are, well, assumed, by the releasing scripts:
- `master` branch is used for releasing.
- All the code that is to be released is already merged into the `master` branch.
- The final release-related updates to `ChangeLog` and `README.md` files are already
present in the local files, **but not yet committed**.
- The release commit does not yet exist.
- The release tag does not yet exist.
- The release does not exist yet on GitHub.
## Steps to release Snoopy
0. If it makes sense, drop a note to Marcos Fouces and mention the RC tag to test,
and he'll upload it to the Debian Sid CI as an experimental release. This way,
the new Snoopy code can be built and tested on [a lot of different architectures](https://buildd.debian.org/status/package.php?p=snoopy&suite=sid).
https://buildd.debian.org/status/package.php?p=snoopy&suite=sid
1. Edit the `ChangeLog` file, update the upcoming release version and date:
edit ChangeLog
2. Edit the `README.md` file, update:
- The latest shown release version
- The latest release version in URLs right next to the edit above
- Add the latest release to the `News` section:
edit README.md
3. Create a commit and tag:
./dev-tools/create-release-commit-and-tag.sh
4. Build the release package:
./dev-tools/build-release-package.sh
5. Publish the release:
./dev-tools/publish-release.sh
6. Go to GitHub and close the corresponding milestone:
https://github.com/a2o/snoopy/milestones
7. Go to Snoopy's [Actions](https://github.com/a2o/snoopy/actions) tab
on GitHub and monitor the workflows related to the new release:
https://github.com/a2o/snoopy/actions?query=branch%3A$RELEASE_TAG
8. Trigger the native packaging build jobs:
gh workflow run -R a2o/snoopy publish-native-packages.yml --ref=$RELEASE_TAG
9. Monitor the native packaging build jobs:
https://github.com/a2o/snoopy/actions/workflows/publish-native-packages.yml?query=branch%3A$RELEASE_TAG
10. Trigger the native package installation verification jobs:
gh workflow run -R a2o/snoopy release-qa-os-matrix-install-from-repo.yml --ref=$RELEASE_TAG
11. Monitor the native package installation verification jobs:
https://github.com/a2o/snoopy/actions/workflows/release-qa-os-matrix-install-from-repo.yml?query=branch%3A$RELEASE_TAG
12. All done.
|
