HOWTO-make-a-release.md:take into account the moved secadv files

This includes vulnerabilities.xml and all of secadv/*

Reviewed-by: Matt Caswell <matt@openssl.org>
(Merged from https://github.com/openssl/tools/pull/120)

diff --git a/HOWTO-make-a-release.md b/HOWTO-make-a-release.md
index 44580a1bd99c6e91c8a6d9bf3106817093a57be1..cf3e310cb7547e58677668f7e472669c6f3b8133 100644 (file)
--- a/HOWTO-make-a-release.md
+++ b/HOWTO-make-a-release.md
@@ -23,11 +23,8 @@ and additional tester.
         -   [OpenSSL before 3.0](#openssl-before-3.0)
     -   [Update the release data locally](#update-the-release-data-locally)
         [do not push]
-    -   [Update the website locally](#update-the-website-locally)
-        [security advisory only, do not push]
 -   [Publish the release](#publish-the-release)
     -   [Updating the release data](#updating-the-release-data)
-    -   [Updating the website](#updating-the-website) [security advisory only]
 -   [Post-publishing tasks](#post-publishing-tasks)
     -   [Check the website](#check-the-website)
     -   [Send the announcement mail](#send-the-announcement-mail)
@@ -59,10 +56,6 @@ You must have access to the following repositories:
 
     This is the usual main source repository
 
--   `git@github.openssl.org:openssl/web.git`
-
-    This is the website repository
-
 -   `git@github.openssl.org:otc/tools.git`
 
     This contains certain common tools
@@ -121,10 +114,6 @@ version released.
 
 You will need to checkout at least three working trees:
 
--   one for the website
-
-        git clone git@github.openssl.org:openssl/web.git website
-
 -   one for extra tools
 
         git clone git@github.openssl.org:otc/tools.git tools
@@ -256,26 +245,14 @@ copy and paste existing announcements making minor changes for the date and
 version number as necessary.  If there is an advisory then ensure you
 include a link to it.
 
-*Do* send the commits to the reviewer and await their approval.
-
-Commit your changes, but *do not push* them to the release data repo at this
-stage.  (the release data repo being `git@github.openssl.org:omc/data.git`)
-
-## Update the website locally
+Update the vulnerabilities.xml file if appropriate.
 
-**This is for security advisory updates only**
-
-*The changes in this section should be made in your clone of the openssl
-web repo*
-
-Update the news/vulnerabilities.xml file if appropriate.
-
-If there is a Security Advisory then copy it into the news/secadv directory.
+If there is a Security Advisory then copy it into the secadv directory.
 
 *Do* send the commits to the reviewer and await their approval.
 
-Commit your changes, but *do not push* them to the website repo at this stage.
-(the website repo being `git@github.openssl.org:openssl/web.git`)
+Commit your changes, but *do not push* them to the release data repo at this
+stage.  (the release data repo being `git@github.openssl.org:omc/data.git`)
 
 # Publish the release
 
@@ -328,15 +305,6 @@ website will get updated and a script to flush the Akamai CDN cache will be
 run.  You can look at things on www-origin.openssl.org; the CDN-hosted
 www.openssl.org should only be a few minutes delayed.
 
-## Updating the website
-
-**This is for security advisory updates only**
-
-Push the website changes you made earlier to the OpenSSL website repo.  When
-you do this, the website will get updated and a script to flush the Akamai
-CDN cache will be run.  You can look at things on www-origin.openssl.org;
-the CDN-hosted www.openssl.org should only be a few minutes delayed.
-
 # Post-publishing tasks
 
 ## Check the website
@@ -394,8 +362,8 @@ announce):
 ## Send out the Security Advisory
 
 *The secadv file mentioned in this section is the Security Advisory
-that you copied into the web repo, up in the section
-[Update the website locally](#update-the-website-locally)*
+that you copied into the release data repo, up in the section
+[Update the release data locally](#update-the-release-data-locally)*
  
 *This section is only applicable if this is a security release*