From: zimoun <zimon.toutoune@gmail.com>
To: Mathieu Othacehe <othacehe@gnu.org>, guix-devel <guix-devel@gnu.org>
Subject: Re: Building the core-updates branch.
Date: Sat, 06 Feb 2021 14:40:33 +0100 [thread overview]
Message-ID: <86a6shb9gu.fsf@gmail.com> (raw)
In-Reply-To: <87blcxaad3.fsf@gnu.org>
Hi Mathieu,
On Sat, 06 Feb 2021 at 09:06, Mathieu Othacehe <othacehe@gnu.org> wrote:
> Even if the core-updates builds have to the lowest priority on the CI,
> and the CI is performing a bit better, I'm not sure building this branch
> is reasonable for now. I feel like we should first focus on providing
> substitutes for the master, guix-modular-master and staging branches
> consistently and on all architectures before trying to build
> core-updates.
Back on October, Chris proposed this:
<https://yhetil.org/guix/877drg3lmi.fsf@cbaines.net/>
and it seems similar. Roughly speaking, let only build core-updates (on
Berlin) when the freeze starts just before the merge.
About the CI, the “production” (= substitutes of master for all the
architectures) and the “testing” (= substitutes of core-updates and
wip-*) should be clearly 2 different things. Maybe on Berlin and
Bayfront.
All the best,
simon
next prev parent reply other threads:[~2021-02-06 13:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-06 8:06 Building the core-updates branch Mathieu Othacehe
2021-02-06 11:11 ` Mathieu Othacehe
2021-02-06 21:48 ` Ludovic Courtès
2021-02-06 22:21 ` Ricardo Wurmus
2021-02-06 13:40 ` zimoun [this message]
2021-02-06 21:50 ` Ludovic Courtès
2021-02-07 18:22 ` Mathieu Othacehe
2021-02-07 18:43 ` Mathieu Othacehe
2021-02-07 19:29 ` Leo Famulari
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86a6shb9gu.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=othacehe@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).