diff mbox series

[pushed] wwwdocs: *: Remove unused buildstat pages

Message ID 20231015214241.B37BB33EB9@hamza.pair.com
State Unresolved
Headers
Series [pushed] wwwdocs: *: Remove unused buildstat pages |

Checks

Context Check Description
snail/gcc-patch-check warning Git am fail log

Commit Message

Gerald Pfeifer Oct. 15, 2023, 9:42 p.m. UTC 
  [ Release managers, heads-up for when you branch future releases! ]

For GCC 9 to GCC 13 the per-release series buildstat pages have not
been populated at all, so remove them and reference from the respective
main release pages.

Pushed.
Gerald
---
 htdocs/gcc-10/buildstat.html | 27 ---------------------------
 htdocs/gcc-10/index.html     |  3 ---
 htdocs/gcc-11/buildstat.html | 27 ---------------------------
 htdocs/gcc-11/index.html     |  3 ---
 htdocs/gcc-12/buildstat.html | 27 ---------------------------
 htdocs/gcc-12/index.html     |  3 ---
 htdocs/gcc-13/buildstat.html | 27 ---------------------------
 htdocs/gcc-13/index.html     |  3 ---
 htdocs/gcc-9/buildstat.html  | 27 ---------------------------
 htdocs/gcc-9/index.html      |  3 ---
 10 files changed, 150 deletions(-)
 delete mode 100644 htdocs/gcc-10/buildstat.html
 delete mode 100644 htdocs/gcc-11/buildstat.html
 delete mode 100644 htdocs/gcc-12/buildstat.html
 delete mode 100644 htdocs/gcc-13/buildstat.html
 delete mode 100644 htdocs/gcc-9/buildstat.html

Comments

Thomas Schwinge Nov. 20, 2023, 8:42 a.m. UTC | #1 
Hi!

On 2023-10-15T23:42:39+0200, Gerald Pfeifer <gerald@pfeifer.com> wrote:
> [ Release managers, heads-up for when you branch future releases! ]

> For GCC 9 to GCC 13 the per-release series buildstat pages have not
> been populated at all, so remove them and reference from the respective
> main release pages.

ACK; I had recently run into such an empty page, and wanted to suggest
the same.

We still need to update the docs some more.  Do we just remove all
references (and related text), and/or refer to the gcc-testresults
mailing list?

In wwwdocs:

    htdocs/branching.html:<li>Add <code>buildstat.html</code> and update the toplevel
    htdocs/branching.html:<code>buildstat.html</code> accordingly.</li>

    htdocs/faq.html:Reports of <a href="buildstat.html">successful builds</a>
    htdocs/faq.html-for several versions of GCC are also available at the web site.</p>

    htdocs/releasing.html-<li>For a new major release, ensure that the build status page is present
    htdocs/releasing.html:and add a link from the main <code>buildstat.html</code> page.</li>

