From: Nick Clifton <nickc@redhat.com>
To: Mark Wielaard <mark@klomp.org>
Cc: buildbot@sourceware.org, binutils@sourceware.org,
"Jose E. Marchesi" <jose.marchesi@oracle.com>,
elena.zannoni@oracle.com, david.faust@oracle.com
Subject: Re: binutils snapshot builds
Date: Fri, 24 May 2024 13:31:31 +0100 [thread overview]
Message-ID: <59999a82-ccb6-4298-95e8-d5e49b59c739@redhat.com> (raw)
In-Reply-To: <20240523233230.GE13045@gnu.wildebeest.org>
Hi Mark,
> What do people think is a good policy?
>
> - Just keep one snapshot a day after a year.
> - Only keep snapshots for 1, 2 or 3 years.
> - Just throw money at it, disks are cheap.
> Just buy another 600G when it fills up?
Given that any of these snapshots can be reproduced from the git repository
I do not see any great benefit in maintaining them long term. My feeling
is that is they will loose their usefulness once an official release is
made, or possibly after two releases. So how about:
* Snapshots are retained for at least 1 year after their creation.
* After that they can be culled at the discretion of the overseers
(and without needing to consult with the binutils project) as and
when they wish.
Cheers
Nick
next prev parent reply other threads:[~2024-05-24 12:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 22:08 Mark Wielaard
2024-05-22 22:08 ` [PATCH 1/2] Add binutils-snapshots builder Mark Wielaard
2024-05-22 22:08 ` [PATCH 2/2] binutils snapshot steps should run in the git step workdir Mark Wielaard
2024-05-23 10:35 ` binutils snapshot builds Nick Clifton
2024-05-23 23:32 ` Mark Wielaard
2024-05-24 12:31 ` Nick Clifton [this message]
2024-05-24 14:03 ` Jose E. Marchesi
2024-05-23 15:11 ` Jose E. Marchesi
2024-05-23 15:28 ` Frank Ch. Eigler
2024-05-23 15:33 ` Jose E. Marchesi
2024-05-23 22:52 ` Sam James
2024-05-23 23:59 ` Mark Wielaard
2024-05-23 23:41 ` Mark Wielaard
2024-05-24 9:58 ` Jose E. Marchesi
2024-05-26 0:16 ` Mark Wielaard
2024-05-28 14:35 ` Nick Clifton
2024-05-28 16:16 ` Mark Wielaard
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=59999a82-ccb6-4298-95e8-d5e49b59c739@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=buildbot@sourceware.org \
--cc=david.faust@oracle.com \
--cc=elena.zannoni@oracle.com \
--cc=jose.marchesi@oracle.com \
--cc=mark@klomp.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).