svn commit: r1888227 - in /httpd/site/trunk/content: dev/release.mdtext security/vulnerabilities-httpd.page/ security/vulnerabilities-httpd.xml

[mj...@apache.org]

Author: mjc
Date: Tue Mar 30 17:38:54 2021
New Revision: 1888227

URL: http://svn.apache.org/viewvc?rev=1888227&view=rev
Log:
Cleanup the files we no longer need and sync the release note

Removed:
    httpd/site/trunk/content/security/vulnerabilities-httpd.page/
    httpd/site/trunk/content/security/vulnerabilities-httpd.xml
Modified:
    httpd/site/trunk/content/dev/release.mdtext

Modified: httpd/site/trunk/content/dev/release.mdtext
URL: http://svn.apache.org/viewvc/httpd/site/trunk/content/dev/release.mdtext?rev=1888227&r1=1888226&r2=1888227&view=diff
==============================================================================
--- httpd/site/trunk/content/dev/release.mdtext (original)
+++ httpd/site/trunk/content/dev/release.mdtext Tue Mar 30 17:38:54 2021
@@ -335,12 +335,12 @@ are published by CMS. More information c
 If a release contains a fix for any security issues then you need to ensure that the
 extra steps [here](https://www.apache.org/security/committers.html) are followed.
 
-Additionally you need to update the ( `httpd/site/trunk/content/security/vulnerabilities-httpd.xml` ) file
+Additionally you need to update add vulnerability json files to ( `httpd/site/trunk/content/security/json/` )
 with details of all the security fixes.  Once committed this will automatically generate the relevant
 security pages.  This information can also be used to help generate the annoucement emails.  Make sure
 to use CMS to publish these page updates.
 
-You may wish to stage the xml file in the private SECURITY repo prior to the release to allow
+You may wish to stage the json file in the private SECURITY repo prior to the release to allow
 issues to be spotted.
 
 # Should the announcement wait for binaries? #