$include_dir="/home/hyper-archives/boost-commit/include"; include("$include_dir/msg-header.inc") ?>
From: bdawes_at_[hidden]
Date: 2008-07-23 11:43:01
Author: bemandawes
Date: 2008-07-23 11:43:01 EDT (Wed, 23 Jul 2008)
New Revision: 47723
URL: http://svn.boost.org/trac/boost/changeset/47723
Log:
Reorganize and update
Text files modified: 
   website/public_html/beta/development/testing.html |   187 +++++++++++++-------------------------- 
   1 files changed, 64 insertions(+), 123 deletions(-)
Modified: website/public_html/beta/development/testing.html
==============================================================================
--- website/public_html/beta/development/testing.html	(original)
+++ website/public_html/beta/development/testing.html	2008-07-23 11:43:01 EDT (Wed, 23 Jul 2008)
@@ -35,73 +35,25 @@
               <h1>Testing</h1>
             </div>
 
-            <div class="section-body">
+            <div class="section-body" style="width: 796; height: 1802">
               <ul class="toc">
-                <li>Introduction</li>
 
-                <li>Regression Testing</li>
+                <li>Regression Tests</li>
 
-                <li>Smoke Testing</li>
-
-                <li>Inspection</li>
+                <li>Inspection Reports</li>
 
                 <li>Release Branch Snapshots</li>
 
-                <li>Acknowledgements</li>
+                <li><a href="#Acknowledgements"><a href="#Introduction">More 
+                about regression tests</a></a>Acknowledgements</li>
               </ul>
 
-              <h2><a name="Introduction" id=
-              "Introduction"></a>Introduction</h2>
-
-              <p>Will all Boost libraries work with your compiler? 
-              Unfortunately, the answer is "it depends". See the <a href=
-              "#RegressionTesting">regression testing results</a> to see
-              exactly what works and what doesn't.</p>
-
-              <p>Boost libraries rely on modern C++ features such as
-              templates and the C++ Standard Library.  Most modern
-              compilers support those major features fairly well. But even
-              today, years after the adoption of the C++ Standard, some
-              compilers still don't support important minor features like
-              partial template specialization.</p>
-
-              <p>Boost library authors often expend a great deal of effort
-              trying to work around compiler deficiencies. 
-              Nevertheless, some libraries will not compile at all with
-              certain compilers or may have crippled functionality. 
-              Even if the current release of a compiler supports a boost
-              library, older versions of the compiler may not work
-              properly.</p>
-
-              <p>Boost releases are run through regression tests which
-              automatically generates compiler status tables for various
-              platforms. Unless otherwise indicated, the C++ Standard Library
-              implementation is the one shipped with the compiler.</p>
-
-              <h3>Warnings:</h3>
-
-              <ul>
-                <li>These tables are not a good indication of a particular
-                compiler's compliance with the C++ Standard.  The Boost
-                libraries often contain workarounds which mask compiler
-                deficiencies.</li>
-
-                <li>Some regression tests are run only occasionally, and so
-                are relatively out-of-date.  Check the date for each
-                table.</li>
-              </ul>
-
-              <p>The development code is being updated several times a day,
-              so it may contain bug fixes, compiler workarounds, new
-              features, and even whole new libraries. It may be unstable,
-              however.</p>
-
               <h2><a name="RegressionTesting" id=
-              "RegressionTesting"></a>Regression Testing</h2>
+              "RegressionTesting"></a>Regression Tests</h2>
 
-              <p>A group of volunteers donate CPU cycles, and large amounts
-              of disk space, to collectively produce the regression testing
-              result tables. Various Boost releases are tested for the
+              <p>A group of volunteers donate CPU cycles and large amounts
+              of disk space to collectively produce the regression testing
+              result tables. Various Boost repository versions are tested for the
               benefit of library developers and interested users:</p>
 
               <table summary="Regression Results">
@@ -114,10 +66,6 @@
                 </tr>
 
                 <tr>
-                  <th class="c1" colspan="4">Local Results</th>
-                </tr>
-
-                <tr>
                   <td>Main trunk</td>
 
                   <td></td>
@@ -157,75 +105,35 @@
                   Issues</a></td>
                 </tr>
 
-                <tr>
-                  <th class="c1" colspan="4">Alternate Results @ <a href=
-                  "http://engineering.meta-comm.com/boost.aspx">MetaCommunications</a></th>
-                </tr>
-
-                <tr>
-                  <td>Main trunk</td>
-
-                  <td></td>
-
-                  <td><a href=
-                  "http://engineering.meta-comm.com/boost-regression/trunk/developer/summary.html">
-                  Summary</a></td>
-
-                  <td><a href=
-                  "http://engineering.meta-comm.com/boost-regression/trunk/developer/issues.html">
-                  Unresolved Issues</a></td>
-                </tr>
-              </table>
+                </table>
 
-              <h2><a name="SmokeTesting" id="SmokeTesting"></a>Smoke
-              Testing</h2>
+              <h2><a name="Inspection" id="Inspection"></a>Inspection Reports</h2>
 
-              <p>The full regression test reports give a broad and deep view
-              of how Boost libraries perform across many platforms and
-              compilers. But developers often need a quick snapshot of how
-              tests are doing on representative platforms and compilers. The
-              smoke tests check the repository at regular intervals and run
-              incremental tests if anything has changed. Test results may be
-              available as little as 5 minutes later, depending on the
-              platform and how many libraries were affected by changes. More
-              extensive changes take a couple of hours to test.</p>
+              <p>The Boost Subversion repository is inspected daily to detect
+              problems such as missing copyrights or licenses. The Boost Inspection
+              Report tells all!</p>
 
-              <table summary="Smoke Results">
+              <table summary="Regression Results">
                 <tr>
                   <th>Version</th>
 
-                  <th>Platform and Compiler</th>
                 </tr>
 
                 <tr>
-                  <td>Main Trunk</td>
+                  <td>Main trunk</td>
 
-                  <td><a href=
-                  "http://mysite.verizon.net/beman/bgd-win32-trunk-results.html">
-                  Windows (32-bit), Visual C++ 2005 SP1</a></td>
                 </tr>
 
                 <tr>
-                  <td>Main Trunk</td>
+                  <td>Release branch</td>
 
-                  <td><a href=
-                  "http://mysite.verizon.net/beman/bgd-linux-trunk-results.html">
-                  Ubuntu Linux (X86 32-bit), gcc-4.1.2</a></td>
                 </tr>
-              </table>
 
-              <h2><a name="Inspection" id="Inspection"></a>Inspection</h2>
-
-              <p>The Boost Subversion trunk is inspected daily to detect
-              problems such as missing copyrights or licenses. The <a href=
-              "http://mysite.verizon.net/beman/inspect.html">Boost Inspection
-              Report</a> tells all!</p>
+              </table>
 
               <h2><a name="Snapshots" id="Snapshots"></a>Release Branch
               Snapshots</h2>
 
-              <p> </p>
-
               <p><a href="http://boost.cowic.de/rc/">Release branch
               snapshots</a> are built on a daily basis. They are used for
               quality control checks on the release currently under
@@ -236,21 +144,60 @@
               <p>Because the snapshots represent work-in-process, they are
               not suitable for production use.</p>
 
-              <p>A <a href=
-              "http://boost.cowic.de/rc/inspect-snapshot.html">Boost
-              Inspection Report</a> is also run on the release branch
-              snapshot.</p>
-
               <p>The Subversion release branch can be checked out from
               http://svn.boost.org/svn/boost/branches/release.