unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Latest news on core-updates
Date: Fri, 21 Apr 2023 09:58:57 +0200	[thread overview]
Message-ID: <ZEJCQSVo+qX2zpoE@jurong> (raw)
In-Reply-To: <ZD/he8EmwH7nqHh+@jurong>

Hello Maxim,

Am Wed, Apr 19, 2023 at 02:41:31PM +0200 schrieb Andreas Enge:
> I am not sure what "frozen" means exactly; I would say we must not make
> commits to core-updates unless they repair a broken package, or maybe help
> repair broken packages further down towards the leaves.

your recent docbook commits probably do not fit this definition, much less
so than the suggested valgrind update that we nevertheless postponed until
after the merge. They cause an extraordinary number of rebuilds. I hope they
are mostly harmless and do not cause additional build failures, so keeping
them in is probably easier than reverting them.

But let us from now on stick with commits that make important packages work,
or packages very close to the leaves.

I suggest the following timetable:
- Hard freeze now, only important broken packages or packages close to the
  leaves may be changed.
- Over the weekend, update your systems and profiles and test and repair
  problems that appear.
- If no show-stopper occurs, merge core-updates into master on Tuesday.

Andreas



  reply	other threads:[~2023-04-21  7:59 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-16 11:09 Core-updates after the staging merge Andreas Enge
2023-04-16 11:59 ` [bug#62863] Openldap in core-updates Andreas Enge
2023-04-16 14:00 ` wget on i686 " Andreas Enge
2023-04-16 18:57   ` Andreas Enge
2023-04-17  8:06     ` Andreas Enge
2023-04-17  8:18 ` Core-updates after the staging merge Guillaume Le Vaillant
2023-04-17  8:33   ` Andreas Enge
2023-04-17  9:03 ` Andreas Enge
2023-04-17  9:56   ` Andreas Enge
2023-04-17 12:19     ` Simon Tournier
2023-04-17 12:38       ` Andreas Enge
2023-04-17 12:57         ` Simon Tournier
2023-04-17 14:12       ` Lars-Dominik Braun
2023-04-17 17:47         ` Simon Tournier
2023-04-17 18:07           ` Andreas Enge
2023-04-17 19:01             ` Lars-Dominik Braun
2023-04-18 17:16               ` Andreas Enge
2023-04-21 18:29                 ` Lars-Dominik Braun
2023-04-17 12:57   ` Andreas Enge
2023-04-17 18:03   ` Maxim Cournoyer
2023-04-17 18:08     ` Andreas Enge
2023-04-18  5:04   ` John Kehayias
2023-04-18 17:38     ` Andreas Enge
2023-04-19 10:48   ` Latest news on core-updates Andreas Enge
2023-04-19 10:58     ` Christopher Baines
2023-04-19 12:41       ` Andreas Enge
2023-04-21  7:58         ` Andreas Enge [this message]
2023-04-21 13:01           ` Maxim Cournoyer
2023-04-20 13:56       ` Christopher Baines
2023-04-20 18:09         ` Andreas Enge
2023-04-21  8:20     ` Simon Tournier
2023-04-21  8:47       ` Andreas Enge
2023-04-21 11:31         ` Simon Tournier
2023-04-21 16:12     ` Katherine Cox-Buday
2023-04-21 16:12       ` Katherine Cox-Buday
2023-04-21 17:04       ` reza.housseini
2023-04-23  7:17         ` Andreas Enge

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=ZEJCQSVo+qX2zpoE@jurong \
    --to=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    /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).