Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: "Frank Ch. Eigler" <fche@redhat.com>, gdb@sourceware.org
Subject: Re: value of gdbadmin effort to create gdb daily/weekly source tarballs
Date: Mon, 15 Apr 2024 20:14:47 +0200	[thread overview]
Message-ID: <20240415181447.GX1292@gnu.wildebeest.org> (raw)
In-Reply-To: <Zh1oV/DE6mDY/pzJ@adacore.com>

Hi,

On Mon, Apr 15, 2024 at 10:48:07AM -0700, Joel Brobecker via Gdb wrote:
> On the other hand, it does act a periodic test of the script being
> src-release.sh script staying operational. But if that were the only
> reason we had, we can preserve this as a pure test, where we do
> a periodic source packaging, but instead of saving it for people
> to download, we simple discard it.

Other projects like glibc, valgrind, libabigail, etc. have moved their
snapshots builds to http://snapshots.sourceware.org/ which creates a
snapshot build and creates documentation from current git. This makes
sure the release processes/scripts keep working. And it has caught
release issues early (which often don't occur during a normal
developer build). Since this is part of the normal
builder.sourceware.org infrastructure it also provides better
visibility.

Cheers,

Mark

  reply	other threads:[~2024-04-15 18:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-15 14:34 Frank Ch. Eigler via Gdb
2024-04-15 17:48 ` Joel Brobecker via Gdb
2024-04-15 18:14   ` Mark Wielaard [this message]
2024-04-15 18:26     ` Joel Brobecker via Gdb
2024-05-24 23:17       ` Mark Wielaard
2024-04-15 18:28   ` Frank Ch. Eigler via Gdb

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240415181447.GX1292@gnu.wildebeest.org \
    --to=mark@klomp.org \
    --cc=brobecker@adacore.com \
    --cc=fche@redhat.com \
    --cc=gdb@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox