blob: 25b3ac31c85d1d86405866052dbd12d189700d76 (
plain)
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
|
The libseccomp Release Process
===============================================================================
https://github.com/seccomp/libseccomp
This is the process that should be followed when creating a new libseccomp
release.
#### 1. Verify that all issues assigned to the release milestone have been resolved
* https://github.com/seccomp/libseccomp/milestones
#### 2. Verify that the syntax/style meets the guidelines
# make check-syntax
#### 3. Verify that the bundled test suite runs without error
# ./autogen.sh
# ./configure --enable-python
# make check
# (cd tests; ./regression -T live)
#### 4. Verify that the packaging is correct
# make distcheck
#### 5. Verify that there are no outstanding defects from Coverity
# make coverity-tarball
<submit tarball manually>
... or ...
# git push -f coverity-scan
<leverage existing Travis CI infrastructure>
#### 6. Perform any distribution test builds
* Fedora Rawhide
* Red Hat Enterprise Linux
* etc.
#### 7. If any problems were found up to this point that resulted in code changes, restart the process
#### 8. Update the CREDITS file with any new contributors
# ./doc/credits_updater > CREDITS
... the results can be sanity checked with the following git command:
# git log --pretty=format:"%aN <%aE>" | sort -u
#### 9. Update the CHANGELOG file with significant changes since the last release
#### 10. If this is a new major/minor release, create new 'release-X.Y' branch
# stg branch -c "release-X.Y"
... or ...
# git branch "release-X.Y"
#### 11. Update the version number in configure.ac AC_INIT(...) macro
#### 12. Tag the release in the repository with a signed tag
# git tag -s -m "version X.Y.Z" vX.Y.Z
# git push --tags
#### 13. Build final release tarball
# make clean
# ./autogen.sh
# make dist-gzip
#### 14. Verify the release tarball in a separate directory
<unpack the release tarball in a temporary directory>
# ./configure --enable-python
# make check
# (cd tests; ./regression -T live)
#### 15. Generate a checksum for the release tarball
# sha256sum <tarball> > libseccomp-X.Y.Z.tar.gz.SHA256SUM
#### 16. GPG sign the release tarball and checksum using the maintainer's key
# gpg --armor --detach-sign libseccomp-X.Y.Z.tar.gz
# gpg --clearsign libseccomp-X.Y.Z.tar.gz.SHA256SUM
#### 17. Create a new GitHub release using the associated tag; added the relevant section from the CHANGELOG file, and upload the following files
* libseccomp-X.Y.Z.tar.gz
* libseccomp-X.Y.Z.tar.gz.asc
* libseccomp-X.Y.Z.tar.gz.SHA256SUM
* libseccomp-X.Y.Z.tar.gz.SHA256SUM.asc
|
