[llvm] 7225c0b - HowToReleaseLLVM: Add annual release schedule template

[Tom Stellard via llvm-commits]

Author: Tom Stellard
Date: 2022-08-20T01:25:14-07:00
New Revision: 7225c0bd0115c947f3c081599e6268cfa027722f

URL: https://github.com/llvm/llvm-project/commit/7225c0bd0115c947f3c081599e6268cfa027722f
DIFF: https://github.com/llvm/llvm-project/commit/7225c0bd0115c947f3c081599e6268cfa027722f.diff

LOG: HowToReleaseLLVM: Add annual release schedule template

Reviewed By: ldionne, thieta

Differential Revision: https://reviews.llvm.org/D95114

Added: 
    

Modified: 
    llvm/docs/HowToReleaseLLVM.rst

Removed: 
    


################################################################################
diff  --git a/llvm/docs/HowToReleaseLLVM.rst b/llvm/docs/HowToReleaseLLVM.rst
index 6328fa5d6376..8aac3b6de05c 100644
--- a/llvm/docs/HowToReleaseLLVM.rst
+++ b/llvm/docs/HowToReleaseLLVM.rst
@@ -28,15 +28,41 @@ has been discovered that affects a large number of users.
 Unless otherwise stated, dot releases will follow the same procedure as
 major releases.
 
-The release process is roughly as follows:
-
-* Set code freeze and branch creation date for 6 months after last code freeze
-  date.  Announce release schedule to the LLVM community and update the website.
+Annual Release Schedule
+-----------------------
+
+Here is the annual release schedule for LLVM.  This is meant to be a
+guide, and release managers are not required to follow this exactly.
+Releases should be tagged on Tuesdays.
+
+=============================== ========================
+Release                         Approx. Date
+=============================== ========================
+------------------------------- ------------------------
+*release branch: even releases* *4th Tue in January*
+*release branch: odd releases*  *4th Tue in July*
+X.0.0-rc1                       3 days after branch.
+X.0.0-rc2                       2 weeks after branch.
+X.0.0-rc3                       4 weeks after branch
+**X.0.0-final**                 **6 weeks after branch**
+**X.0.1                         **8 weeks after branch**
+**X.0.2                         **10 weeks after branch**
+**X.0.3                         **12 weeks after branch**
+**X.0.4                         **14 weeks after branch**
+**X.0.5                         **16 weeks after branch**
+**X.0.6 (if necessary)          **18 weeks after branch**
+------------------------------- -------------------------
+
+Release Process Summary
+-----------------------
+
+* Announce release schedule to the LLVM community and update the website.  Do
+  this at least 3 weeks before the -rc1 release.
 
 * Create release branch and begin release process.
 
 * Send out release candidate sources for first round of testing.  Testing lasts
-  7-10 days.  During the first round of testing, any regressions found should be
+  6 weeks.  During the first round of testing, any regressions found should be
   fixed.  Patches are merged from mainline into the release branch.  Also, all
   features need to be completed during this time.  Any features not completed at
   the end of the first round of testing will be removed or disabled for the
@@ -52,14 +78,7 @@ The release process is roughly as follows:
 
 * Announce bug fix release schedule to the LLVM community and update the website.
 
-* Tag bug fix -rc1 after 4 weeks have passed.
-
-* Tag bug fix -rc2 4 weeks after -rc1.
-
-* Tag additional -rc candidates, if needed, to fix critical issues in
-  previous -rc releases.
-
-* Tag final release.
+* Do bug-fix releases every two weeks until X.0.5 or X.0.6 (if necessary).
 
 Release Process
 ===============