unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: Andreas Enge <andreas@enge.fr>,
	Felix Lechner <felix.lechner@lease-up.com>
Cc: Josselin Poiret <dev@jpoiret.xyz>, guix-devel@gnu.org
Subject: Re: Core-updates coordination and plans
Date: Tue, 27 Feb 2024 09:49:23 -0800	[thread overview]
Message-ID: <874jdtre58.fsf@contorta> (raw)
In-Reply-To: <Zd4NNyr-F8sAvQRL@jurong>

[-- Attachment #1: Type: text/plain, Size: 1022 bytes --]

On 2024-02-27, Andreas Enge wrote:
> Am Mon, Feb 26, 2024 at 07:26:57AM -0800 schrieb Felix Lechner:
>> How about a 48-hour period every month in which commits are permitted
>> even if they cause "world rebuilds"?
>> We could pause the substitute builders during that period. It would get
>> rid of core-updates forever.
>
> a time-based approach sounds like a good idea indeed; if just for things
> like ungrafting, which are considered extremely low risk. It might still
> be good to do it in a separate branch instead of master, and to merge it
> after substitutes are available. Since "guix pull" takes the latest commit
> from the master branch, users could otherwise end up with a world-rebuild
> commit without substitutes.
>
> So maybe we could have a time window, but also discuss and prepare before-
> hand which big changes we would like to push?

Or a similarly "short" time period where commits to master are blocked,
so that substitutes being built for branches-to-be-merged are not
chasing a moving target?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  reply	other threads:[~2024-02-27 17:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-31 16:44 Core-updates coordination and plans Josselin Poiret
2024-01-31 18:19 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-01-31 21:59   ` Vivien Kraus
2024-01-31 23:28     ` Eudev in gnome-team [Was: Core-updates coordination and plans] Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-01-31 20:18 ` Core-updates coordination and plans Andreas Enge
2024-02-26 15:26   ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-02-27 16:26     ` Andreas Enge
2024-02-27 17:49       ` Vagrant Cascadian [this message]
2024-02-27 20:51       ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-01-31 22:01 ` Vagrant Cascadian
2024-02-01 17:53 ` Vivien Kraus
2024-02-18 13:51 ` Josselin Poiret
2024-02-24 16:11   ` Ludovic Courtès

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=874jdtre58.fsf@contorta \
    --to=vagrant@debian.org \
    --cc=andreas@enge.fr \
    --cc=dev@jpoiret.xyz \
    --cc=felix.lechner@lease-up.com \
    --cc=guix-devel@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).