In GCC:

    gcc/doc/install.texi-Lists of successful builds for released versions of GCC are
    gcc/doc/install.texi:available at @uref{https://gcc.gnu.org/buildstat.html}.
    gcc/doc/install.texi-These lists are updated as new information becomes available.

    gcc/doc/install.texi-Some of these archived results are linked from the build status lists
    gcc/doc/install.texi:at @uref{https://gcc.gnu.org/buildstat.html}, although not everyone who
    gcc/doc/install.texi-reports a successful build runs the testsuites and submits the results.

    gcc/doc/install.texi-If you are bootstrapping a released version of GCC then please
    gcc/doc/install.texi-quickly review the build status page for your release, available from
    gcc/doc/install.texi:@uref{https://gcc.gnu.org/buildstat.html}.

    libstdc++-v3/doc/xml/faq.xml-    the rapid development and near-legendary
    libstdc++-v3/doc/xml/faq.xml:    <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://gcc.gnu.org/buildstat.html">portability</link>
    libstdc++-v3/doc/xml/faq.xml-    that are the hallmarks of an open-source project are applied to libstdc++.

    libstdc++-v3/doc/xml/manual/test.xml-       Archives of test results for various versions and platforms are
    libstdc++-v3/doc/xml/manual/test.xml:       available on the GCC website in the <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://gcc.gnu.org/gcc-4.3/buildstat.html">build
    libstdc++-v3/doc/xml/manual/test.xml-       status</link> section of each individual release, and are also
    libstdc++-v3/doc/xml/manual/test.xml-       archived on a daily basis on the <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://gcc.gnu.org/ml/gcc-testresults/current">gcc-testresults</link>


Grüße
 Thomas


>  htdocs/gcc-10/buildstat.html | 27 ---------------------------
>  htdocs/gcc-10/index.html     |  3 ---
>  htdocs/gcc-11/buildstat.html | 27 ---------------------------
>  htdocs/gcc-11/index.html     |  3 ---
>  htdocs/gcc-12/buildstat.html | 27 ---------------------------
>  htdocs/gcc-12/index.html     |  3 ---
>  htdocs/gcc-13/buildstat.html | 27 ---------------------------
>  htdocs/gcc-13/index.html     |  3 ---
>  htdocs/gcc-9/buildstat.html  | 27 ---------------------------
>  htdocs/gcc-9/index.html      |  3 ---
>  10 files changed, 150 deletions(-)
>  delete mode 100644 htdocs/gcc-10/buildstat.html
>  delete mode 100644 htdocs/gcc-11/buildstat.html
>  delete mode 100644 htdocs/gcc-12/buildstat.html
>  delete mode 100644 htdocs/gcc-13/buildstat.html
>  delete mode 100644 htdocs/gcc-9/buildstat.html
Jonathan Wakely Nov. 20, 2023, 2:12 p.m. UTC | #2 
On Mon, 20 Nov 2023 at 08:42, Thomas Schwinge <thomas@schwinge.name> wrote:
>
> Hi!
>
> On 2023-10-15T23:42:39+0200, Gerald Pfeifer <gerald@pfeifer.com> wrote:
> > [ Release managers, heads-up for when you branch future releases! ]
>
> > For GCC 9 to GCC 13 the per-release series buildstat pages have not
> > been populated at all, so remove them and reference from the respective
> > main release pages.
>
> ACK; I had recently run into such an empty page, and wanted to suggest
> the same.
>
> We still need to update the docs some more.  Do we just remove all
> references (and related text), and/or refer to the gcc-testresults
> mailing list?
>
> In wwwdocs:
>
>     htdocs/branching.html:<li>Add <code>buildstat.html</code> and update the toplevel
>     htdocs/branching.html:<code>buildstat.html</code> accordingly.</li>
>
>     htdocs/faq.html:Reports of <a href="buildstat.html">successful builds</a>
>     htdocs/faq.html-for several versions of GCC are also available at the web site.</p>
>
>     htdocs/releasing.html-<li>For a new major release, ensure that the build status page is present
>     htdocs/releasing.html:and add a link from the main <code>buildstat.html</code> page.</li>
>
> In GCC:
>
>     gcc/doc/install.texi-Lists of successful builds for released versions of GCC are
>     gcc/doc/install.texi:available at @uref{https://gcc.gnu.org/buildstat.html}.
>     gcc/doc/install.texi-These lists are updated as new information becomes available.
>
>     gcc/doc/install.texi-Some of these archived results are linked from the build status lists
>     gcc/doc/install.texi:at @uref{https://gcc.gnu.org/buildstat.html}, although not everyone who
>     gcc/doc/install.texi-reports a successful build runs the testsuites and submits the results.
>
>     gcc/doc/install.texi-If you are bootstrapping a released version of GCC then please
>     gcc/doc/install.texi-quickly review the build status page for your release, available from
>     gcc/doc/install.texi:@uref{https://gcc.gnu.org/buildstat.html}.
>
>     libstdc++-v3/doc/xml/faq.xml-    the rapid development and near-legendary
>     libstdc++-v3/doc/xml/faq.xml:    <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://gcc.gnu.org/buildstat.html">portability</link>
>     libstdc++-v3/doc/xml/faq.xml-    that are the hallmarks of an open-source project are applied to libstdc++.
>
>     libstdc++-v3/doc/xml/manual/test.xml-       Archives of test results for various versions and platforms are
>     libstdc++-v3/doc/xml/manual/test.xml:       available on the GCC website in the <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://gcc.gnu.org/gcc-4.3/buildstat.html">build
>     libstdc++-v3/doc/xml/manual/test.xml-       status</link> section of each individual release, and are also
>     libstdc++-v3/doc/xml/manual/test.xml-       archived on a daily basis on the <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://gcc.gnu.org/ml/gcc-testresults/current">gcc-testresults</link>


Good point. I'll push the attached patch to the docs.
commit fd7a339512b60545700124b21700fb86a6527f76
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Mon Nov 20 12:41:30 2023

    libstdc++: Remove outdated references to buildstat.html
    
    The buildstat.html pages have not existed since gcc-8 so remove
    referencs to them in the libstdc++ manual.
    
    libstdc++-v3/ChangeLog:
    
            * doc/html/*: Regenerate.
            * doc/xml/faq.xml: Remove reference to buildstat.html pages.
            * doc/xml/manual/test.xml: Likewise

diff --git a/libstdc++-v3/doc/xml/faq.xml b/libstdc++-v3/doc/xml/faq.xml
index da41199584e..79edb02bec4 100644
--- a/libstdc++-v3/doc/xml/faq.xml
+++ b/libstdc++-v3/doc/xml/faq.xml
@@ -64,9 +64,8 @@
     (<command>gcc</command>, <command>g++</command>, etc) is widely
     considered to be one of the leading compilers in the world.  Its
     development is overseen by the
-    <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://gcc.gnu.org/">GCC team</link>.  All of
-    the rapid development and near-legendary
-    <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://gcc.gnu.org/buildstat.html">portability</link>
+    <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://gcc.gnu.org/">GCC team</link>.
+    All of the rapid development and near-legendary portability
     that are the hallmarks of an open-source project are applied to libstdc++.
     </para>
     <para>
diff --git a/libstdc++-v3/doc/xml/manual/test.xml b/libstdc++-v3/doc/xml/manual/test.xml
index 936f97417af..f2c709bc6bf 100644
--- a/libstdc++-v3/doc/xml/manual/test.xml
+++ b/libstdc++-v3/doc/xml/manual/test.xml
@@ -266,10 +266,8 @@ cat 27_io/objects/char/3_xin.in | a.out</programlisting>
 
      <para>
        Archives of test results for various versions and platforms are
-       available on the GCC website in the <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://gcc.gnu.org/gcc-4.3/buildstat.html">build
-       status</link> section of each individual release, and are also
        archived on a daily basis on the <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://gcc.gnu.org/ml/gcc-testresults/current">gcc-testresults</link>
-       mailing list. Please check either of these places for a similar
+       mailing list. Please check there for a similar
        combination of source version, operating system, and host CPU.
      </para>
   </section>
Gerald Pfeifer Nov. 24, 2023, 12:01 a.m. UTC | #3 
On Mon, 20 Nov 2023, Thomas Schwinge wrote:
>> For GCC 9 to GCC 13 the per-release series buildstat pages have not
>> been populated at all, so remove them and reference from the respective
>> main release pages.
> ACK; I had recently run into such an empty page, and wanted to suggest
> the same.
> 
> We still need to update the docs some more.  Do we just remove all
> references (and related text), and/or refer to the gcc-testresults
> mailing list?

The libstdc++ docs refer to gcc-results and I'll see to add this to the 
web pages where applicable.

> In wwwdocs:
> 
>     htdocs/branching.html:<li>Add <code>buildstat.html</code> and update the toplevel
>     htdocs/branching.html:<code>buildstat.html</code> accordingly.</li>
> 
>     htdocs/faq.html:Reports of <a href="buildstat.html">successful builds</a>
>     htdocs/faq.html-for several versions of GCC are also available at the web site.</p>
> 
>     htdocs/releasing.html-<li>For a new major release, ensure that the build status page is present
>     htdocs/releasing.html:and add a link from the main <code>buildstat.html</code> page.</li>

I have taken care of all these and will look into gcc/doc/install.texi in 
the coming days.

Thanks for bringing this up!

Gerald
diff mbox series

Patch

diff --git a/htdocs/gcc-10/buildstat.html b/htdocs/gcc-10/buildstat.html
deleted file mode 100644
index 5d18742e..00000000
--- a/htdocs/gcc-10/buildstat.html
+++ /dev/null
@@ -1,27 +0,0 @@ 
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-<title>Build status for GCC 10</title>
-<link rel="stylesheet" type="text/css" href="https://gcc.gnu.org/gcc.css">
-</head>
-
-<body>
-<h1>Build status for GCC 10</h1>
-
-<p>This list summarizes build reports for GCC 10.x, with links to the
-archived mail messages that reported the builds and to test result
-summaries.</p>
-
-<p>Instructions for running the test suite and for submitting test results
-are part of
-<a href="http://gcc.gnu.org/install/test.html">
-Installing GCC: Testing</a>.
-Instructions for reporting a successful &quot;make bootstrap&quot;,
-including a list of information to include in such a report, are part of
-<a href="http://gcc.gnu.org/install/finalinstall.html">
-Installing GCC: Final Installation</a>.</p>
-
-</body>
-</html>
diff --git a/htdocs/gcc-10/index.html b/htdocs/gcc-10/index.html
index a9547d18..5fb1e02e 100644
--- a/htdocs/gcc-10/index.html
+++ b/htdocs/gcc-10/index.html
@@ -63,9 +63,6 @@  GCC 10.4 relative to previous releases of GCC.</p>
 supports several other languages aside from C, it now stands for the
 GNU Compiler Collection.</p>
 
-<p>A list of <a href="buildstat.html">successful builds</a> is updated
-as new information becomes available.</p>
-
 <p>The GCC developers would like to thank the numerous people that have
 contributed new features, improvements, bug fixes, and other changes as
 well as test results to GCC.
diff --git a/htdocs/gcc-11/buildstat.html b/htdocs/gcc-11/buildstat.html
deleted file mode 100644
index c86238c6..00000000
--- a/htdocs/gcc-11/buildstat.html
+++ /dev/null
@@ -1,27 +0,0 @@ 
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-<title>Build status for GCC 11</title>
-<link rel="stylesheet" type="text/css" href="https://gcc.gnu.org/gcc.css">
-</head>
-
-<body>
-<h1>Build status for GCC 11</h1>
-
-<p>This list summarizes build reports for GCC 11.x, with links to the
-archived mail messages that reported the builds and to test result
-summaries.</p>
-
-<p>Instructions for running the test suite and for submitting test results
-are part of
-<a href="http://gcc.gnu.org/install/test.html">
-Installing GCC: Testing</a>.
-Instructions for reporting a successful &quot;make bootstrap&quot;,
-including a list of information to include in such a report, are part of
-<a href="http://gcc.gnu.org/install/finalinstall.html">
-Installing GCC: Final Installation</a>.</p>
-
-</body>
-</html>
diff --git a/htdocs/gcc-11/index.html b/htdocs/gcc-11/index.html
index 7cd96f7e..bb41c492 100644
--- a/htdocs/gcc-11/index.html
+++ b/htdocs/gcc-11/index.html
@@ -54,9 +54,6 @@  GCC 11.3 relative to previous releases of GCC.</p>
 supports several other languages aside from C, it now stands for the
 GNU Compiler Collection.</p>
 
-<p>A list of <a href="buildstat.html">successful builds</a> is updated
-as new information becomes available.</p>
-
 <p>The GCC developers would like to thank the numerous people that have
 contributed new features, improvements, bug fixes, and other changes as
 well as test results to GCC.
diff --git a/htdocs/gcc-12/buildstat.html b/htdocs/gcc-12/buildstat.html
deleted file mode 100644
index e066026f..00000000
--- a/htdocs/gcc-12/buildstat.html
+++ /dev/null
@@ -1,27 +0,0 @@ 
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-<title>Build status for GCC 12</title>
-<link rel="stylesheet" type="text/css" href="https://gcc.gnu.org/gcc.css">
-</head>
-
-<body>
-<h1>Build status for GCC 12</h1>
-
-<p>This list summarizes build reports for GCC 12.x, with links to the
-archived mail messages that reported the builds and to test result
-summaries.</p>
-
-<p>Instructions for running the test suite and for submitting test results
-are part of
-<a href="http://gcc.gnu.org/install/test.html">
-Installing GCC: Testing</a>.
-Instructions for reporting a successful &quot;make bootstrap&quot;,
-including a list of information to include in such a report, are part of
-<a href="http://gcc.gnu.org/install/finalinstall.html">
-Installing GCC: Final Installation</a>.</p>
-
-</body>
-</html>
diff --git a/htdocs/gcc-12/index.html b/htdocs/gcc-12/index.html
index f8c589e8..a76ef1dc 100644
--- a/htdocs/gcc-12/index.html
+++ b/htdocs/gcc-12/index.html
@@ -48,9 +48,6 @@  GCC 12.2 relative to previous releases of GCC.</p>
 supports several other languages aside from C, it now stands for the
 GNU Compiler Collection.</p>
 
-<p>A list of <a href="buildstat.html">successful builds</a> is updated
-as new information becomes available.</p>
-
 <p>The GCC developers would like to thank the numerous people that have
 contributed new features, improvements, bug fixes, and other changes as
 well as test results to GCC.
diff --git a/htdocs/gcc-13/buildstat.html b/htdocs/gcc-13/buildstat.html
deleted file mode 100644
index a54d0214..00000000
--- a/htdocs/gcc-13/buildstat.html
+++ /dev/null
@@ -1,27 +0,0 @@ 
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-<title>Build status for GCC 13</title>
-<link rel="stylesheet" type="text/css" href="https://gcc.gnu.org/gcc.css">
-</head>
-
-<body>
-<h1>Build status for GCC 13</h1>
-
-<p>This list summarizes build reports for GCC 13.x, with links to the
-archived mail messages that reported the builds and to test result
-summaries.</p>
-
-<p>Instructions for running the test suite and for submitting test results
-are part of
-<a href="http://gcc.gnu.org/install/test.html">
-Installing GCC: Testing</a>.
-Instructions for reporting a successful &quot;make bootstrap&quot;,
-including a list of information to include in such a report, are part of
-<a href="http://gcc.gnu.org/install/finalinstall.html">
-Installing GCC: Final Installation</a>.</p>
-
-</body>
-</html>
diff --git a/htdocs/gcc-13/index.html b/htdocs/gcc-13/index.html
index e11b48a3..ed23d786 100644
--- a/htdocs/gcc-13/index.html
+++ b/htdocs/gcc-13/index.html
@@ -42,9 +42,6 @@  GCC 13.1 relative to previous releases of GCC.</p>
 supports several other languages aside from C, it now stands for the
 GNU Compiler Collection.</p>
 
-<p>A list of <a href="buildstat.html">successful builds</a> is updated
-as new information becomes available.</p>
-
 <p>The GCC developers would like to thank the numerous people that have
 contributed new features, improvements, bug fixes, and other changes as
 well as test results to GCC.
diff --git a/htdocs/gcc-9/buildstat.html b/htdocs/gcc-9/buildstat.html
deleted file mode 100644
index 0ad07a51..00000000
--- a/htdocs/gcc-9/buildstat.html
+++ /dev/null
@@ -1,27 +0,0 @@ 
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-<title>Build status for GCC 9</title>
-<link rel="stylesheet" type="text/css" href="https://gcc.gnu.org/gcc.css">
-</head>
-
-<body>
-<h1>Build status for GCC 9</h1>
-
-<p>This list summarizes build reports for GCC 9.x, with links to the
-archived mail messages that reported the builds and to test result
-summaries.</p>
-
-<p>Instructions for running the test suite and for submitting test results
-are part of
-<a href="http://gcc.gnu.org/install/test.html">
-Installing GCC: Testing</a>.
-Instructions for reporting a successful &quot;make bootstrap&quot;,
-including a list of information to include in such a report, are part of
-<a href="http://gcc.gnu.org/install/finalinstall.html">
-Installing GCC: Final Installation</a>.</p>
-
-</body>
-</html>
diff --git a/htdocs/gcc-9/index.html b/htdocs/gcc-9/index.html
index 22f76155..71d25103 100644
--- a/htdocs/gcc-9/index.html
+++ b/htdocs/gcc-9/index.html
@@ -63,9 +63,6 @@  GCC 9.4 relative to previous releases of GCC.</p>
 supports several other languages aside from C, it now stands for the
 GNU Compiler Collection.</p>
 
-<p>A list of <a href="buildstat.html">successful builds</a> is updated
-as new information becomes available.</p>
-
 <p>The GCC developers would like to thank the numerous people that have
 contributed new features, improvements, bug fixes, and other changes as
 well as test results to GCC.