shylie/llvm-project
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[Docs] Incorporate the recent discussed changes to release process (#145285)

Browse Source 
* Move up the date 2 weeks
* Make RC3 required
* Add more releases to the table to align with the release every two
weeks RFC.

This has been discussed in the following RFCs:

https://discourse.llvm.org/t/rfc-llvm-releases-every-two-weeks/84245

https://discourse.llvm.org/t/rfc-updating-and-aligning-the-llvm-release-process-before-llvm-21/86493
This commit is contained in:
Tobias Hieta 2025-06-25 09:36:42 +02:00 committed by GitHub
parent 237b8de2c0
commit 31545ca5f4
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 9 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
llvm/docs/HowToReleaseLLVM.rst
View File

@ -38,8 +38,8 @@ Releases should be tagged on Tuesdays.
=============================== ========================= =============================== =========================
Release Approx. Date Release Approx. Date
=============================== ========================= =============================== =========================
*release branch: even releases* *4th Tue in January* *release branch: even releases* *2nd Tue in January*
*release branch: odd releases* *4th Tue in July* *release branch: odd releases* *2nd Tue in July*
X.1.0-rc1 3 days after branch. X.1.0-rc1 3 days after branch.
X.1.0-rc2 2 weeks after branch. X.1.0-rc2 2 weeks after branch.
X.1.0-rc3 4 weeks after branch X.1.0-rc3 4 weeks after branch
@ -49,7 +49,11 @@ X.1.0-rc3 4 weeks after branch
**X.1.3** **12 weeks after branch** **X.1.3** **12 weeks after branch**
**X.1.4** **14 weeks after branch** **X.1.4** **14 weeks after branch**
**X.1.5** **16 weeks after branch** **X.1.5** **16 weeks after branch**
**X.1.6 (if necessary)** **18 weeks after branch** **X.1.6** **18 weeks after branch**
**X.1.7** **20 weeks after branch**
**X.1.8** **22 weeks after branch**
**X.1.9** (If necessary) **24 weeks after branch**
**Next release branches** **~25 weeks after branch**
=============================== ========================= =============================== =========================
Release Process Summary Release Process Summary
@ -341,10 +345,10 @@ Below are the rules regarding patching the release branch:
was created. As with all phases, release managers and maintainers can reject was created. As with all phases, release managers and maintainers can reject
patches that are deemed too invasive. patches that are deemed too invasive.
#. *Before RC2* Patches should be limited to bug fixes or backend specific #. *Before RC2/RC3* Patches should be limited to bug fixes or backend specific
improvements that are determined to be very safe. improvements that are determined to be very safe.
#. *Before RC3/Final Major Release* Patches should be limited to critical #. *Before Final Major Release* Patches should be limited to critical
bugs or regressions. bugs or regressions.
#. *Bug fix releases* Patches should be limited to bug fixes or very safe #. *Bug fix releases* Patches should be limited to bug fixes or very safe