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 <mark@awe.com>
(Merged from https://github.com/openssl/tools/pull/65)

diff --git a/release-tools/README.md b/release-tools/README.md
index af2b78fd60641b6238cc328e056ca7defd65c697..ad0350875991baca63c80ac83efc294c02584183 100644 (file)
--- 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.