unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: guix-devel <guix-devel@gnu.org>
Subject: Preparing the release on the ‘version-1.4.0’ branch
Date: Tue, 29 Nov 2022 10:07:51 +0100	[thread overview]
Message-ID: <87pmd65dso.fsf@gnu.org> (raw)

Hello Guix!

Just a heads-up: the lights are green on ‘version-1.4.0’ to prepare a
release candidate:

--8<---------------cut here---------------start------------->8---
$ make assert-binaries-available
Compiling Scheme modules...
Compiling Scheme modules...
Compiling Scheme modules...
Compiling Scheme modules...
computing 399 package derivations for x86_64-linux...
looking for 504 store items on https://ci.guix.gnu.org...
https://ci.guix.gnu.org ☀
  100.0% substitutes available (504 out of 504)
  at least 5,200.3 MiB of nars (compressed)
  8,651.1 MiB on disk (uncompressed)
  0.708 seconds per request (0.7 seconds in total)
  1.4 requests per second

  at least 1,000 queued builds
      aarch64-linux: 979 (97.9%)
      powerpc64le-linux: 21 (2.1%)
  build rate: 42.87 builds per hour
      x86_64-linux: 27.89 builds per hour
      aarch64-linux: 13.63 builds per hour
      i686-linux: 1.33 builds per hour
      powerpc64le-linux: 0.48 builds per hour
$ git log |head -5
commit 1bc9d5222f9053fd0ace7b92df0ef9548707cf41
Author: Ludovic Courtès <ludo@gnu.org>
Date:   Mon Nov 28 13:51:51 2022 +0100

    maint: Leave 'gcc-toolchain' out for i586-gnu.
--8<---------------cut here---------------end--------------->8---

Please only push release-critical fixes to that branch.  Other changes
can of course still go to ‘master’.

In the coming days I’ll run “make release” and address remaining issues
there so we can hopefully publish RC1 within a few days.  Help is
welcome!  Let’s synchronize by email and (preferably) on IRC!

Ludo’.


                 reply	other threads:[~2022-11-29  9:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87pmd65dso.fsf@gnu.org \
    --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 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).