[PATCH] D21880: Overhaul the release process docs

Daniel Sanders via llvm-commits llvm-commits at lists.llvm.org
Tue Jul 5 07:57:51 PDT 2016

dsanders added a subscriber: dsanders.

Comment at: docs/ReleaseProcess.rst:93-94
@@ -56,4 +92,4 @@
 ``libcxx``, ``libomp`` and ``clang-extra-tools``) in three stages, and will test the final stage.
-It'll have installed the final binaries on the Phase3/Releasei(+Asserts) directory, and
+It'll have installed the final binaries on the Phase3/Release(+Asserts) directory, and
 that's the one you should use for the test-suite and other external tests.
FWIW, I've always used the clang+llvm-*.tar.xz tarballs for external testing since this is the package we release and doesn't have anything left over from the build

Comment at: docs/ReleaseProcess.rst:110
@@ -73,3 +109,3 @@
 * On the pre-release, you should change ``-rc 1`` to ``-final``. On RC2, change it to ``-rc 2`` and so on.
Did you mean `pre-release` here? Going by the reference to `-final` I think it should say `release`.

Comment at: docs/ReleaseProcess.rst:112-113
@@ -75,4 +111,4 @@
 * On non-release testing, you can use ``-final`` in conjunction with ``-no-checkout``, but you'll have to
   create the ``final`` directory by hand and link the correct source dir to ``final/llvm.src``.
I'm not sure what is meant by 'non-release testing' here.

Also, should there be a bullet point for -svn-path? It's mostly useful for testing the tip of a branch (including trunk) before a tag has been created.


More information about the llvm-commits mailing list