all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: core-updates schedule
Date: Thu, 2 Aug 2018 12:08:19 +0300	[thread overview]
Message-ID: <20180802090819.GC13776@macbook41> (raw)
In-Reply-To: <87a7q6rkub.fsf@elephly.net>

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

On Wed, Aug 01, 2018 at 08:41:00PM +0200, Ricardo Wurmus wrote:
> Hello Guix!
> 
> This is a reminder about the “core-updates” branch.  Our plan was to
> freeze the branch on <2018-08-06 Mon> and aim to merge the branch into
> “master” on <2018-08-20 Mon>, dependent on how long it takes to fix all
> problems and build most packages.
> 
> Freezing the branch means that only commits to fix build failures may be
> pushed.
> 
> We will need volunteers to watch build failures on the Hydra web
> interface.
> 
> --
> Ricardo
> 
> PS: I would like to push the patch in #29951 to core-updates so that we
> can opt to wrap scripts with “wrap-script” going forward.
> 

Does core-updates currently address bug 31974, aka 'phases should return
#t or actually fail'?

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

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

  reply	other threads:[~2018-08-02  9:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-01 18:41 core-updates schedule Ricardo Wurmus
2018-08-02  9:08 ` Efraim Flashner [this message]
2018-08-04  3:22   ` Mark H Weaver
2018-08-05 14:47 ` Ricardo Wurmus
2018-08-20  9:03   ` Ludovic Courtès
2018-08-20  9:59     ` Ricardo Wurmus
2018-08-20 12:41       ` Marius Bakke
2018-08-20 16:07         ` 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=20180802090819.GC13776@macbook41 \
    --to=efraim@flashner.co.il \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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.