You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by bu...@apache.org on 2021/03/30 17:39:04 UTC
svn commit: r1073170 - in /websites/staging/httpd/trunk/content: ./
dev/release.html security/vulnerabilities-httpd.page/
security/vulnerabilities-httpd.xml
Author: buildbot
Date: Tue Mar 30 17:39:04 2021
New Revision: 1073170
Log:
Staging update by buildbot for httpd
Removed:
websites/staging/httpd/trunk/content/security/vulnerabilities-httpd.page/
websites/staging/httpd/trunk/content/security/vulnerabilities-httpd.xml
Modified:
websites/staging/httpd/trunk/content/ (props changed)
websites/staging/httpd/trunk/content/dev/release.html
Propchange: websites/staging/httpd/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Mar 30 17:39:04 2021
@@ -1 +1 @@
-1888222
+1888227
Modified: websites/staging/httpd/trunk/content/dev/release.html
==============================================================================
--- websites/staging/httpd/trunk/content/dev/release.html (original)
+++ websites/staging/httpd/trunk/content/dev/release.html Tue Mar 30 17:39:04 2021
@@ -412,11 +412,11 @@ are published by CMS. More information c
<h1 id="what-extra-steps-for-releases-containing-security-fixes">What extra steps for releases containing security fixes?<a class="headerlink" href="#what-extra-steps-for-releases-containing-security-fixes" title="Permanent link">¶</a></h1>
<p>If a release contains a fix for any security issues then you need to ensure that the
extra steps <a href="https://www.apache.org/security/committers.html">here</a> are followed.</p>
-<p>Additionally you need to update the ( <code>httpd/site/trunk/content/security/vulnerabilities-httpd.xml</code> ) file
+<p>Additionally you need to update add vulnerability json files to ( <code>httpd/site/trunk/content/security/json/</code> )
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.</p>
-<p>You may wish to stage the xml file in the private SECURITY repo prior to the release to allow
+<p>You may wish to stage the json file in the private SECURITY repo prior to the release to allow
issues to be spotted.</p>
<h1 id="should-the-announcement-wait-for-binaries">Should the announcement wait for binaries?<a class="headerlink" href="#should-the-announcement-wait-for-binaries" title="Permanent link">¶</a></h1>
<p>In short, no. The only files that are required for a public release are the