From: drakenclimber Date: Fri, 20 Jan 2023 23:22:45 +0000 (+0000) Subject: deploy: d173f9bd86703780662ab5e791594a87464b9995 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=627eb8426cc83d6734a431cbcc494f5335684be2;p=thirdparty%2Flibcgroup.git deploy: d173f9bd86703780662ab5e791594a87464b9995 --- diff --git a/md_doc_internal_release_github.html b/md_doc_internal_release_github.html index 3e93ff4f..fb299f87 100644 --- a/md_doc_internal_release_github.html +++ b/md_doc_internal_release_github.html @@ -75,26 +75,27 @@ $(function() {

https://github.com/libcgroup/libcgroup

This is the process that should be followed when creating a new libcgroup release.

-1. Update the libcgroup-tests submodule

-
# ./bootstrap.sh
-# git submodule update  --remote tests
-# git add tests
-# git commit -s
-# git push
-

-2. Verify that all issues assigned to the release milestone have been resolved

+1. Verify that all issues assigned to the release milestone have been resolved +

+2. Verify that the Github Actions are all passing

-3. Verify that the Github Actions are all passing

-

-4. Verify that the bundled test suite runs without error

+3. Verify that the bundled test suite runs without error
# ./bootstrap.sh
 # make check
-

-5. Verify that the packaging is correct

+

+4. Verify that the packaging is correct

# make distcheck
+

+5. Verify that there are no outstanding defects from Coverity

+
# ./bootstrap.sh
+# export PATH=$PATH:/path/to/cov-build
+# cov-build --dir cov-init make
+# # verify the build succeeded.  Examine $? and cov-int/build-log.txt
+# tar czvf libcgroup-main@ae6b2682f10e.tar.gz cov-int
+# Upload the tar file to Coverity
 

6. Perform any distribution test builds