From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtprelay06.ispgateway.de (smtprelay06.ispgateway.de [80.67.31.103]) by sourceware.org (Postfix) with ESMTPS id 64E383882155; Mon, 20 Nov 2023 08:42:36 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 64E383882155 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=schwinge.name Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=schwinge.name ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 64E383882155 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=80.67.31.103 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1700469760; cv=none; b=TVv71CdGEoit2e6Hs9v7uEDFrqoLmKNbQfHEwIWaVCY/5q2MCaagS/fA8QzJq5mETfrAR7OHjOrlohmTLqDc1f0MtT07hycwDbkUOzwXzcPG076yXS7WQI+tEp/0Vnf8IuDoU77ZmGiFkXgSe0D/hnZF8m83+OO/z8GIV1bBPW0= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1700469760; c=relaxed/simple; bh=mdLBRVY3GXip2IF5yPICqn973cNsHcX9dlp1elovcnI=; h=From:To:Subject:Date:Message-ID:MIME-Version; b=NH/sjaAtTj8nQ5s1pppl6mCokDyZcTInZJArVZ9lDqUAvVnyCO7jTNVfKzjBqWCIDZOeoXfmmDdtbNb1IQFGzrybV1abg2mmNflfxqc6i8Iq9af73UJKN3XHdi/YQNEtlQcQn7/70t9k4jp1/P32zjKGpucDzKeQfgGuH9X7yNw= ARC-Authentication-Results: i=1; server2.sourceware.org Received: from [93.210.54.129] (helo=euler.schwinge.homeip.net) by smtprelay06.ispgateway.de with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96.1) (envelope-from ) id 1r4zrV-0003pf-1L; Mon, 20 Nov 2023 09:42:33 +0100 Received: (nullmailer pid 3585862 invoked by uid 1000); Mon, 20 Nov 2023 08:42:32 -0000 From: Thomas Schwinge To: Gerald Pfeifer Cc: Jakub Jelinek , "Joseph S. Myers" , Richard Biener , gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org Subject: Re: [pushed] wwwdocs: *: Remove unused buildstat pages In-Reply-To: <20231015214241.B37BB33EB9@hamza.pair.com> References: <20231015214241.B37BB33EB9@hamza.pair.com> User-Agent: Notmuch/0.29.3+94~g74c3f1b (https://notmuchmail.org) Emacs/28.2 (x86_64-pc-linux-gnu) Date: Mon, 20 Nov 2023 09:42:27 +0100 Message-ID: <87pm04stn0.fsf@euler.schwinge.homeip.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Df-Sender: b3V0Z29pbmdAc2Nod2luZ2UubmFtZQ== X-Spam-Status: No, score=-63.9 required=5.0 tests=BAYES_00,KAM_ASCII_DIVIDERS,KAM_DMARC_STATUS,KAM_SHORT,SPF_HELO_PASS,SPF_PASS,TXREP,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: Hi! On 2023-10-15T23:42:39+0200, Gerald Pfeifer 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:
  • Add buildstat.html and update th= e toplevel htdocs/branching.html:buildstat.html accordingly.
    • htdocs/faq.html:Reports of successful builds= htdocs/faq.html-for several versions of GCC are also available at the w= eb site.

    htdocs/releasing.html-
  • For a new major release, ensure that the buil= d status page is present htdocs/releasing.html:and add a link from the main buildstat.html= page.
    • In GCC: gcc/doc/install.texi-Lists of successful builds for released versions o= f GCC are gcc/doc/install.texi:available at @uref{https://gcc.gnu.org/buildstat.h= tml}. 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}, alth= ough 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 rele= ase, available from gcc/doc/install.texi:@uref{https://gcc.gnu.org/buildstat.html}. libstdc++-v3/doc/xml/faq.xml- the rapid development and near-legenda= ry libstdc++-v3/doc/xml/faq.xml: portability<= /link> libstdc++-v3/doc/xml/faq.xml- that are the hallmarks of an open-sour= ce project are applied to libstdc++. libstdc++-v3/doc/xml/manual/test.xml- Archives of test results fo= r various versions and platforms are libstdc++-v3/doc/xml/manual/test.xml: available on the GCC websit= e in the build libstdc++-v3/doc/xml/manual/test.xml- status section of ea= ch individual release, and are also libstdc++-v3/doc/xml/manual/test.xml- archived on a daily basis o= n the gcc-testresults Gr=C3=BC=C3=9Fe 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