The branch master has been updated
via a14edd05a9d088aea1e377e665da25b71a799e24 (commit)
from 0cce4862d4ea91d81b6ebcfdc3106d1331f2f291 (commit)
- Log -----------------------------------------------------------------
commit a14edd05a9d088aea1e377e665da25b71a799e24
Author: Matt Caswell <[email protected]>
Date: Tue Apr 21 15:29:24 2020 +0100
Add a note about closing the github advisory
If we've used a private github fork then we should close the advisory
and fork after the release is done.
Reviewed-by: Mark J. Cox <[email protected]>
(Merged from https://github.com/openssl/tools/pull/65)
-----------------------------------------------------------------------
Summary of changes:
release-tools/README.md | 3 +++
1 file changed, 3 insertions(+)
diff --git a/release-tools/README.md b/release-tools/README.md
index af2b78f..ad03508 100644
--- a/release-tools/README.md
+++ b/release-tools/README.md
@@ -223,6 +223,9 @@ Unfreeze the repository.
If this release includes security fixes with a CVE then you should inform
MITRE about them. See the instructions at the top of cvepool.txt in omc.
+Close the github advisory without pushing to github and remove the private
+github fork if there was one.
+
Check mailing lists over the next few hours for reports of any success
or failure. If necessary fix these and in the worst case make another
release.