Update release doc with instructions on rebuilding public with stage toolchain

1 files changed, 28 insertions, 0 deletions

diff --git a/doc/release.cli b/doc/release.cli
index f02db11..78d505f 100644
--- a/doc/release.cli
+++ b/doc/release.cli
@@ -49,6 +49,34 @@ distribution from \c{etc/stage} and add the pre-distributed packages
 
 \li|Current \c{stage} build is clean.||
 
+\h#stage-public|Build public with stage toolchain|
+
+  Before starting the release process we rebuild all the packages in the
+  public repository with the stage toolchain in order to detect any
+  regressions.
+
+  \ol|
+
+  \li|Review \c{brep} commit log for any potential issues and upgrade \c{brep}
+      on public to latest staged version. See the detailed instructions in
+      \c{private}.|
+
+  \li|Compare stage and public \c{buildtabs} and identify public machines that
+      are no longer present on stage. We aim to at least have a build machine
+      for the primary compiler for each operating system.|
+
+  \li|Temporarily add missing machines to stage build bots.|
+
+  \li|Uncomment controller URL for public repository in \c{devel-config} and
+      \c{stage-config} build bot configuratons. Regenerate and reboot.|
+
+  \li|Confirm all the primary configurations are being built.|
+
+  \li|Wait for the builds to complete (note that there may be unbuilt
+      entries for secondary configurations) and compare public toolchain
+      build results to stage for regressions. See the detailed instructions
+      in \c{private}.||
+
 \h#copy|Update copyright if new year|
 
   Use the \c{git/copyright} script. See the script header for instructions.