Lines Matching +full:pre +full:- +full:release
2 How To Validate a New Release
12 This document contains information about testing the release candidates that will
13 ultimately be the next LLVM release. For more information on how to manage the
14 actual release, please refer to :doc:`HowToReleaseLLVM`.
16 Overview of the Release Process
17 -------------------------------
19 Once the release process starts, the Release Manager will ask for volunteers,
22 * Test and benchmark the previous release
24 * Test and benchmark each release candidate, comparing to the previous release and candidates
28 * Make sure the critical bugs get fixed and merged to the next release candidate
30 Not all bugs or regressions are show-stoppers and it's a bit of a grey area what
31 should be fixed before the next candidate and what can wait until the next release.
39 * The stage in the release. Less critical bugs should be considered to be fixed between
50 The scripts are in the ``utils/release`` directory.
52 test-release.sh
53 ---------------
55 This script will check-out, configure and compile LLVM+Clang (+ most add-ons, like ``compiler-rt``,
56 ``libcxx``, ``libomp`` and ``clang-extra-tools``) in three stages, and will test the final stage.
58 that's the one you should use for the test-suite and other external tests.
60 To run the script on a specific release candidate run::
62 ./test-release.sh \
63 -release 3.3 \
64 -rc 1 \
65 -no-64bit \
66 -test-asserts \
67 -no-compare-files
70 ``-no-64bit`` while 32-bit systems will, or the script will fail.
74 * On the pre-release, you should change ``-rc 1`` to ``-final``. On RC2, change it to ``-rc 2`` and…
76 * On non-release testing, you can use ``-final`` in conjunction with ``-no-checkout``, but you'll h…
79 * For release candidates, you need ``-test-asserts``, or it won't create a "Release+Asserts" direct…
80 which is needed for release testing and benchmarking. This will take twice as long.
82 * On the final candidate you just need Release builds, and that's the binary directory you'll have …
84 This script builds three phases of Clang+LLVM twice each (Release and Release+Asserts), so use
87 Use the ``--help`` option to see all the options and chose it according to your needs.
90 findRegressions-nightly.py
91 --------------------------
95 .. _test-suite:
103 …uick Start Guide <http://llvm.org/docs/lnt/quickstart.html>`__ link on how to set-up the test-suite
105 …ion you'll have to use for testing is inside the ``rcN/Phase3/Release+Asserts/llvmCore-REL-RC.inst…
106 Link that directory to an easier location and run the test-suite.
113 -j4 \
114 --sandbox sandbox \
115 --test-suite ~/devel/llvm/test/test-suite \
116 --cc ~/devel/llvm/install/bin/clang \
117 --cxx ~/devel/llvm/install/bin/clang++
119 It should have no new regressions, compared to the previous release or release candidate. You don't…
120 all the bugs in the test-suite, since they're not necessarily meant to pass on all architectures al…
125 as important, but not necessarily blocking the release to proceed. They can be set as "known failur…
128 .. _pre-release-process:
130 Pre-Release Process
136 When the release process is announced on the mailing list, you should prepare
137 for the testing, by applying the same testing you'll do on the release candidates,
138 on the previous release.
142 * Download the previous release sources from http://llvm.org/releases/download.html.
144 * Run the test-release.sh script on ``final`` mode (change ``-rc 1`` to ``-final``).
148 * Using the ``Phase3/Release+Asserts/llvmCore-MAJ.MIN-final.install`` base, run the test-suite.
150 If the final phase's ``make check-all`` failed, it's a good idea to also test the
151 intermediate stages by going on the obj directory and running ``make check-all`` to find
155 .. _release-process:
157 Release Process
163 When the Release Manager sends you the release candidate, download all sources,
164 unzip on the same directory (there will be sym-links from the appropriate places
165 to them), and run the release test as above.
169 * Download the current candidate sources from where the release manager points you
170 (ex. http://llvm.org/pre-releases/3.3/rc1/).
172 * Repeat the steps above with ``-rc 1``, ``-rc 2`` etc modes and run the test-suite
176 where the release manager can grab it.
178 Once the release manages announces that the latest candidate is the good one, you
179 have to pack the ``Release`` (no Asserts) install directory on ``Phase3`` and that
182 * Rename (or link) ``clang+llvm-REL-ARCH-ENV`` to the .install directory
186 * Make it available for the release manager to download
188 .. _bug-reporting:
196 If you found regressions or failures when comparing a release candidate with the
197 previous release, follow the rules below:
202 * Check-all tests should be fixed before the next release candidate, but can wait
203 until the test-suite run is finished.
205 * Bugs in the test suite or unimportant check-all tests can be fixed in between
206 release candidates.
208 * New features or recent big changes, when close to the release, should have done