[PATCH] D95114: HowToReleaseLLVM: Add annual release schedule template
Tom Stellard via Phabricator via llvm-commits
llvm-commits at lists.llvm.org
Tue Jul 26 12:50:32 PDT 2022
tstellar updated this revision to Diff 447805.
tstellar added a comment.
Update the schedule to be more concise. I included a definitive date
for the release branch since this seems like the most important deadline
for most people.
Repository:
rG LLVM Github Monorepo
CHANGES SINCE LAST ACTION
https://reviews.llvm.org/D95114/new/
https://reviews.llvm.org/D95114
Files:
llvm/docs/HowToReleaseLLVM.rst
Index: llvm/docs/HowToReleaseLLVM.rst
===================================================================
--- llvm/docs/HowToReleaseLLVM.rst
+++ llvm/docs/HowToReleaseLLVM.rst
@@ -28,15 +28,41 @@
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
+ 4 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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: D95114.447805.patch
Type: text/x-patch
Size: 2409 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20220726/b8c49839/attachment.bin>
More information about the llvm-commits
mailing list