-
Notifications
You must be signed in to change notification settings - Fork 179
/
Copy pathhowto-release.txt
45 lines (30 loc) · 1.24 KB
/
howto-release.txt
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
How to make a release of PRoot?
===============================
This document summarizes checks that must be performed before
releasing PRoot or CARE.
Checks
------
+ Sanity checks:
* on ARM and *all* OBS distros (x86 and x86_64): `make -C test`
* on x86_64, with *and* without seccomp:
- `make -C tests` on *all* OBS distros
- `make -C tests memcheck`
- `CFLAGS=-fsanitize=address LDFLAGS=-lasan`
- `make -C tests V=1 2>&1 | grep talloc`
+ Fonctional checks: no regressions must appear with respect to
tests/validation.mk and to the configurations tested in the previous
release (`git show tags/...`).
+ Performance checks: the following command must not suffer from
unexpected performance regression::
time proot -R / perl -e 'system("/usr/bin/true") for (1..10000)'
where "/usr/bin/true" is a symlink to "/bin/true".
+ Static analysis: Coverity Scan and Clang Scan Build must not report
new issues.
Documentation Update
--------------------
0. update "doc/changelog.txt"
1. update the release number in "doc/proot/manual.txt"
2. regenerate the documentation: `make -C doc`
3. regenerate the command-line interface: `cp doc/*.h
src/cli/; $EDITOR src/cli/{proot,care}.h`
4. upload the generated RPM .spec file to OBS