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 Tag release candidates using the tag.sh script in utils/release.
146 $ ./tag.sh -release X.Y.Z -rc $RC
149 be done with the export.sh script in utils/release.
153 $ ./export.sh -release X.Y.Z -rc $RC
163 builds are clean, then the release passes Build Qualification.
227 A release is qualified when it has no regressions from the previous release (or
233 each product and only include things on the list. Every release will have
235 software. We need a very concrete and definitive release criteria that
239 which must be satisfied before a release can go out.**
246 ``test-suite`` from the previous release.
261 | x86-32 | Linux | last release | llvm regression tests, |
265 | x86-32 | FreeBSD | last release | llvm regression tests, |
271 | x86-64 | Mac OS 10.X | last release | llvm regression tests, |
275 | x86-64 | Linux | last release | llvm regression tests, |
279 | x86-64 | FreeBSD | last release | llvm regression tests, |
283 | ARMv7A | Linux | last release | llvm regression tests, |
291 Once all testing has been completed and appropriate bugs filed, the release
293 Ask that all LLVM developers test the release in 2 ways:
304 to the list. Verify that there are no regressions from the previous release.
305 The results are not used to qualify a release, but to spot other potential
310 second release candidate is tagged.
315 the release is determined to be ready and the release manager may move onto the
321 Below are the rules regarding patching the release branch:
323 #. Patches applied to the release branch may only be applied by the release
336 the previous major release. Only bugfixes will be accepted.
341 The final stages of the release process involves tagging the "final" release
342 branch, updating documentation that refers to the release, and updating the
351 be updated to reflect the new release version number tag available from
353 mainline into the release branch.
360 Tag the final release sources using the tag.sh script in utils/release.
364 $ ./tag.sh -release X.Y.Z -final
369 The LLVM demo page must be updated to use the new release. This consists of
375 The website must be updated before the release announcement is sent out. Here
388 #. Commit the ``index.html`` to the ``release/X.Y`` directory to redirect (use
389 from previous release).
391 #. Update the ``releases/download.html`` file with the new release.
393 #. Update the ``releases/index.html`` with the new release and link to release
397 new release and release announcement. Make sure this all gets committed back
403 Have Chris send out the release announcement when everything is finished.