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 2014/01/14 17:07:52 UTC
svn commit: r894100 - in /websites/staging/httpd/trunk/content: ./
dev/guidelines.html
Author: buildbot
Date: Tue Jan 14 16:07:51 2014
New Revision: 894100
Log:
Staging update by buildbot for httpd
Modified:
websites/staging/httpd/trunk/content/ (props changed)
websites/staging/httpd/trunk/content/dev/guidelines.html
Propchange: websites/staging/httpd/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Jan 14 16:07:51 2014
@@ -1 +1 @@
-1558087
+1558088
Modified: websites/staging/httpd/trunk/content/dev/guidelines.html
==============================================================================
--- websites/staging/httpd/trunk/content/dev/guidelines.html (original)
+++ websites/staging/httpd/trunk/content/dev/guidelines.html Tue Jan 14 16:07:51 2014
@@ -406,9 +406,9 @@ vulnerability tracking information. The
decided that it is in the best interest of our users that the initial
commit of such code changes to any branch will provide the best
description available at that time as well as any available tracking
-information such as CVE number when committing fixes for vulnerabilities
-to any branch. Committing of the fix will be delayed until the project
-determines that all of the information about the issue can be shared.</p>
+information such as CVE number. Committing of the fix will be delayed
+until the project determines that all of the information about the issue
+can be shared.</p>
<p>In some cases there are very real benefits to sharing code early even if
full information about the issue cannot, including the potential for
broader review, testing, and distribution of the fix. This is outweighed