From: drakenclimber Date: Thu, 4 Aug 2022 19:49:20 +0000 (+0000) Subject: deploy: a2340ab8cb04a7aa02e796a257329784913970df X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=1e416efa25f92645bd5f546f8ed89d3e8657486b;p=thirdparty%2Flibcgroup.git deploy: a2340ab8cb04a7aa02e796a257329784913970df --- diff --git a/md_SECURITY.html b/md_SECURITY.html index f9b598be..8c5403b7 100644 --- a/md_SECURITY.html +++ b/md_SECURITY.html @@ -67,17 +67,17 @@ $(function() {

https://github.com/libcgroup/libcgroup

This document describes the processes through which sensitive security relevant bugs can be responsibly disclosed to the libcgroup project and how the project maintainers should handle these reports. Just like the other libcgroup process documents, this document should be treated as a guiding document and not a hard, unyielding set of regulations; the bug reporters and project maintainers are encouraged to work together to address the issues as best they can, in a manner which works best for all parties involved.

-

+

Reporting Problems

Problems with the libcgroup library that are not suitable for immediate public disclosure should be emailed to the current libcgroup maintainers; see below. We typically request at most a 90 day time period to address the issue before it is made public, but we will make every effort to address the issue as quickly as possible and shorten the disclosure window.

-

+

Resolving Sensitive Security Issues

Upon disclosure of a bug, the maintainers should work together to investigate the problem and decide on a solution. In order to prevent an early disclosure of the problem, those working on the solution should do so privately and outside of the traditional libcgroup development practices. One possible solution to this is to leverage the GitHub "Security" functionality to create a private development fork that can be shared among the maintainers, and optionally the reporter. A placeholder GitHub issue may be created, but details should remain extremely limited until such time as the problem has been fixed and responsibly disclosed. If a CVE, or other tag, has been assigned to the problem, the GitHub issue title should include the vulnerability tag once the problem has been disclosed.

-

+

Public Disclosure

Whenever possible, responsible reporting and patching practices should be followed, including notification to the linux-distros and oss-security mailing lists.

    diff --git a/md_doc_internal_release_github.html b/md_doc_internal_release_github.html index 7dad93a0..cde830d9 100644 --- a/md_doc_internal_release_github.html +++ b/md_doc_internal_release_github.html @@ -68,68 +68,75 @@ $(function() {

    https://github.com/libcgroup/libcgroup

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

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

    +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

    -

    -2. Verify that the Github Actions are all passing

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

    +3. Verify that the Github Actions are all passing +

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

    # ./bootstrap.sh
 # make check
-

    -4. Verify that the packaging is correct

    -
    # make distcheck

    -5. Perform any distribution test builds

    +5. Verify that the packaging is correct +
    # make distcheck
+

    +6. Perform any distribution test builds

    • Oracle Linux
    • Fedora Rawhide
    • Red Hat Enterprise Linux
    • etc.
    -

    -6. If any problems were found up to this point that resulted in code changes, restart the process

    -7. If this is a new major/minor release, create new 'release-X.Y' branch

    +7. If any problems were found up to this point that resulted in code changes, restart the process +

    +8. If this is a new major/minor release, create new 'release-X.Y' branch

    # git branch "release-X.Y"
-

    -8. Update the version number in configure.ac AC_INIT(...) macro

    -

    -9. Tag the release in the local repository with a signed tag

    +

    +9. Update the version number in configure.ac AC_INIT(...) macro

    +

    +10. Tag the release in the local repository with a signed tag

    # git tag -s -m "version X.Y.Z" vX.Y.Z
-

    -10. Build final release tarball

    +

    +11. Build final release tarball

    # make clean
 # ./bootstrap.sh
 # make dist-gzip
-

    -11. Verify the release tarball in a separate directory

    +

    +12. Verify the release tarball in a separate directory

    <unpack the release tarball in a temporary directory>
 # ./configure --sysconfdir=/etc --localstatedir=/var \
 --enable-opaque-hierarchy="name=systemd" --enable-python
 # make check
-

    -12. Generate a checksum for the release tarball

    -
    # sha256sum <tarball> > libcgroup-X.Y.Z.tar.gz.SHA256SUM

    -13. GPG sign the release tarball and checksum using the maintainer's key

    +13. Generate a checksum for the release tarball +
    # sha256sum <tarball> > libcgroup-X.Y.Z.tar.gz.SHA256SUM
+

    +14. GPG sign the release tarball and checksum using the maintainer's key

    # gpg --armor --detach-sign libcgroup-X.Y.Z.tar.gz
 # gpg --clearsign libcgroup-X.Y.Z.tar.gz.SHA256SUM
-

    -14. Push the release tag to the main GitHub repository

    -
    # git push <repo> vX.Y.Z

    -15. Create a new GitHub release using the associated tag and upload the following files

    +15. Push the release tag to the main GitHub repository +
    # git push <repo> vX.Y.Z
+

    +16. Create a new GitHub release using the associated tag and upload the following files

    • libcgroup-X.Y.Z.tar.gz
    • libcgroup-X.Y.Z.tar.gz.asc
    • libcgroup-X.Y.Z.tar.gz.SHA256SUM
    • libcgroup-X.Y.Z.tar.gz.SHA256SUM.asc
    -

    -16. Update the GitHub release notes for older releases which are now unsupported

    +

    +17. Update the GitHub release notes for older releases which are now unsupported

    The following Markdown text is suggested at the top of the release note, see old GitHub releases for examples.

    ***This release is no longer supported upstream, please use a more recent release***