Lines Matching refs:release
17 If you're looking for the document on how to test the release candidates and
27 The release manager will determine if and when to make a dot release based
35 The release process is roughly as follows:
38 date. Announce release schedule to the LLVM community and update the website.
40 * Create release branch and begin release process.
42 * Send out release candidate sources for first round of testing. Testing lasts
44 fixed. Patches are merged from mainline into the release branch. Also, all
47 release.
49 * Generate and send out the second release candidate sources. Only *critial*
53 * The release notes are updated.
55 * Finally, release!
57 The release process will be accelerated for dot releases. If the first round
58 of testing finds no critical bugs and no regressions since the last major release,
71 release process to begin. Specifically, it involves:
73 * Creating the release branch,
77 * Tagging release candidates for the release team to begin testing.
84 #. Remind developers that the release branching is imminent and to refrain from
92 #. Create the release branch for ``llvm``, ``clang``, the ``test-suite``, and
94 ``release_XY``, where ``X`` is the major and ``Y`` the minor release
114 #. The Release Manager should switch to the release branch, because all changes
115 to the release will now be done in the branch. The easiest way to do this is
131 After creating the LLVM release branch, update the release branches'
137 for the next release.
142 Create release candidates for ``llvm``, ``clang``, ``dragonegg``, and the LLVM
143 ``test-suite`` by tagging the branch with the respective release candidate
166 a permanent copy of the release candidate around for people to export and build
190 builds are clean, then the release passes Build Qualification.
254 A release is qualified when it has no regressions from the previous release (or
260 each product and only include things on the list. Every release will have
262 software. We need a very concrete and definitive release criteria that
266 which must be satisfied before a release can go out.**
273 ``test-suite`` from the previous release.
288 | x86-32 | Linux | last release | llvm regression tests, |
292 | x86-32 | FreeBSD | last release | llvm regression tests, |
298 | x86-64 | Mac OS 10.X | last release | llvm regression tests, |
302 | x86-64 | Linux | last release | llvm regression tests, |
306 | x86-64 | FreeBSD | last release | llvm regression tests, |
310 | ARMv7A | Linux | last release | llvm regression tests, |
318 Once all testing has been completed and appropriate bugs filed, the release
320 Ask that all LLVM developers test the release in 2 ways:
331 to the list. Verify that there are no regressions from the previous release.
332 The results are not used to qualify a release, but to spot other potential
337 second release candidate is tagged.
342 the release is determined to be ready and the release manager may move onto the
348 Below are the rules regarding patching the release branch:
350 #. Patches applied to the release branch may only be applied by the release
363 the previous major release. Only bugfixes will be accepted.
368 The final stages of the release process involves tagging the "final" release
369 branch, updating documentation that refers to the release, and updating the
378 be updated to reflect the new release version number tag available from
380 mainline into the release branch.
387 Tag the final release sources using the following procedure:
406 The LLVM demo page must be updated to use the new release. This consists of
412 The website must be updated before the release announcement is sent out. Here
425 #. Commit the ``index.html`` to the ``release/X.Y`` directory to redirect (use
426 from previous release).
428 #. Update the ``releases/download.html`` file with the new release.
430 #. Update the ``releases/index.html`` with the new release and link to release
434 new release and release announcement. Make sure this all gets committed back
440 Have Chris send out the release announcement when everything is finished.