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
|
Release checklist
=================
Last code touches:
* make the code ready, collect patches queued for the release
* look to mailinglist for any relevant last-minute fixes
* skim patches for typos, inconsistent subjects
Pre-checks:
* update package in OBS, (multi arch build checks)
* run all functional tests locally with
* defaults
* D=asan
* D=ubsan
* run all build tests (``tests/build-tests.sh``)
* run with fstests
* check Github actions for status (https://github.com/kdave/btrfs-progs/actions)
* branch *devel*
* branch *release-test* -- extensive pre-release build checks
* branch *coverage-test* -- code coverage, for information purposes only
Pre-release:
* write CHANGES entry (will be visible on RTD right away)
Python btrfsutil (pypi.org):
* rebuild whole project (regenerate constants.c and version.py)
* ``cd libbtrfsutil/python``
* ``python3 -m build`` -- build dist files
* ``twine check dist/*.tar.gz`` -- look for warnings
* ``twine upload dist/*.tar.gz`` -- make sure there's only the latest version,
*twine* must need access token to pypi.org
Release:
* tag release, sign
* build check of unpacked tar
* generate documentation
* make tar
* upload tar to kernel.org
* refresh git branches, push tags
Post-release:
* write and send announcement mail to the mailinglist
* update title on IRC
* github updates
* create a new release from the latest tag
* copy text from CHANGES as contents, formatting is the same
* wait for static binaries github action to finish
* run ``ci/actions/update-artifacts`` to copy the built static binaries to the
release (requires github command line tool ``gh``)
|
