diff --git a/llvm/docs/HowToReleaseLLVM.rst b/llvm/docs/HowToReleaseLLVM.rst
--- a/llvm/docs/HowToReleaseLLVM.rst
+++ b/llvm/docs/HowToReleaseLLVM.rst
@@ -28,15 +28,46 @@
 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         Week #    Approx. Date
+=============== ========= ================
+\               **Even Releases**
+--------------- --------------------------
+*X.0.0-rc1*     *4*       *Jan 26 (Branch Date)*
+X.0.0-rc2       8         Feb 23
+**X.0.0-final** **10**    **Mar 9**
+X.0.1-rc1       14        Apr 6
+X.0.1-rc2       18        May 4
+**X.0.1-final**  **20**   **May 18**
+--------------- --------- ----------------
+------------------------------------------
+\               **Odd Releases**
+--------------- --------------------------
+*X.0.0-rc1*     *30*      *4th Tue in July (Branch Date)*
+X.0.0-rc2       34        Aug 24
+**X.0.0-final** **36**    **Sep 7**
+X.0.1-rc1       40        Oct 5
+X.0.1-rc2       44        Nov 2
+**X.0.1-final** **46**    **Nov 16**
+=============== ========= ================
+
+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