maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/llvm/docs/HowToReleaseLLVM.html

627 lines
25 KiB
HTML
Raw Normal View History

A very early, rough draft of a guide to making public releases for LLVM. This document will detail the steps needed for making a quality release of LLVM that ensures the release functions and is of high quality. llvm-svn: 26978
2006-03-23 14:45:42 +08:00
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html>
<head>
<title>How To Release LLVM To The Public</title>
<link rel="stylesheet" href="llvm.css" type="text/css">
</head>
<body>
<div class="doc_title">How To Release LLVM To The Public</div>
<ol>
<li><a href="#introduction">Introduction</a></li>
First steps to document new release plan. llvm-svn: 79376
2009-08-19 06:33:28 +08:00
<li><a href="#criteria">Qualification Criteria</a></li>
Update how to release document. Add release version to getting started guide. llvm-svn: 42454
2007-09-29 06:50:54 +08:00
<li><a href="#introduction">Release Timeline</a></li>
* Remove duplicated table of contents for a section and at the top level * Fix relative links within the file * Add <tt> tags around command names and literal file names and directories llvm-svn: 27566
2006-04-11 05:43:05 +08:00
<li><a href="#process">Release Process</a></li>
A very early, rough draft of a guide to making public releases for LLVM. This document will detail the steps needed for making a quality release of LLVM that ensures the release functions and is of high quality. llvm-svn: 26978
2006-03-23 14:45:42 +08:00
</ol>
<div class="doc_author">
First steps to document new release plan. llvm-svn: 79376
2009-08-19 06:33:28 +08:00
<p>Written by <a href="mailto:tonic@nondot.org">Tanya Lattner</a>,
<a href="mailto:rspencer@x10sys.com">Reid Spencer</a>,
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
<a href="mailto:criswell@cs.uiuc.edu">John Criswell</a>, &amp;
<a href="mailto:wendling@apple.com">Bill Wendling</a>
First steps to document new release plan. llvm-svn: 79376
2009-08-19 06:33:28 +08:00
</p>
A very early, rough draft of a guide to making public releases for LLVM. This document will detail the steps needed for making a quality release of LLVM that ensures the release functions and is of high quality. llvm-svn: 26978
2006-03-23 14:45:42 +08:00
</div>
<!-- *********************************************************************** -->
<div class="doc_section"><a name="introduction">Introduction</a></div>
<!-- *********************************************************************** -->
<div class="doc_text">
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
<p>This document contains information about successfully releasing LLVM &mdash;
including subprojects: e.g., <tt>llvm-gcc</tt> and <tt>clang</tt> &mdash; to
the public. It is the Release Manager's responsibility to ensure that a high
quality build of LLVM is released.</p>
A very early, rough draft of a guide to making public releases for LLVM. This document will detail the steps needed for making a quality release of LLVM that ensures the release functions and is of high quality. llvm-svn: 26978
2006-03-23 14:45:42 +08:00
</div>
Update how to release document. Add release version to getting started guide. llvm-svn: 42454
2007-09-29 06:50:54 +08:00
<!-- *********************************************************************** -->
<div class="doc_section"><a name="process">Release Timeline</a></div>
<!-- *********************************************************************** -->
<div class="doc_text">
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
<p>LLVM is released on a time based schedule &mdash; roughly every 6 months. We
do not normally have dot releases because of the nature of LLVM's incremental
development philosophy. That said, the only thing preventing dot releases for
critical bug fixes from happening is a lack of resources &mdash; testers,
machines, time, etc. And, because of the high quality we desire for LLVM
releases, we cannot allow for a truncated form of release qualification.</p>
<p>The release process is roughly as follows:</p>
<ul>
<li><p>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.</p></li>
<li><p>Create release branch and begin release process.</p></li>
<li><p>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.</p></li>
<li><p>Generate and send out the second release candidate sources. Only
<em>critial</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.</p></li>
<li><p>The release notes are updated.</p></li>
<li><p>Finally, release!</p></li>
</ul>
</div>
Update how to release document. Add release version to getting started guide. llvm-svn: 42454
2007-09-29 06:50:54 +08:00
A very early, rough draft of a guide to making public releases for LLVM. This document will detail the steps needed for making a quality release of LLVM that ensures the release functions and is of high quality. llvm-svn: 26978
2006-03-23 14:45:42 +08:00
<!-- *********************************************************************** -->
<div class="doc_section"><a name="process">Release Process</a></div>
<!-- *********************************************************************** -->
<div class="doc_text">
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
<ol>
<li><a href="#release-admin">Release Administrative Tasks</a></li>
A very early, rough draft of a guide to making public releases for LLVM. This document will detail the steps needed for making a quality release of LLVM that ensures the release functions and is of high quality. llvm-svn: 26978
2006-03-23 14:45:42 +08:00
<ol>
Update how to release document. Add release version to getting started guide. llvm-svn: 42454
2007-09-29 06:50:54 +08:00
<li><a href="#branch">Create Release Branch</a></li>
First steps to document new release plan. llvm-svn: 79376
2009-08-19 06:33:28 +08:00
<li><a href="#verchanges">Update Version Numbers</a></li>
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
</ol>
<li><a href="#release-build">Building the Release</a></li>
<ol>
Update how to release document. Add release version to getting started guide. llvm-svn: 42454
2007-09-29 06:50:54 +08:00
<li><a href="#dist">Build the LLVM Source Distributions</a></li>
* Remove duplicated table of contents for a section and at the top level * Fix relative links within the file * Add <tt> tags around command names and literal file names and directories llvm-svn: 27566
2006-04-11 05:43:05 +08:00
<li><a href="#build">Build LLVM</a></li>
First steps to document new release plan. llvm-svn: 79376
2009-08-19 06:33:28 +08:00
<li><a href="#llvmgccbin">Build the LLVM-GCC Binary Distribution</a></li>
<li><a href="#clangbin">Build the Clang Binary Distribution</a></li>
<li><a href="#target-build">Target Specific Build Details</a></li>
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
</ol>
<li><a href="#release-qualify">Release Qualification Criteria</a></li>
<ol>
First steps to document new release plan. llvm-svn: 79376
2009-08-19 06:33:28 +08:00
<li><a href="#llvm-qualify">Qualify LLVM</a></li>
<li><a href="#llvmgcc-qualify">Qualify LLVM-GCC</a></li>
<li><a href="#clang-qualify">Qualify Clang</a></li>
<li><a href="#targets">Specific Target Qualification Details</a></li>
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
</ol>
<li><a href="#commTest">Community Testing</a></li>
<li><a href="#release-patch">Release Patch Rules</a></li>
<li><a href="#release-final">Release final tasks</a></li>
<ol>
Update how to release document. Add release version to getting started guide. llvm-svn: 42454
2007-09-29 06:50:54 +08:00
<li><a href="#updocs">Update Documentation</a></li>
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
<li><a href="#tag">Tag the LLVM Final Release</a></li>
Update how to release document. Add release version to getting started guide. llvm-svn: 42454
2007-09-29 06:50:54 +08:00
<li><a href="#updemo">Update the LLVM Demo Page</a></li>
Adding notes from release experience. llvm-svn: 29591
2006-08-10 08:23:05 +08:00
<li><a href="#webupdates">Update the LLVM Website</a></li>
Update how to release document. Add release version to getting started guide. llvm-svn: 42454
2007-09-29 06:50:54 +08:00
<li><a href="#announce">Announce the Release</a></li>
A very early, rough draft of a guide to making public releases for LLVM. This document will detail the steps needed for making a quality release of LLVM that ensures the release functions and is of high quality. llvm-svn: 26978
2006-03-23 14:45:42 +08:00
</ol>
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
</ol>
A very early, rough draft of a guide to making public releases for LLVM. This document will detail the steps needed for making a quality release of LLVM that ensures the release functions and is of high quality. llvm-svn: 26978
2006-03-23 14:45:42 +08:00
</div>
First pass over Reid's document. Changed the order of operations so that more of the fine tuning is performed in the release branch. This should free up mainline sooner to resume development. Removed information on the special release Makefile targets as I've never used them for a release; Tanya is investigating their integration, and they can be re-added if she uses them. Added an outline for building the LLVM GCC binary distributions. I will be filling that section out later (but before the 1.7 release). llvm-svn: 27595
2006-04-12 04:24:28 +08:00
<!-- ======================================================================= -->
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
<div class="doc_subsection"><a name="release-admin">Release Administrative Tasks</a></div>
First steps to document new release plan. llvm-svn: 79376
2009-08-19 06:33:28 +08:00
<div class="doc_text">
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
<p>This section describes a few administrative tasks that need to be done for
the release process to begin. Specifically, it involves:</p>
<ul>
<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>
First steps to document new release plan. llvm-svn: 79376
2009-08-19 06:33:28 +08:00
</div>
<!-- ======================================================================= -->
<div class="doc_subsubsection"><a name="branch">Create Release Branch</a></div>
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
A very early, rough draft of a guide to making public releases for LLVM. This document will detail the steps needed for making a quality release of LLVM that ensures the release functions and is of high quality. llvm-svn: 26978
2006-03-23 14:45:42 +08:00
<div class="doc_text">
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
<p>Branch the Subversion trunk using the following procedure:</p>
<ol>
<li><p>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>Verify that the current Subversion trunk is in decent shape by
examining nightly tester and buildbot results.</p></li>
<li><p>Create the release branch for <tt>llvm</tt>, <tt>llvm-gcc-4.2</tt>,
<tt>clang</tt>, and the <tt>test-suite</tt> from the last known good
revision. The branch's name is <tt>release_XY</tt>, where <tt>X</tt> is
the major and <tt>Y</tt> the minor release numbers. The branches should be
created using the following commands:</p>
Update how to release document. Add release version to getting started guide. llvm-svn: 42454
2007-09-29 06:50:54 +08:00
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
<div class="doc_code">
Converted to "svn" and reformatted. llvm-svn: 40416
2007-07-23 12:41:42 +08:00
<pre>
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
$ svn copy https://llvm.org/svn/llvm-project/llvm/trunk \
https://llvm.org/svn/llvm-project/llvm/branches/release_<i>XY</i>
$ svn copy https://llvm.org/svn/llvm-project/llvm-gcc-4.2/trunk \
https://llvm.org/svn/llvm-project/llvm-gcc-4.2/branches/release_<i>XY</i>
$ svn copy https://llvm.org/svn/llvm-project/test-suite/trunk \
https://llvm.org/svn/llvm-project/test-suite/branches/release_<i>XY</i>
$ svn copy https://llvm.org/svn/llvm-project/cfe/trunk \
https://llvm.org/svn/llvm-project/cfe/branches/release_<i>XY</i>
Converted to "svn" and reformatted. llvm-svn: 40416
2007-07-23 12:41:42 +08:00
</pre>
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
</div></li>
First pass over Reid's document. Changed the order of operations so that more of the fine tuning is performed in the release branch. This should free up mainline sooner to resume development. Removed information on the special release Makefile targets as I've never used them for a release; Tanya is investigating their integration, and they can be re-added if she uses them. Added an outline for building the LLVM GCC binary distributions. I will be filling that section out later (but before the 1.7 release). llvm-svn: 27595
2006-04-12 04:24:28 +08:00
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
<li><p>Advise developers that they may now check their patches into the
Subversion tree again.</p></li>
<li><p>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>
Converted to "svn" and reformatted. llvm-svn: 40416
2007-07-23 12:41:42 +08:00
<div class="doc_code">
<pre>
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
$ svn co https://llvm.org/svn/llvm-project/llvm/branches/release_<i>XY</i> llvm-<i>X.Y</i>
$ svn co https://llvm.org/svn/llvm-project/llvm-gcc-4.2/branches/release_<i>XY</i> llvm-gcc-4.2-<i>X.Y</i>
$ svn co https://llvm.org/svn/llvm-project/test-suite/branches/release_<i>XY</i> test-suite-<i>X.Y</i>
$ svn co https://llvm.org/svn/llvm-project/cfe/branches/release_<i>XY</i> clang-<i>X.Y</i>
Converted to "svn" and reformatted. llvm-svn: 40416
2007-07-23 12:41:42 +08:00
</pre>
Fix some validation errors. llvm-svn: 40417
2007-07-23 12:44:02 +08:00
</div></li>
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
</ol>
Update how to release document. Add release version to getting started guide. llvm-svn: 42454
2007-09-29 06:50:54 +08:00
A very early, rough draft of a guide to making public releases for LLVM. This document will detail the steps needed for making a quality release of LLVM that ensures the release functions and is of high quality. llvm-svn: 26978
2006-03-23 14:45:42 +08:00
</div>
Adding notes from release experience. llvm-svn: 29591
2006-08-10 08:23:05 +08:00
<!-- ======================================================================= -->
First steps to document new release plan. llvm-svn: 79376
2009-08-19 06:33:28 +08:00
<div class="doc_subsubsection"><a name="verchanges">Update LLVM Version</a></div>
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
Adding notes from release experience. llvm-svn: 29591
2006-08-10 08:23:05 +08:00
<div class="doc_text">
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
<p>After creating the LLVM release branch, update the release branches'
<tt>autoconf</tt> and <tt>configure.ac</tt> versions from '<tt>X.Ysvn</tt>'
to '<tt>X.Y</tt>'. Update it on mainline as well to be the next version
('<tt>X.Y+1svn</tt>'). Regenerate the configure scripts for both
<tt>llvm</tt> and the <tt>test-suite</tt>.</p>
<p>In addition, the version numbers of all the Bugzilla components must be
updated for the next release.</p>
Adding notes from release experience. llvm-svn: 29591
2006-08-10 08:23:05 +08:00
</div>
Update how to release document. Add release version to getting started guide. llvm-svn: 42454
2007-09-29 06:50:54 +08:00
<!-- ======================================================================= -->
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
<div class="doc_subsubsection"><a name="dist">Build the LLVM Release Candidates</a></div>
Update how to release document. Add release version to getting started guide. llvm-svn: 42454
2007-09-29 06:50:54 +08:00
<div class="doc_text">
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
<p>Create release candidates for <tt>llvm</tt>, <tt>llvm-gcc</tt>,
<tt>clang</tt>, and the LLVM <tt>test-suite</tt> by tagging the branch with
the respective release candidate number. For instance, to create <b>Release
Candidate 1</b> you would issue the following commands:</p>
Update how to release document. Add release version to getting started guide. llvm-svn: 42454
2007-09-29 06:50:54 +08:00
<div class="doc_code">
<pre>
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
$ svn mkdir https://llvm.org/svn/llvm-project/llvm/tags/RELEASE_<i>XY</i>
$ svn copy https://llvm.org/svn/llvm-project/llvm/branches/release_<i>XY</i> \
Fix tagging name. llvm-svn: 127154
2011-03-07 15:37:12 +08:00
https://llvm.org/svn/llvm-project/llvm/tags/RELEASE_<i>XY</i>/rc1
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
$ svn mkdir https://llvm.org/svn/llvm-project/llvm-gcc-4.2/tags/RELEASE_<i>XY</i>
$ svn copy https://llvm.org/svn/llvm-project/llvm-gcc-4.2/branches/release_<i>XY</i> \
Fix tagging name. llvm-svn: 127154
2011-03-07 15:37:12 +08:00
https://llvm.org/svn/llvm-project/llvm-gcc-4.2/tags/RELEASE_<i>XY</i>/rc1
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
$ svn mkdir https://llvm.org/svn/llvm-project/test-suite/tags/RELEASE_<i>XY</i>
$ svn copy https://llvm.org/svn/llvm-project/test-suite/branches/release_<i>XY</i> \
Fix tagging name. llvm-svn: 127154
2011-03-07 15:37:12 +08:00
https://llvm.org/svn/llvm-project/test-suite/tags/RELEASE_<i>XY</i>/rc1
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
$ svn mkdir https://llvm.org/svn/llvm-project/cfe/tags/RELEASE_<i>XY</i>
$ svn copy https://llvm.org/svn/llvm-project/cfe/branches/release_<i>XY</i> \
Fix tagging name. llvm-svn: 127154
2011-03-07 15:37:12 +08:00
https://llvm.org/svn/llvm-project/cfe/tags/RELEASE_<i>XY</i>/rc1
Update how to release document. Add release version to getting started guide. llvm-svn: 42454
2007-09-29 06:50:54 +08:00
</pre>
</div>
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
<p>Similarly, <b>Release Candidate 2</b> would be named <tt>RC2</tt> and so
on. This keeps a permanent copy of the release candidate around for people to
export and build as they wish. The final released sources will be tagged in
the <tt>RELEASE_<i>XY</i></tt> directory as <tt>Final</tt>
(c.f. <a href="#tag">Tag the LLVM Final Release</a>).</p>
<p>The Release Manager may supply pre-packaged source tarballs for users. This
can be done with the following commands:</p>
<div class="doc_code">
<pre>
Fix tagging name. llvm-svn: 127154
2011-03-07 15:37:12 +08:00
$ svn export https://llvm.org/svn/llvm-project/llvm/tags/RELEASE_<i>XY</i>/rc1 llvm-<i>X.Y</i>rc1
$ svn export https://llvm.org/svn/llvm-project/llvm-gcc-4.2/tags/RELEASE_<i>XY</i>/rc1 llvm-gcc4.2-<i>X.Y</i>rc1
$ svn export https://llvm.org/svn/llvm-project/test-suite/tags/RELEASE_<i>XY</i>/rc1 llvm-test-<i>X.Y</i>rc1
$ svn export https://llvm.org/svn/llvm-project/cfe/tags/RELEASE_<i>XY</i>/rc1 clang-<i>X.Y</i>rc1
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
Remove redundant compression option. llvm-svn: 128267
2011-03-25 14:43:59 +08:00
$ tar -cvf - llvm-<i>X.Y</i>rc1 | gzip &gt; llvm-<i>X.Y</i>rc1.src.tar.gz
$ tar -cvf - llvm-test-<i>X.Y</i>rc1 | gzip &gt; llvm-test-<i>X.Y</i>rc1.src.tar.gz
$ tar -cvf - llvm-gcc4.2-<i>X.Y</i>rc1 | gzip &gt; llvm-gcc-4.2-<i>X.Y</i>rc1.src.tar.gz
$ tar -cvf - clang-<i>X.Y</i>rc1 | gzip &gt; clang-<i>X.Y</i>rc1.src.tar.gz
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
</pre>
</div>
Update how to release document. Add release version to getting started guide. llvm-svn: 42454
2007-09-29 06:50:54 +08:00
</div>
A very early, rough draft of a guide to making public releases for LLVM. This document will detail the steps needed for making a quality release of LLVM that ensures the release functions and is of high quality. llvm-svn: 26978
2006-03-23 14:45:42 +08:00
<!-- ======================================================================= -->
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
<div class="doc_subsection"><a name="release-build">Building the Release</a></div>
First steps to document new release plan. llvm-svn: 79376
2009-08-19 06:33:28 +08:00
<div class="doc_text">
Update release document with more details. llvm-svn: 79818
2009-08-23 12:36:30 +08:00
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
<p>The builds of <tt>llvm</tt>, <tt>llvm-gcc</tt>, and <tt>clang</tt>
<em>must</em> be free of errors and warnings in Debug, Release+Asserts, and
Release builds. If all builds are clean, then the release passes Build
Qualification.</p>
<p>The <tt>make</tt> options for building the different modes:</p>
<table>
<tr><th>Mode</th><th>Options</th></tr>
<tr align="left"><td>Debug</td><td><tt>ENABLE_OPTIMIZED=0</tt></td></tr>
<tr align="left"><td>Release+Asserts</td><td><tt>ENABLE_OPTIMIZED=1</tt></td></tr>
<tr align="left"><td>Release</td><td><tt>ENABLE_OPTIMIZED=1 DISABLE_ASSERTIONS=1</tt></td></tr>
</table>
First steps to document new release plan. llvm-svn: 79376
2009-08-19 06:33:28 +08:00
</div>
<!-- ======================================================================= -->
<div class="doc_subsubsection"><a name="build">Build LLVM</a></div>
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
A very early, rough draft of a guide to making public releases for LLVM. This document will detail the steps needed for making a quality release of LLVM that ensures the release functions and is of high quality. llvm-svn: 26978
2006-03-23 14:45:42 +08:00
<div class="doc_text">
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
<p>Build <tt>Debug</tt>, <tt>Release+Asserts</tt>, and <tt>Release</tt> versions
of <tt>llvm</tt> on all supported platforms. Directions to build
<tt>llvm</tt> are
<a href="http://llvm.org/docs/GettingStarted.html#quickstart">here</a>.</p>
Update how to release document. Add release version to getting started guide. llvm-svn: 42454
2007-09-29 06:50:54 +08:00
</div>
First pass over Reid's document. Changed the order of operations so that more of the fine tuning is performed in the release branch. This should free up mainline sooner to resume development. Removed information on the special release Makefile targets as I've never used them for a release; Tanya is investigating their integration, and they can be re-added if she uses them. Added an outline for building the LLVM GCC binary distributions. I will be filling that section out later (but before the 1.7 release). llvm-svn: 27595
2006-04-12 04:24:28 +08:00
Update how to release document. Add release version to getting started guide. llvm-svn: 42454
2007-09-29 06:50:54 +08:00
<!-- ======================================================================= -->
First steps to document new release plan. llvm-svn: 79376
2009-08-19 06:33:28 +08:00
<div class="doc_subsubsection"><a name="llvmgccbin">Build the LLVM GCC Binary Distribution</a></div>
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
Update how to release document. Add release version to getting started guide. llvm-svn: 42454
2007-09-29 06:50:54 +08:00
<div class="doc_text">
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
<p>Creating the <tt>llvm-gcc</tt> binary distribution (Release/Optimized)
requires performing the following steps for each supported platform:</p>
<ol>
<li><p>Build the <tt>llvm-gcc</tt> front-end by following the directions in
the <tt>README.LLVM</tt> file. The front-end must be compiled with C, C++,
Objective-C (Mac only), Objective-C++ (Mac only), and Fortran
support.</p></li>
<li><p>Boostrapping must be enabled.</p></li>
<li><p>Be sure to build with <tt>LLVM_VERSION_INFO=X.Y</tt>, where <tt>X</tt>
is the major and <tt>Y</tt> is the minor release numbers.</p></li>
<li><p>Copy the installation directory to a directory named for the specific
target. For example on Red Hat Enterprise Linux, the directory would be
named <tt>llvm-gcc4.2-2.6-x86-linux-RHEL4</tt>. Archive and compress the
new directory.</p></li>
</ol>
A very early, rough draft of a guide to making public releases for LLVM. This document will detail the steps needed for making a quality release of LLVM that ensures the release functions and is of high quality. llvm-svn: 26978
2006-03-23 14:45:42 +08:00
</div>
<!-- ======================================================================= -->
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
<div class="doc_subsubsection"><a name="clangbin">Build Clang Binary Distribution</a></div>
A very early, rough draft of a guide to making public releases for LLVM. This document will detail the steps needed for making a quality release of LLVM that ensures the release functions and is of high quality. llvm-svn: 26978
2006-03-23 14:45:42 +08:00
<div class="doc_text">
First pass over Reid's document. Changed the order of operations so that more of the fine tuning is performed in the release branch. This should free up mainline sooner to resume development. Removed information on the special release Makefile targets as I've never used them for a release; Tanya is investigating their integration, and they can be re-added if she uses them. Added an outline for building the LLVM GCC binary distributions. I will be filling that section out later (but before the 1.7 release). llvm-svn: 27595
2006-04-12 04:24:28 +08:00
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
<p>Creating the <tt>clang</tt> binary distribution
(Debug/Release+Asserts/Release) requires performing the following steps for
each supported platform:</p>
<ol>
<li>Build clang according to the directions
<a href="http://clang.llvm.org/get_started.html">here</a>.</li>
<li>Build both a debug and release version of clang. The binary will be the
release build.</lI>
<li>Package <tt>clang</tt> (details to follow).</li>
</ol>
First steps to document new release plan. llvm-svn: 79376
2009-08-19 06:33:28 +08:00
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
</div>
First steps to document new release plan. llvm-svn: 79376
2009-08-19 06:33:28 +08:00
<!-- ======================================================================= -->
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
<div class="doc_subsubsection"><a name="target-build">Target Specific Build Details</a></div>
First steps to document new release plan. llvm-svn: 79376
2009-08-19 06:33:28 +08:00
<div class="doc_text">
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
<p>The table below specifies which compilers are used for each Arch/OS
combination when qualifying the build of <tt>llvm</tt>, <tt>llvm-gcc</tt>,
and <tt>clang</tt>.</p>
<table>
Update the release process some more. Lots of good details now. llvm-svn: 79488
2009-08-20 07:07:37 +08:00
<tr><th>Architecture</th><th>OS</th><th>compiler</th></tr>
<tr><td>x86-32</td><td>Mac OS 10.5</td><td>gcc 4.0.1</td></tr>
<tr><td>x86-32</td><td>Linux</td><td>gcc 4.2.X, gcc 4.3.X</td></tr>
Update release document with more details. llvm-svn: 79818
2009-08-23 12:36:30 +08:00
<tr><td>x86-32</td><td>FreeBSD</td><td>gcc 4.2.X</td></tr>
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
<tr><td>x86-32</td><td>mingw</td><td>gcc 3.4.5</td></tr>
Update the release process some more. Lots of good details now. llvm-svn: 79488
2009-08-20 07:07:37 +08:00
<tr><td>x86-64</td><td>Mac OS 10.5</td><td>gcc 4.0.1</td></tr>
<tr><td>x86-64</td><td>Linux</td><td>gcc 4.2.X, gcc 4.3.X</td></tr>
Update release document with more details. llvm-svn: 79818
2009-08-23 12:36:30 +08:00
<tr><td>x86-64</td><td>FreeBSD</td><td>gcc 4.2.X</td></tr>
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
</table>
Update the release process some more. Lots of good details now. llvm-svn: 79488
2009-08-20 07:07:37 +08:00
A very early, rough draft of a guide to making public releases for LLVM. This document will detail the steps needed for making a quality release of LLVM that ensures the release functions and is of high quality. llvm-svn: 26978
2006-03-23 14:45:42 +08:00
</div>
<!-- ======================================================================= -->
First steps to document new release plan. llvm-svn: 79376
2009-08-19 06:33:28 +08:00
<div class="doc_subsection"><a name="release-qualify">
Building the Release</a></div>
<div class="doc_text">
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
<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><b>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</b></p>
</div>
First steps to document new release plan. llvm-svn: 79376
2009-08-19 06:33:28 +08:00
<!-- ======================================================================= -->
<div class="doc_subsubsection"><a name="llvm-qualify">Qualify LLVM</a></div>
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
A very early, rough draft of a guide to making public releases for LLVM. This document will detail the steps needed for making a quality release of LLVM that ensures the release functions and is of high quality. llvm-svn: 26978
2006-03-23 14:45:42 +08:00
<div class="doc_text">
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
<p>LLVM is qualified when it has a clean test run without a front-end. And it
has no regressions when using either <tt>llvm-gcc</tt> or <tt>clang</tt> with
the <tt>test-suite</tt> from the previous release.</p>
Add a section on how to build an RPM package as an optional release activity. llvm-svn: 29719
2006-08-16 08:54:50 +08:00
</div>
A very early, rough draft of a guide to making public releases for LLVM. This document will detail the steps needed for making a quality release of LLVM that ensures the release functions and is of high quality. llvm-svn: 26978
2006-03-23 14:45:42 +08:00
Add a section on how to build an RPM package as an optional release activity. llvm-svn: 29719
2006-08-16 08:54:50 +08:00
<!-- ======================================================================= -->
First steps to document new release plan. llvm-svn: 79376
2009-08-19 06:33:28 +08:00
<div class="doc_subsubsection"><a name="llvmgcc-qualify">Qualify LLVM-GCC</a></div>
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
Add a section on how to build an RPM package as an optional release activity. llvm-svn: 29719
2006-08-16 08:54:50 +08:00
<div class="doc_text">
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
<p><tt>LLVM-GCC</tt> is qualified when front-end specific tests in the
<tt>llvm</tt> regression test suite all pass and there are no regressions in
the <tt>test-suite</tt>.</p>
<p>We do not use the GCC DejaGNU test suite as release criteria.</p>
First steps to document new release plan. llvm-svn: 79376
2009-08-19 06:33:28 +08:00
</div>
Converted to "svn" and reformatted. llvm-svn: 40416
2007-07-23 12:41:42 +08:00
First steps to document new release plan. llvm-svn: 79376
2009-08-19 06:33:28 +08:00
<!-- ======================================================================= -->
<div class="doc_subsubsection"><a name="clang-qualify">Qualify Clang</a></div>
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
First steps to document new release plan. llvm-svn: 79376
2009-08-19 06:33:28 +08:00
<div class="doc_text">
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
<p><tt>Clang</tt> is qualified when front-end specific tests in the
<tt>llvm</tt> dejagnu test suite all pass, clang's own test suite passes
cleanly, and there are no regressions in the <tt>test-suite</tt>.</p>
Converted to "svn" and reformatted. llvm-svn: 40416
2007-07-23 12:41:42 +08:00
</div>
First steps to document new release plan. llvm-svn: 79376
2009-08-19 06:33:28 +08:00
<!-- ======================================================================= -->
<div class="doc_subsubsection"><a name="targets">Specific Target
Qualification Details</a></div>
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
First steps to document new release plan. llvm-svn: 79376
2009-08-19 06:33:28 +08:00
<div class="doc_text">
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
<table>
<tr><th>Architecture</th><th>OS</th><th>llvm-gcc baseline</th><th>clang baseline</th><th>tests</th></tr>
Update to note that clang has a baseline now. Dropping x86-32 for MacOS. llvm-svn: 100447
2010-04-06 02:35:37 +08:00
<tr><td>x86-32</td><td>Linux</td><td>last release</td><td>last release</td><td>llvm dejagnu, clang tests, test-suite (including spec)</td></tr>
<tr><td>x86-32</td><td>FreeBSD</td><td>none</td><td>last release</td><td>llvm dejagnu, clang tests, test-suite</td></tr>
Update the release process some more. Lots of good details now. llvm-svn: 79488
2009-08-20 07:07:37 +08:00
<tr><td>x86-32</td><td>mingw</td><td>last release</td><td>none</td><td>QT</td></tr>
Update to note that clang has a baseline now. Dropping x86-32 for MacOS. llvm-svn: 100447
2010-04-06 02:35:37 +08:00
<tr><td>x86-64</td><td>Mac OS 10.X</td><td>last release</td><td>last release</td><td>llvm dejagnu, clang tests, test-suite (including spec)</td></tr>
<tr><td>x86-64</td><td>Linux</td><td>last release</td><td>last release</td><td>llvm dejagnu, clang tests, test-suite (including spec)</td></tr>
<tr><td>x86-64</td><td>FreeBSD</td><td>none</td><td>last release</td><td>llvm dejagnu, clang tests, test-suite</td></tr>
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
</table>
First pass over Reid's document. Changed the order of operations so that more of the fine tuning is performed in the release branch. This should free up mainline sooner to resume development. Removed information on the special release Makefile targets as I've never used them for a release; Tanya is investigating their integration, and they can be re-added if she uses them. Added an outline for building the LLVM GCC binary distributions. I will be filling that section out later (but before the 1.7 release). llvm-svn: 27595
2006-04-12 04:24:28 +08:00
</div>
<!-- ======================================================================= -->
First steps to document new release plan. llvm-svn: 79376
2009-08-19 06:33:28 +08:00
<div class="doc_subsection"><a name="commTest">Community Testing</a></div>
First pass over Reid's document. Changed the order of operations so that more of the fine tuning is performed in the release branch. This should free up mainline sooner to resume development. Removed information on the special release Makefile targets as I've never used them for a release; Tanya is investigating their integration, and they can be re-added if she uses them. Added an outline for building the LLVM GCC binary distributions. I will be filling that section out later (but before the 1.7 release). llvm-svn: 27595
2006-04-12 04:24:28 +08:00
<div class="doc_text">
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
<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. Ask that all LLVM developers test the release in 2 ways:</p>
<ol>
<li>Download <tt>llvm-<i>X.Y</i></tt>, <tt>llvm-test-<i>X.Y</i></tt>, and the
appropriate <tt>llvm-gcc</tt> and/or <tt>clang</tt> binary. Build
LLVM. Run <tt>make check</tt> and the full LLVM test suite (<tt>make
TEST=nightly report</tt>).</li>
<li>Download <tt>llvm-<i>X.Y</i></tt>, <tt>llvm-test-<i>X.Y</i></tt>, and the
<tt>llvm-gcc</tt> and/or <tt>clang</tt> source. Compile everything. Run
<tt>make check</tt> and the full LLVM test suite (<tt>make TEST=nightly
report</tt>).</li>
</ol>
<p>Ask LLVM developers to submit the test suite report and <tt>make check</tt>
results to the list. Verify that there are no regressions from the previous
release. The results are not used to qualify a release, but to spot other
potential problems. For unsupported targets, verify that <tt>make check</tt>
is at least clean.</p>
Update how to release document. Add release version to getting started guide. llvm-svn: 42454
2007-09-29 06:50:54 +08:00
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
<p>During the first round of testing, all regressions must be fixed before the
second release candidate is tagged.</p>
Update how to release document. Add release version to getting started guide. llvm-svn: 42454
2007-09-29 06:50:54 +08:00
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
<p>If this is the second round of testing, the testing is only to ensure that
bug fixes previously merged in have not created new major problems. <i>This
is not the time to solve additional and unrelated bugs!</i> If no patches are
merged in, the release is determined to be ready and the release manager may
move onto the next stage.</p>
Update how to release document. Add release version to getting started guide. llvm-svn: 42454
2007-09-29 06:50:54 +08:00
</div>
First pass over Reid's document. Changed the order of operations so that more of the fine tuning is performed in the release branch. This should free up mainline sooner to resume development. Removed information on the special release Makefile targets as I've never used them for a release; Tanya is investigating their integration, and they can be re-added if she uses them. Added an outline for building the LLVM GCC binary distributions. I will be filling that section out later (but before the 1.7 release). llvm-svn: 27595
2006-04-12 04:24:28 +08:00
First steps to document new release plan. llvm-svn: 79376
2009-08-19 06:33:28 +08:00
<!-- ======================================================================= -->
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
<div class="doc_subsection"><a name="release-patch">Release Patch Rules</a></div>
First steps to document new release plan. llvm-svn: 79376
2009-08-19 06:33:28 +08:00
<div class="doc_text">
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
<p>Below are the rules regarding patching the release branch:</p>
<ol>
<li><p>Patches applied to the release branch may only be applied by the
release manager.</p></li>
<li><p>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.</p></li>
<li><p>During the remaining rounds of testing, only patches that fix critical
regressions may be applied.</p></li>
</ol>
</div>
First steps to document new release plan. llvm-svn: 79376
2009-08-19 06:33:28 +08:00
<!-- ======================================================================= -->
<div class="doc_subsection"><a name="release-final">Release Final Tasks
</a></div>
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
First steps to document new release plan. llvm-svn: 79376
2009-08-19 06:33:28 +08:00
<div class="doc_text">
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
<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>
First steps to document new release plan. llvm-svn: 79376
2009-08-19 06:33:28 +08:00
</div>
First pass over Reid's document. Changed the order of operations so that more of the fine tuning is performed in the release branch. This should free up mainline sooner to resume development. Removed information on the special release Makefile targets as I've never used them for a release; Tanya is investigating their integration, and they can be re-added if she uses them. Added an outline for building the LLVM GCC binary distributions. I will be filling that section out later (but before the 1.7 release). llvm-svn: 27595
2006-04-12 04:24:28 +08:00
Update the release process some more. Lots of good details now. llvm-svn: 79488
2009-08-20 07:07:37 +08:00
<!-- ======================================================================= -->
<div class="doc_subsubsection"><a name="updocs">Update Documentation</a></div>
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
Update the release process some more. Lots of good details now. llvm-svn: 79488
2009-08-20 07:07:37 +08:00
<div class="doc_text">
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
<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 avaiable from
Subversion and changes in basic system requirements. Merge both changes from
mainline into the release branch.</p>
Update the release process some more. Lots of good details now. llvm-svn: 79488
2009-08-20 07:07:37 +08:00
</div>
Update how to release document. Add release version to getting started guide. llvm-svn: 42454
2007-09-29 06:50:54 +08:00
<!-- ======================================================================= -->
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
<div class="doc_subsubsection"><a name="tag">Tag the LLVM Final Release</a></div>
Update how to release document. Add release version to getting started guide. llvm-svn: 42454
2007-09-29 06:50:54 +08:00
<div class="doc_text">
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
<p>Tag the final release sources using the following procedure:</p>
Update how to release document. Add release version to getting started guide. llvm-svn: 42454
2007-09-29 06:50:54 +08:00
<div class="doc_code">
<pre>
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
$ svn copy https://llvm.org/svn/llvm-project/llvm/branches/release_XY \
https://llvm.org/svn/llvm-project/llvm/tags/RELEASE_<i>XY</i>/Final
$ svn copy https://llvm.org/svn/llvm-project/llvm-gcc-4.2/branches/release_XY \
https://llvm.org/svn/llvm-project/llvm-gcc-4.2/tags/RELEASE_<i>XY</i>/Final
$ svn copy https://llvm.org/svn/llvm-project/test-suite/branches/release_XY \
https://llvm.org/svn/llvm-project/test-suite/tags/RELEASE_<i>XY</i>/Final
$ svn copy https://llvm.org/svn/llvm-project/cfe/branches/release_XY \
https://llvm.org/svn/llvm-project/cfe/tags/RELEASE_<i>XY</i>/Final
Update how to release document. Add release version to getting started guide. llvm-svn: 42454
2007-09-29 06:50:54 +08:00
</pre>
</div>
Update the release process some more. Lots of good details now. llvm-svn: 79488
2009-08-20 07:07:37 +08:00
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
</div>
A very early, rough draft of a guide to making public releases for LLVM. This document will detail the steps needed for making a quality release of LLVM that ensures the release functions and is of high quality. llvm-svn: 26978
2006-03-23 14:45:42 +08:00
Update how to release document. Add release version to getting started guide. llvm-svn: 42454
2007-09-29 06:50:54 +08:00
<!-- ======================================================================= -->
<div class="doc_subsection"><a name="updemo">Update the LLVM Demo Page</a></div>
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
Update how to release document. Add release version to getting started guide. llvm-svn: 42454
2007-09-29 06:50:54 +08:00
<div class="doc_text">
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
<p>The LLVM demo page must be updated to use the new release. This consists of
using the new <tt>llvm-gcc</tt> binary and building LLVM.</p>
Update how to release document. Add release version to getting started guide. llvm-svn: 42454
2007-09-29 06:50:54 +08:00
</div>
Adding notes from release experience. llvm-svn: 29591
2006-08-10 08:23:05 +08:00
<!-- ======================================================================= -->
First steps to document new release plan. llvm-svn: 79376
2009-08-19 06:33:28 +08:00
<div class="doc_subsubsection"><a name="webupdates">Update the LLVM Website</a></div>
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
Adding notes from release experience. llvm-svn: 29591
2006-08-10 08:23:05 +08:00
<div class="doc_text">
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
<p>The website must be updated before the release announcement is sent out. Here
is what to do:</p>
<ol>
<li>Check out the <tt>www</tt> module from Subversion.</li>
<li>Create a new subdirectory <tt>X.Y</tt> in the releases directory.</li>
<li>Commit the <tt>llvm</tt>, <tt>test-suite</tt>, <tt>llvm-gcc</tt> source,
<tt>clang source</tt>, <tt>clang binaries</tt>, and <tt>llvm-gcc</tt>
binaries in this new directory.</li>
<li>Copy and commit the <tt>llvm/docs</tt> and <tt>LICENSE.txt</tt> files
into this new directory. The docs should be built with
<tt>BUILD_FOR_WEBSITE=1</tt>.</li>
<li>Commit the <tt>index.html</tt> to the <tt>release/X.Y</tt> directory to
redirect (use from previous release.</li>
<li>Update the <tt>releases/download.html</tt> file with the new release.</li>
<li>Update the <tt>releases/index.html</tt> with the new release and link to
release documentation.</li>
<li>Finally, update the main page (<tt>index.html</tt> and sidebar) to point
to the new release and release announcement. Make sure this all gets
committed back into Subversion.</li>
</ol>
Adding notes from release experience. llvm-svn: 29591
2006-08-10 08:23:05 +08:00
</div>
Update how to release document. Add release version to getting started guide. llvm-svn: 42454
2007-09-29 06:50:54 +08:00
<!-- ======================================================================= -->
First steps to document new release plan. llvm-svn: 79376
2009-08-19 06:33:28 +08:00
<div class="doc_subsubsection"><a name="announce">Announce the Release</a></div>
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
A very early, rough draft of a guide to making public releases for LLVM. This document will detail the steps needed for making a quality release of LLVM that ensures the release functions and is of high quality. llvm-svn: 26978
2006-03-23 14:45:42 +08:00
<div class="doc_text">
Update the documentation on "How to Release LLVM". It lays out a new way of tagging and branching for the release. I will update this more throughout the 2.9 release process. llvm-svn: 126604
2011-02-28 09:10:44 +08:00
<p>Have Chris send out the release announcement when everything is finished.</p>
A very early, rough draft of a guide to making public releases for LLVM. This document will detail the steps needed for making a quality release of LLVM that ensures the release functions and is of high quality. llvm-svn: 26978
2006-03-23 14:45:42 +08:00
</div>
<!-- *********************************************************************** -->
<hr>
<address>
<a href="http://jigsaw.w3.org/css-validator/check/referer"><img
Global replace of yellow W3C "valid HTML/CSS" icons with blue ones. llvm-svn: 60880
2008-12-12 01:34:48 +08:00
src="http://jigsaw.w3.org/css-validator/images/vcss-blue" alt="Valid CSS"></a>
A very early, rough draft of a guide to making public releases for LLVM. This document will detail the steps needed for making a quality release of LLVM that ensures the release functions and is of high quality. llvm-svn: 26978
2006-03-23 14:45:42 +08:00
<a href="http://validator.w3.org/check/referer"><img
Removed warnings from HTML 4.01 validator: trailing slashes in <br> and <img> tags are not needed in HTML, only XML. llvm-svn: 60885
2008-12-12 02:23:24 +08:00
src="http://www.w3.org/Icons/valid-html401-blue" alt="Valid HTML 4.01"></a>
A very early, rough draft of a guide to making public releases for LLVM. This document will detail the steps needed for making a quality release of LLVM that ensures the release functions and is of high quality. llvm-svn: 26978
2006-03-23 14:45:42 +08:00
<a href="http://llvm.cs.uiuc.edu">The LLVM Compiler Infrastructure</a>
Removed warnings from HTML 4.01 validator: trailing slashes in <br> and <img> tags are not needed in HTML, only XML. llvm-svn: 60885
2008-12-12 02:23:24 +08:00
<br>
A very early, rough draft of a guide to making public releases for LLVM. This document will detail the steps needed for making a quality release of LLVM that ensures the release functions and is of high quality. llvm-svn: 26978
2006-03-23 14:45:42 +08:00
Last modified: $Date$
</address>
</body>
</html>