[openssl-commits] [web] master update

[Rich Salz]

The branch master has been updated
       via  8241c47b948d2213e8cead94844fd23207716499 (commit)
      from  62df8cc9ba93dd099b4f5622e331f935643b6790 (commit)


- Log -----------------------------------------------------------------
commit 8241c47b948d2213e8cead94844fd23207716499
Author: Rich Salz <rsalz at akamai.com>
Date:   Tue May 29 11:18:24 2018 -0400

    Remove rationale paragraph
    
    Reviewed-by: OMC Vote

-----------------------------------------------------------------------

Summary of changes:
 policies/releasestrat.html | 16 +---------------
 1 file changed, 1 insertion(+), 15 deletions(-)

diff --git a/policies/releasestrat.html b/policies/releasestrat.html
index 9d0e3c3..0bb80f5 100644
--- a/policies/releasestrat.html
+++ b/policies/releasestrat.html
@@ -34,20 +34,6 @@
 	  performance improvements and so on. There is no need to
 	  recompile applications to benefit from these features.</p>
 
-	  <p>Binary compatibility also allows other possibilities. For
-	  example, consider an application that wishes to utilize
-	  a new cipher provided in a specific 1.0.x release, but it
-	  is also desirable to maintain the application in a 1.0.0
-	  context.  Customarily this would be resolved at compile time
-	  resulting in two binary packages targeting different OpenSSL
-	  versions. However, depending on the feature, it might be
-	  possible to check for its availability at run-time, thus cutting
-	  down on the maintenance of multiple binary packages. Admittedly
-	  it takes a certain discipline and some extra coding, but we
-	  would like to encourage such practice. This is because we
-	  want to see later releases being adopted faster, because new
-	  features can improve security.</p>
-
 	  <p>With regards to current and future releases the OpenSSL
 	  project has adopted the following policy:</p>
 
@@ -64,7 +50,7 @@
 	  and we will specify one at least every four years. Non-LTS
 	  releases will be supported for at least two years.</p>
 
-	  <p>As implied by the above paragraphs, during the final year
+	  <p>During the final year
 	  of support, we do not commit to anything other than security
 	  fixes. Before that, bug and security fixes will be applied
 	  as appropriate.</p>