From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gnu.wildebeest.org (gnu.wildebeest.org [45.83.234.184]) by sourceware.org (Postfix) with ESMTPS id A45A03858D1E for ; Sat, 31 Dec 2022 22:19:58 +0000 (GMT) Received: from reform (deer0x08.wildebeest.org [172.31.17.138]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id C167130067BB; Sat, 31 Dec 2022 23:19:55 +0100 (CET) Received: by reform (Postfix, from userid 1000) id 4FA382E80550; Sat, 31 Dec 2022 23:19:55 +0100 (CET) Date: Sat, 31 Dec 2022 23:19:55 +0100 From: Mark Wielaard To: Nick Clifton Cc: joel@rtems.org, Mike Frysinger , Joel Brobecker , Binutils Subject: Re: A GNU Binutils wiki Message-ID: References: <71067e2b-f43b-2be8-ea4a-88ead1dd6e56@redhat.com> <4ca81bcb-c569-7d9d-a243-fea12bfead52@redhat.com> <87fb1712-d568-46fc-aa47-733ff6931171@redhat.com> <4944644e-68c3-abfa-e2dd-e99bcb4085f0@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4944644e-68c3-abfa-e2dd-e99bcb4085f0@redhat.com> X-Spam-Status: No, score=-3032.3 required=5.0 tests=BAYES_00,JMQ_SPF_NEUTRAL,KAM_DMARC_STATUS,SPF_HELO_NONE,SPF_PASS,TXREP 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 Nick, On Wed, Nov 30, 2022 at 11:03:12AM +0000, Nick Clifton via Binutils wrote: > > How are the current code snapshots created? > > I think that there is a cron job on sourceware that creates the snapshots. I can find the gdbadmin cron job that creates gdb snapshots, but it looks like you create the binutils snapshots by hand and upload them to https://sourceware.org/pub/binutils/snapshots/ It would be nice to automate this a bit more either with a real cronjob or a specific buildbot worker. > > How is the documentation uploaded at release time? > > By hand. :-) > > I have a procedure outlined in the binutils/README-how-to-make-a-release > document that I follow whenever I need to update the documentation. Nice. I saw you just updated for the next release. We can automate some steps of that. Specifically 9. Create an initial pre-release. Which can be a build script for the buildbot that can create a snapshot each commit or day. About 12. Build various different toolchains, test them and nag maintainers to fix any testsuite failures for their architectures... Which toolchains/architectures are that? Are any of them missing from: https://builder.sourceware.org/buildbot/#/builders?tags=binutils BTW. binutils-debian-i386, binutils-fedora-arm64 and binutils-fedora-s390x do show some testsuite failures. > > We can automate both and publish them on a special buildbot worker > > under something like snapshots.sourceware.org/bintuils to keep them > > current and so everybody can immediately see how the documentation > > looks. > > That would be nice. Would it involve taking up a lot of disk space ? > (Ie for how long would these snapshots last ?) binutils snapshots are ~24MB, documentation ~18MB. So if we do one a day that is ~1GB a month. And since it looks like you recently added the option to create reproducible tarballs we don't really need to keep all of them since people could recreate them from a git checkout. Cheers, Mark