The branch master has been updated
       via  5fdc4406e53ff3af0a5e5c4db55a9565fcd29015 (commit)
      from  1a99da7d86438c88211a32f48d5627ec2aa77f87 (commit)


- Log -----------------------------------------------------------------
commit 5fdc4406e53ff3af0a5e5c4db55a9565fcd29015
Author: Matt Caswell <m...@openssl.org>
Date:   Tue Jun 16 10:33:46 2020 +0100

    Update the Release schedule in the release strategy
    
    Reviewed-by: Paul Dale <paul.d...@oracle.com>
    (Merged from https://github.com/openssl/web/pull/184)

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

Summary of changes:
 policies/releasestrat.html | 17 +++--------------
 1 file changed, 3 insertions(+), 14 deletions(-)

diff --git a/policies/releasestrat.html b/policies/releasestrat.html
index 2fd9ad9..4b3f4f0 100644
--- a/policies/releasestrat.html
+++ b/policies/releasestrat.html
@@ -107,20 +107,9 @@
            <li>Bug fixes only</li>
          </ul>
 
-         <p>The following alpha and beta releases for OpenSSL 3.0 are currently
-         scheduled. Note that these dates are subject to change and alpha or 
beta
-         releases may be inserted or removed as required:</p>
-         <ul>
-           <li>alpha1, 2020-03-31: Basic functionality plus basic FIPS 
module</li>
-           <li>alpha2, 2020-04-21: Complete external provider support 
(serialization,
-           support for new algs, support for providers which only include
-           operations in a class)</li>
-           <li>alpha3, 2020-05-21: Aiming to test the API completeness before 
beta1
-           freezes it)</li>
-           <li>beta1, 2020-06-02: Code complete (API stable, feature 
freeze)</li>
-           <li>betaN: Other beta releases TBD</li>
-           <li>Final: 2020 early Q4</li>
-         </ul>
+         <p>The OpenSSL 3.0 release schedule is documented on the
+         <a 
href="https://wiki.openssl.org/index.php/OpenSSL_3.0_Release_Schedule";>OpenSSL 
3.0 Release Schedule</a>
+         wiki page. We expect the final release to be in early Q4 2020.</p>
       
          <p>
            For any major or minor release, we have defined the following

Reply via email to