all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: guix-devel <guix-devel@gnu.org>
Subject: ‘staging’ branch is open!
Date: Sat, 30 Apr 2022 01:08:52 +0200	[thread overview]
Message-ID: <878rrn5vy3.fsf@inria.fr> (raw)

Hi!

The ‘staging’ branch is open!  Which means that changes with “between
300 and 1,800 rebuilds” (info "(guix) Submitting Patches") can go there;
now’s the time to (re)send package updates in that ballpark.

Incidentally, I was considering ungrafting things on that branch, even
those that go beyond the 1,800 dependents limit, since this is almost
always a safe change and ci.guix now has the capacity and stability
needed for that.

What do people think?

I think we should aim for a freeze in one or two weeks, merging in three
weeks, and resume work on the new release to be done sometime after the
merge.

Thoughts?

Ludo’.


             reply	other threads:[~2022-04-29 23:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-29 23:08 Ludovic Courtès [this message]
2022-04-30  8:40 ` ‘staging’ branch is open! zimoun
2022-05-07 22:04   ` Ludovic Courtès
2022-05-08 20:14     ` zimoun
2022-05-15 20:55     ` Ludovic Courtès
2022-05-16 21:37       ` zimoun
2022-05-23 15:23         ` Ludovic Courtès
2022-05-31  7:34           ` Christopher Baines
2022-06-01 16:44             ` ‘staging’ to be merged soon: help needed! Ludovic Courtès
2022-05-03 17:54 ` ‘staging’ branch is open! Maxim Cournoyer
2022-05-10 12:59 ` python-cryptography and rust [was: Re: ‘staging’ branch is open!] Efraim Flashner
2022-05-15 21:22   ` Ludovic Courtès
2022-05-16  7:43     ` Efraim Flashner
2022-05-23 15:25       ` 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

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

  git send-email \
    --in-reply-to=878rrn5vy3.fsf@inria.fr \
    --to=ludo@gnu.org \
    --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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.