<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="X-UA-Compatible" content="IE=Edge" />
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>How To Release LLVM To The Public — LLVM 8 documentation</title>
<link rel="stylesheet" href="_static/llvm-theme.css" type="text/css" />
<link rel="stylesheet" href="_static/pygments.css" type="text/css" />
<script type="text/javascript" id="documentation_options" data-url_root="./" src="_static/documentation_options.js"></script>
<script type="text/javascript" src="_static/jquery.js"></script>
<script type="text/javascript" src="_static/underscore.js"></script>
<script type="text/javascript" src="_static/doctools.js"></script>
<script type="text/javascript" src="_static/language_data.js"></script>
<link rel="index" title="Index" href="genindex.html" />
<link rel="search" title="Search" href="search.html" />
<link rel="next" title="Advice on Packaging LLVM" href="Packaging.html" />
<link rel="prev" title="LLVMBuild Guide" href="LLVMBuild.html" />
<style type="text/css">
table.right { float: right; margin-left: 20px; }
table.right td { border: 1px solid #ccc; }
</style>
</head><body>
<div class="logo">
<a href="index.html">
<img src="_static/logo.png"
alt="LLVM Logo" width="250" height="88"/></a>
</div>
<div class="related" role="navigation" aria-label="related navigation">
<h3>Navigation</h3>
<ul>
<li class="right" style="margin-right: 10px">
<a href="genindex.html" title="General Index"
accesskey="I">index</a></li>
<li class="right" >
<a href="Packaging.html" title="Advice on Packaging LLVM"
accesskey="N">next</a> |</li>
<li class="right" >
<a href="LLVMBuild.html" title="LLVMBuild Guide"
accesskey="P">previous</a> |</li>
<li><a href="http://llvm.org/">LLVM Home</a> | </li>
<li><a href="index.html">Documentation</a>»</li>
</ul>
</div>
<div class="document">
<div class="documentwrapper">
<div class="body" role="main">
<div class="section" id="how-to-release-llvm-to-the-public">
<h1>How To Release LLVM To The Public<a class="headerlink" href="#how-to-release-llvm-to-the-public" title="Permalink to this headline">¶</a></h1>
<div class="section" id="introduction">
<h2>Introduction<a class="headerlink" href="#introduction" title="Permalink to this headline">¶</a></h2>
<p>This document contains information about successfully releasing LLVM —
including sub-projects: e.g., <code class="docutils literal notranslate"><span class="pre">clang</span></code> and <code class="docutils literal notranslate"><span class="pre">compiler-rt</span></code> — to the public.
It is the Release Manager’s responsibility to ensure that a high quality build
of LLVM is released.</p>
<p>If you’re looking for the document on how to test the release candidates and
create the binary packages, please refer to the <a class="reference internal" href="ReleaseProcess.html"><span class="doc">How To Validate a New Release</span></a> instead.</p>
</div>
<div class="section" id="release-timeline">
<span id="timeline"></span><h2>Release Timeline<a class="headerlink" href="#release-timeline" title="Permalink to this headline">¶</a></h2>
<p>LLVM is released on a time based schedule — with major releases roughly
every 6 months. In between major releases there may be dot releases.
The release manager will determine if and when to make a dot release based
on feedback from the community. Typically, dot releases should be made if
there are large number of bug-fixes in the stable branch or a critical bug
has been discovered that affects a large number of users.</p>
<p>Unless otherwise stated, dot releases will follow the same procedure as
major releases.</p>
<p>The release process is roughly as follows:</p>
<ul class="simple">
<li>Set code freeze and branch creation date for 6 months after last code freeze
date. Announce release schedule to the LLVM community and update the website.</li>
<li>Create release branch and begin release process.</li>
<li>Send out release candidate sources for first round of testing. Testing lasts
7-10 days. During the first round of testing, any regressions found should be
fixed. Patches are merged from mainline into the release branch. Also, all
features need to be completed during this time. Any features not completed at
the end of the first round of testing will be removed or disabled for the
release.</li>
<li>Generate and send out the second release candidate sources. Only <em>critical</em>
bugs found during this testing phase will be fixed. Any bugs introduced by
merged patches will be fixed. If so a third round of testing is needed.</li>
<li>The release notes are updated.</li>
<li>Finally, release!</li>
</ul>
<p>The release process will be accelerated for dot releases. If the first round
of testing finds no critical bugs and no regressions since the last major release,
then additional rounds of testing will not be required.</p>
</div>
<div class="section" id="release-process">
<h2>Release Process<a class="headerlink" href="#release-process" title="Permalink to this headline">¶</a></h2>
<div class="contents local topic" id="contents">
<ul class="simple">
<li><a class="reference internal" href="#release-administrative-tasks" id="id1">Release Administrative Tasks</a><ul>
<li><a class="reference internal" href="#create-release-branch" id="id2">Create Release Branch</a></li>
<li><a class="reference internal" href="#update-llvm-version" id="id3">Update LLVM Version</a></li>
<li><a class="reference internal" href="#tagging-the-llvm-release-candidates" id="id4">Tagging the LLVM Release Candidates</a></li>
<li><a class="reference internal" href="#build-clang-binary-distribution" id="id5">Build Clang Binary Distribution</a></li>
</ul>
</li>
<li><a class="reference internal" href="#release-qualification-criteria" id="id6">Release Qualification Criteria</a></li>
<li><a class="reference internal" href="#official-testing" id="id7">Official Testing</a></li>
<li><a class="reference internal" href="#community-testing" id="id8">Community Testing</a></li>
<li><a class="reference internal" href="#reporting-regressions" id="id9">Reporting Regressions</a></li>
<li><a class="reference internal" href="#merge-requests" id="id10">Merge Requests</a></li>
<li><a class="reference internal" href="#release-patch-rules" id="id11">Release Patch Rules</a><ul>
<li><a class="reference internal" href="#merging-patches" id="id12">Merging Patches</a></li>
</ul>
</li>
<li><a class="reference internal" href="#release-final-tasks" id="id13">Release Final Tasks</a><ul>
<li><a class="reference internal" href="#update-documentation" id="id14">Update Documentation</a></li>
<li><a class="reference internal" href="#tag-the-llvm-final-release" id="id15">Tag the LLVM Final Release</a></li>
</ul>
</li>
<li><a class="reference internal" href="#update-the-llvm-demo-page" id="id16">Update the LLVM Demo Page</a><ul>
<li><a class="reference internal" href="#update-the-llvm-website" id="id17">Update the LLVM Website</a></li>
<li><a class="reference internal" href="#announce-the-release" id="id18">Announce the Release</a></li>
</ul>
</li>
</ul>
</div>
<div class="section" id="release-administrative-tasks">
<h3><a class="toc-backref" href="#id1">Release Administrative Tasks</a><a class="headerlink" href="#release-administrative-tasks" title="Permalink to this headline">¶</a></h3>
<p>This section describes a few administrative tasks that need to be done for the
release process to begin. Specifically, it involves:</p>
<ul class="simple">
<li>Creating the release branch,</li>
<li>Setting version numbers, and</li>
<li>Tagging release candidates for the release team to begin testing.</li>
</ul>
<div class="section" id="create-release-branch">
<h4><a class="toc-backref" href="#id2">Create Release Branch</a><a class="headerlink" href="#create-release-branch" title="Permalink to this headline">¶</a></h4>
<p>Branch the Subversion trunk using the following procedure:</p>
<ol class="arabic">
<li><p class="first">Remind developers that the release branching is imminent and to refrain from
committing patches that might break the build. E.g., new features, large
patches for works in progress, an overhaul of the type system, an exciting
new TableGen feature, etc.</p>
</li>
<li><p class="first">Verify that the current Subversion trunk is in decent shape by
examining nightly tester and buildbot results.</p>
</li>
<li><p class="first">Create the release branch for <code class="docutils literal notranslate"><span class="pre">llvm</span></code>, <code class="docutils literal notranslate"><span class="pre">clang</span></code>, and other sub-projects,
from the last known good revision. The branch’s name is
<code class="docutils literal notranslate"><span class="pre">release_XY</span></code>, where <code class="docutils literal notranslate"><span class="pre">X</span></code> is the major and <code class="docutils literal notranslate"><span class="pre">Y</span></code> the minor release
numbers. Use <code class="docutils literal notranslate"><span class="pre">utils/release/tag.sh</span></code> to tag the release.</p>
</li>
<li><p class="first">Advise developers that they may now check their patches into the Subversion
tree again.</p>
</li>
<li><p class="first">The Release Manager should switch to the release branch, because all changes
to the release will now be done in the branch. The easiest way to do this is
to grab a working copy using the following commands:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span>$ svn co https://llvm.org/svn/llvm-project/llvm/branches/release_XY llvm-X.Y
$ svn co https://llvm.org/svn/llvm-project/cfe/branches/release_XY clang-X.Y
$ svn co https://llvm.org/svn/llvm-project/test-suite/branches/release_XY test-suite-X.Y
</pre></div>
</div>
</li>
</ol>
</div>
<div class="section" id="update-llvm-version">
<h4><a class="toc-backref" href="#id3">Update LLVM Version</a><a class="headerlink" href="#update-llvm-version" title="Permalink to this headline">¶</a></h4>
<p>After creating the LLVM release branch, update the release branches’
<code class="docutils literal notranslate"><span class="pre">autoconf</span></code> and <code class="docutils literal notranslate"><span class="pre">configure.ac</span></code> versions from ‘<code class="docutils literal notranslate"><span class="pre">X.Ysvn</span></code>’ to ‘<code class="docutils literal notranslate"><span class="pre">X.Y</span></code>’.
Update it on mainline as well to be the next version (‘<code class="docutils literal notranslate"><span class="pre">X.Y+1svn</span></code>’).
Regenerate the configure scripts for both <code class="docutils literal notranslate"><span class="pre">llvm</span></code> and the <code class="docutils literal notranslate"><span class="pre">test-suite</span></code>.</p>
<p>In addition, the version numbers of all the Bugzilla components must be updated
for the next release.</p>
</div>
<div class="section" id="tagging-the-llvm-release-candidates">
<h4><a class="toc-backref" href="#id4">Tagging the LLVM Release Candidates</a><a class="headerlink" href="#tagging-the-llvm-release-candidates" title="Permalink to this headline">¶</a></h4>
<p>Tag release candidates using the tag.sh script in utils/release.</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span>$ ./tag.sh -release X.Y.Z -rc $RC
</pre></div>
</div>
<p>The Release Manager may supply pre-packaged source tarballs for users. This can
be done with the export.sh script in utils/release.</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span>$ ./export.sh -release X.Y.Z -rc $RC
</pre></div>
</div>
<p>This will generate source tarballs for each LLVM project being validated, which
can be uploaded to the website for further testing.</p>
</div>
<div class="section" id="build-clang-binary-distribution">
<h4><a class="toc-backref" href="#id5">Build Clang Binary Distribution</a><a class="headerlink" href="#build-clang-binary-distribution" title="Permalink to this headline">¶</a></h4>
<p>Creating the <code class="docutils literal notranslate"><span class="pre">clang</span></code> binary distribution requires following the instructions
<a class="reference internal" href="ReleaseProcess.html"><span class="doc">here</span></a>.</p>
<p>That process will perform both Release+Asserts and Release builds but only
pack the Release build for upload. You should use the Release+Asserts sysroot,
normally under <code class="docutils literal notranslate"><span class="pre">final/Phase3/Release+Asserts/llvmCore-3.8.1-RCn.install/</span></code>,
for test-suite and run-time benchmarks, to make sure nothing serious has
passed through the net. For compile-time benchmarks, use the Release version.</p>
<p>The minimum required version of the tools you’ll need are <a class="reference internal" href="GettingStarted.html"><span class="doc">here</span></a></p>
</div>
</div>
<div class="section" id="release-qualification-criteria">
<h3><a class="toc-backref" href="#id6">Release Qualification Criteria</a><a class="headerlink" href="#release-qualification-criteria" title="Permalink to this headline">¶</a></h3>
<p>A release is qualified when it has no regressions from the previous release (or
baseline). Regressions are related to correctness first and performance second.
(We may tolerate some minor performance regressions if they are deemed
necessary for the general quality of the compiler.)</p>
<p>More specifically, Clang/LLVM is qualified when it has a clean test with all
supported sub-projects included (<code class="docutils literal notranslate"><span class="pre">make</span> <span class="pre">check-all</span></code>), per target, and it has no
regressions with the <code class="docutils literal notranslate"><span class="pre">test-suite</span></code> in relation to the previous release.</p>
<p>Regressions are new failures in the set of tests that are used to qualify
each product and only include things on the list. Every release will have
some bugs in it. It is the reality of developing a complex piece of
software. We need a very concrete and definitive release criteria that
ensures we have monotonically improving quality on some metric. The metric we
use is described below. This doesn’t mean that we don’t care about other
criteria, but these are the criteria which we found to be most important and
which must be satisfied before a release can go out.</p>
</div>
<div class="section" id="official-testing">
<h3><a class="toc-backref" href="#id7">Official Testing</a><a class="headerlink" href="#official-testing" title="Permalink to this headline">¶</a></h3>
<p>A few developers in the community have dedicated time to validate the release
candidates and volunteered to be the official release testers for each
architecture.</p>
<p>These will be the ones testing, generating and uploading the official binaries
to the server, and will be the minimum tests <em>necessary</em> for the release to
proceed.</p>
<p>This will obviously not cover all OSs and distributions, so additional community
validation is important. However, if community input is not reached before the
release is out, all bugs reported will have to go on the next stable release.</p>
<p>The official release managers are:</p>
<ul class="simple">
<li>Major releases (X.0): Hans Wennborg</li>
<li>Stable releases (X.n): Tom Stellard</li>
</ul>
<p>The official release testers are volunteered from the community and have
consistently validated and released binaries for their targets/OSs. To contact
them, you should email the <code class="docutils literal notranslate"><span class="pre">release-testers@lists.llvm.org</span></code> mailing list.</p>
<p>The official testers list is in the file <code class="docutils literal notranslate"><span class="pre">RELEASE_TESTERS.TXT</span></code>, in the <code class="docutils literal notranslate"><span class="pre">LLVM</span></code>
repository.</p>
</div>
<div class="section" id="community-testing">
<h3><a class="toc-backref" href="#id8">Community Testing</a><a class="headerlink" href="#community-testing" title="Permalink to this headline">¶</a></h3>
<p>Once all testing has been completed and appropriate bugs filed, the release
candidate tarballs are put on the website and the LLVM community is notified.</p>
<p>We ask that all LLVM developers test the release in any the following ways:</p>
<ol class="arabic simple">
<li>Download <code class="docutils literal notranslate"><span class="pre">llvm-X.Y</span></code>, <code class="docutils literal notranslate"><span class="pre">llvm-test-X.Y</span></code>, and the appropriate <code class="docutils literal notranslate"><span class="pre">clang</span></code>
binary. Build LLVM. Run <code class="docutils literal notranslate"><span class="pre">make</span> <span class="pre">check</span></code> and the full LLVM test suite (<code class="docutils literal notranslate"><span class="pre">make</span>
<span class="pre">TEST=nightly</span> <span class="pre">report</span></code>).</li>
<li>Download <code class="docutils literal notranslate"><span class="pre">llvm-X.Y</span></code>, <code class="docutils literal notranslate"><span class="pre">llvm-test-X.Y</span></code>, and the <code class="docutils literal notranslate"><span class="pre">clang</span></code> sources. Compile
everything. Run <code class="docutils literal notranslate"><span class="pre">make</span> <span class="pre">check</span></code> and the full LLVM test suite (<code class="docutils literal notranslate"><span class="pre">make</span>
<span class="pre">TEST=nightly</span> <span class="pre">report</span></code>).</li>
<li>Download <code class="docutils literal notranslate"><span class="pre">llvm-X.Y</span></code>, <code class="docutils literal notranslate"><span class="pre">llvm-test-X.Y</span></code>, and the appropriate <code class="docutils literal notranslate"><span class="pre">clang</span></code>
binary. Build whole programs with it (ex. Chromium, Firefox, Apache) for
your platform.</li>
<li>Download <code class="docutils literal notranslate"><span class="pre">llvm-X.Y</span></code>, <code class="docutils literal notranslate"><span class="pre">llvm-test-X.Y</span></code>, and the appropriate <code class="docutils literal notranslate"><span class="pre">clang</span></code>
binary. Build <em>your</em> programs with it and check for conformance and
performance regressions.</li>
<li>Run the <a class="reference internal" href="ReleaseProcess.html"><span class="doc">release process</span></a>, if your platform is
<em>different</em> than that which is officially supported, and report back errors
only if they were not reported by the official release tester for that
architecture.</li>
</ol>
<p>We also ask that the OS distribution release managers test their packages with
the first candidate of every release, and report any <em>new</em> errors in Bugzilla.
If the bug can be reproduced with an unpatched upstream version of the release
candidate (as opposed to the distribution’s own build), the priority should be
release blocker.</p>
<p>During the first round of testing, all regressions must be fixed before the
second release candidate is tagged.</p>
<p>In the subsequent stages, the testing is only to ensure that bug
fixes previously merged in have not created new major problems. <em>This is not
the time to solve additional and unrelated bugs!</em> If no patches are merged in,
the release is determined to be ready and the release manager may move onto the
next stage.</p>
</div>
<div class="section" id="reporting-regressions">
<h3><a class="toc-backref" href="#id9">Reporting Regressions</a><a class="headerlink" href="#reporting-regressions" title="Permalink to this headline">¶</a></h3>
<p>Every regression that is found during the tests (as per the criteria above),
should be filled in a bug in Bugzilla with the priority <em>release blocker</em> and
blocking a specific release.</p>
<p>To help manage all the bugs reported and which ones are blockers or not, a new
“[meta]” bug should be created and all regressions <em>blocking</em> that Meta. Once
all blockers are done, the Meta can be closed.</p>
<p>If a bug can’t be reproduced, or stops being a blocker, it should be removed
from the Meta and its priority decreased to <em>normal</em>. Debugging can continue,
but on trunk.</p>
</div>
<div class="section" id="merge-requests">
<h3><a class="toc-backref" href="#id10">Merge Requests</a><a class="headerlink" href="#merge-requests" title="Permalink to this headline">¶</a></h3>
<p>You can use any of the following methods to request that a revision from trunk
be merged into a release branch:</p>
<ol class="arabic simple">
<li>Use the <code class="docutils literal notranslate"><span class="pre">utils/release/merge-request.sh</span></code> script which will automatically
file a <a class="reference external" href="https://bugs.llvm.org/">bug</a> requesting that the patch be merged. e.g. To request revision
12345 be merged into the branch for the 5.0.1 release:
<code class="docutils literal notranslate"><span class="pre">llvm.src/utils/release/merge-request.sh</span> <span class="pre">-stable-version</span> <span class="pre">5.0</span> <span class="pre">-r</span> <span class="pre">12345</span> <span class="pre">-user</span> <span class="pre">bugzilla@example.com</span></code></li>
<li>Manually file a <a class="reference external" href="https://bugs.llvm.org/">bug</a> with the subject: “Merge r12345 into the X.Y branch”,
enter the commit(s) that you want merged in the “Fixed by Commit(s)” and mark
it as a blocker of the current release bug. Release bugs are given aliases
in the form of release-x.y.z, so to mark a bug as a blocker for the 5.0.1
release, just enter release-5.0.1 in the “Blocks” field.</li>
<li>Reply to the commit email on llvm-commits for the revision to merge and cc
the release manager.</li>
</ol>
</div>
<div class="section" id="release-patch-rules">
<h3><a class="toc-backref" href="#id11">Release Patch Rules</a><a class="headerlink" href="#release-patch-rules" title="Permalink to this headline">¶</a></h3>
<p>Below are the rules regarding patching the release branch:</p>
<ol class="arabic simple">
<li>Patches applied to the release branch may only be applied by the release
manager, the official release testers or the code owners with approval from
the release manager.</li>
<li>During the first round of testing, patches that fix regressions or that are
small and relatively risk free (verified by the appropriate code owner) are
applied to the branch. Code owners are asked to be very conservative in
approving patches for the branch. We reserve the right to reject any patch
that does not fix a regression as previously defined.</li>
<li>During the remaining rounds of testing, only patches that fix critical
regressions may be applied.</li>
<li>For dot releases all patches must maintain both API and ABI compatibility with
the previous major release. Only bug-fixes will be accepted.</li>
</ol>
<div class="section" id="merging-patches">
<h4><a class="toc-backref" href="#id12">Merging Patches</a><a class="headerlink" href="#merging-patches" title="Permalink to this headline">¶</a></h4>
<p>The <code class="docutils literal notranslate"><span class="pre">utils/release/merge.sh</span></code> script can be used to merge individual revisions
into any one of the llvm projects. To merge revision <code class="docutils literal notranslate"><span class="pre">$N</span></code> into project
<code class="docutils literal notranslate"><span class="pre">$PROJ</span></code>, do:</p>
<ol class="arabic simple">
<li><code class="docutils literal notranslate"><span class="pre">svn</span> <span class="pre">co</span> <span class="pre">https://llvm.org/svn/llvm-project/$PROJ/branches/release_XX</span>
<span class="pre">$PROJ.src</span></code></li>
<li><code class="docutils literal notranslate"><span class="pre">$PROJ.src/utils/release/merge.sh</span> <span class="pre">--proj</span> <span class="pre">$PROJ</span> <span class="pre">--rev</span> <span class="pre">$N</span></code></li>
<li>Run regression tests.</li>
<li><code class="docutils literal notranslate"><span class="pre">cd</span> <span class="pre">$PROJ.src</span></code>. Run the <code class="docutils literal notranslate"><span class="pre">svn</span> <span class="pre">commit</span></code> command printed out by <code class="docutils literal notranslate"><span class="pre">merge.sh</span></code>
in step 2.</li>
</ol>
</div>
</div>
<div class="section" id="release-final-tasks">
<h3><a class="toc-backref" href="#id13">Release Final Tasks</a><a class="headerlink" href="#release-final-tasks" title="Permalink to this headline">¶</a></h3>
<p>The final stages of the release process involves tagging the “final” release
branch, updating documentation that refers to the release, and updating the
demo page.</p>
<div class="section" id="update-documentation">
<h4><a class="toc-backref" href="#id14">Update Documentation</a><a class="headerlink" href="#update-documentation" title="Permalink to this headline">¶</a></h4>
<p>Review the documentation and ensure that it is up to date. The “Release Notes”
must be updated to reflect new features, bug fixes, new known issues, and
changes in the list of supported platforms. The “Getting Started Guide” should
be updated to reflect the new release version number tag available from
Subversion and changes in basic system requirements. Merge both changes from
mainline into the release branch.</p>
</div>
<div class="section" id="tag-the-llvm-final-release">
<span id="tag"></span><h4><a class="toc-backref" href="#id15">Tag the LLVM Final Release</a><a class="headerlink" href="#tag-the-llvm-final-release" title="Permalink to this headline">¶</a></h4>
<p>Tag the final release sources using the tag.sh script in utils/release.</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span>$ ./tag.sh -release X.Y.Z -final
</pre></div>
</div>
</div>
</div>
<div class="section" id="update-the-llvm-demo-page">
<h3><a class="toc-backref" href="#id16">Update the LLVM Demo Page</a><a class="headerlink" href="#update-the-llvm-demo-page" title="Permalink to this headline">¶</a></h3>
<p>The LLVM demo page must be updated to use the new release. This consists of
using the new <code class="docutils literal notranslate"><span class="pre">clang</span></code> binary and building LLVM.</p>
<div class="section" id="update-the-llvm-website">
<h4><a class="toc-backref" href="#id17">Update the LLVM Website</a><a class="headerlink" href="#update-the-llvm-website" title="Permalink to this headline">¶</a></h4>
<p>The website must be updated before the release announcement is sent out. Here
is what to do:</p>
<ol class="arabic simple">
<li>Check out the <code class="docutils literal notranslate"><span class="pre">www</span></code> module from Subversion.</li>
<li>Create a new sub-directory <code class="docutils literal notranslate"><span class="pre">X.Y</span></code> in the releases directory.</li>
<li>Commit the <code class="docutils literal notranslate"><span class="pre">llvm</span></code>, <code class="docutils literal notranslate"><span class="pre">test-suite</span></code>, <code class="docutils literal notranslate"><span class="pre">clang</span></code> source and binaries in this
new directory.</li>
<li>Copy and commit the <code class="docutils literal notranslate"><span class="pre">llvm/docs</span></code> and <code class="docutils literal notranslate"><span class="pre">LICENSE.txt</span></code> files into this new
directory. The docs should be built with <code class="docutils literal notranslate"><span class="pre">BUILD_FOR_WEBSITE=1</span></code>.</li>
<li>Commit the <code class="docutils literal notranslate"><span class="pre">index.html</span></code> to the <code class="docutils literal notranslate"><span class="pre">release/X.Y</span></code> directory to redirect (use
from previous release).</li>
<li>Update the <code class="docutils literal notranslate"><span class="pre">releases/download.html</span></code> file with the new release.</li>
<li>Update the <code class="docutils literal notranslate"><span class="pre">releases/index.html</span></code> with the new release and link to release
documentation.</li>
<li>Finally, update the main page (<code class="docutils literal notranslate"><span class="pre">index.html</span></code> and sidebar) to point to the
new release and release announcement. Make sure this all gets committed back
into Subversion.</li>
</ol>
</div>
<div class="section" id="announce-the-release">
<h4><a class="toc-backref" href="#id18">Announce the Release</a><a class="headerlink" href="#announce-the-release" title="Permalink to this headline">¶</a></h4>
<p>Send an email to the list announcing the release, pointing people to all the
relevant documentation, download pages and bugs fixed.</p>
</div>
</div>
</div>
</div>
</div>
</div>
<div class="clearer"></div>
</div>
<div class="related" role="navigation" aria-label="related navigation">
<h3>Navigation</h3>
<ul>
<li class="right" style="margin-right: 10px">
<a href="genindex.html" title="General Index"
>index</a></li>
<li class="right" >
<a href="Packaging.html" title="Advice on Packaging LLVM"
>next</a> |</li>
<li class="right" >
<a href="LLVMBuild.html" title="LLVMBuild Guide"
>previous</a> |</li>
<li><a href="http://llvm.org/">LLVM Home</a> | </li>
<li><a href="index.html">Documentation</a>»</li>
</ul>
</div>
<div class="footer" role="contentinfo">
© Copyright 2003-2020, LLVM Project.
Last updated on 2020-09-07.
Created using <a href="http://sphinx-doc.org/">Sphinx</a> 1.8.4.
</div>
</body>
</html>
distrib
>
Mageia
>
7
>
i586
>
media
>
core-updates
>
by-pkgid
>
d635a8cd705396ade48f1d2b830a115d
>
files
>
2020
