From 405ce8db96f7a3a5a4c3da0f71d2ca54d30316f0 Mon Sep 17 00:00:00 2001 From: Tanya Lattner Date: Sun, 23 Aug 2009 04:36:30 +0000 Subject: Update release document with more details. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@79818 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/HowToReleaseLLVM.html | 36 ++++++++++++++++++++++++------------ 1 file changed, 24 insertions(+), 12 deletions(-) (limited to 'docs') diff --git a/docs/HowToReleaseLLVM.html b/docs/HowToReleaseLLVM.html index a5763000e6..70406099d0 100644 --- a/docs/HowToReleaseLLVM.html +++ b/docs/HowToReleaseLLVM.html @@ -202,7 +202,7 @@ svn export https://llvm.org/svn/llvm-project/cfe/branches/release_XX clan tar -czvf - llvm-X.X | gzip > llvm-X.X.tar.gz tar -czvf - llvm-test-X.X | gzip > llvm-test-X.X.tar.gz tar -czvf - llvm-gcc4.2-X.X.source | gzip > llvm-gcc-4.2-X.X.source.tar.gz -tar -czvf - clang-X.X.source | gzip > clang-X.X.source.tar.gz +tar -czvf - clang-X.X | gzip > clang-X.X.tar.gz @@ -213,16 +213,22 @@ Building the Release
The build of llvm, llvm-gcc, and clang must be free -of errors and warnings in both debug and release modes. If both debug and -release builds are clean, then the release passes build qualification. +of errors and warnings in both debug, release, and release-asserts builds. +If all builds are clean, then the release passes build qualification. + +
    +
  1. debug: ENABLE_OPTIMIZED=0
    2. +
  2. release: ENABLE_OPTIMIZED=1
    3. +
  3. release-asserts: ENABLE_OPTIMIZED=1 DISABLE_ASSERTIONS=1
    4. +
Build LLVM

- Build both debug and release (optimized) versions of LLVM on all supported - platforms. Direction to build llvm are + Build both debug, release (optimized), and release-asserts versions of + LLVM on all supported platforms. Direction to build llvm are here.

@@ -239,8 +245,9 @@ release builds are clean, then the release passes build qualification.
  • Build the LLVM GCC front-end by following the directions in the README.LLVM file. The frontend must be compiled with c, c++, objc (mac only), - objc++ (mac only) and fortran support. - Be sure to build with LLVM_VERSION_INFO=X.X, where X is the major and + objc++ (mac only) and fortran support.
    • +
  • Please boostrap as well.
    • +
  • Be sure to build with LLVM_VERSION_INFO=X.X, where X is the major and minor release numbers.
    • @@ -257,7 +264,7 @@ release builds are clean, then the release passes build qualification. Binary Distribution

    - Creating the Clang binary distribution (release/optimized) requires + Creating the Clang binary distribution (debug/release/release-asserts) requires performing the following steps for each supported platform:

    @@ -291,11 +298,11 @@ Details
    ArchitectureOScompiler x86-32Mac OS 10.5gcc 4.0.1 x86-32Linuxgcc 4.2.X, gcc 4.3.X - x86-32FreeBSDgcc ? - x86-32mingwgcc ? + x86-32FreeBSDgcc 4.2.X + x86-32mingwgcc 3.4.5 x86-64Mac OS 10.5gcc 4.0.1 x86-64Linuxgcc 4.2.X, gcc 4.3.X - x86-64FreeBSDgcc? + x86-64FreeBSDgcc 4.2.X

    @@ -311,7 +318,12 @@ Building the Release A release is qualified when it has no regressions from the previous release (or baseline). Regressions are related to correctness only and not performance at this time. Regressions are new failures in the set of tests that - are used to qualify each product and do not include anything not in the list. + are used to qualify each product and only include things on the list. + Ultimately, there is no end to the number of possible bugs in a release. 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 things, + but this are things that must be satisfied before a release can go out -- cgit v1.2.3