From: Leo Famulari <leo@famulari.name>
To: guix-devel@gnu.org
Subject: core-updates frozen!
Date: Mon, 27 Feb 2017 15:30:59 -0500 [thread overview]
Message-ID: <20170227203059.GA2959@jasmine> (raw)
In-Reply-To: <87mvdpw3b3.fsf@gnu.org>
On Tue, Feb 14, 2017 at 10:05:04AM +0100, Ludovic Courtès wrote:
> So, here’s a plan:
>
> • Once Efraim has pushed some of the aarch64 patches, do another
> evaluation of the “core” package set for that branch, and check for
> anything wrong. From there on, forbid full-rebuild changes.
Let's freeze core-updates and try to build it. No more rebuild the world
changes except to fix breakage.
> • Once the “core” subset builds correctly on all the supported
> platforms (those that Hydra supports), merge ‘master’. Maybe update
> a couple of things like GnuTLS while we’re at it. From there on
> forbid non-trivial changes.
>
> • Build all the packages. (To do that, someone with access to Hydra
> must change the “subset” argument to “all” in the config of the
> ‘core-updates’ jobset.)
>
> • Fix things.
>
> • Once most regressions have been addressed and most binaries are
> available, merge ‘core-updates’ into ‘master’.
>
> How does that sound?
>
> Thanks,
> Ludo’.
>
next prev parent reply other threads:[~2017-02-27 20:31 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 9:05 Let’s freeze and build ‘core-updates’! Ludovic Courtès
2017-02-14 15:00 ` Marius Bakke
2017-02-14 16:22 ` Ludovic Courtès
2017-02-21 14:03 ` Marius Bakke
2017-02-21 16:27 ` Andreas Enge
2017-02-21 17:32 ` Leo Famulari
2017-02-21 17:41 ` Leo Famulari
2017-03-06 9:19 ` Ludovic Courtès
2017-03-06 12:31 ` Marius Bakke
2017-03-06 15:39 ` Ludovic Courtès
2017-03-06 22:26 ` Leo Famulari
2017-03-07 13:59 ` Ludovic Courtès
2017-03-08 5:43 ` Leo Famulari
2017-03-08 8:44 ` Ludovic Courtès
2017-03-08 9:03 ` Leo Famulari
2017-03-06 18:42 ` Leo Famulari
2017-03-06 18:49 ` Marius Bakke
2017-03-06 18:54 ` Marius Bakke
2017-03-06 19:13 ` Leo Famulari
2017-03-06 18:54 ` Leo Famulari
2017-02-27 20:30 ` Leo Famulari [this message]
2017-03-02 17:34 ` core-updates frozen! Leo Famulari
2017-03-03 0:02 ` Marius Bakke
2017-03-03 18:27 ` Leo Famulari
2017-03-03 18:33 ` Marius Bakke
2017-03-03 18:53 ` Leo Famulari
2017-03-09 22:33 ` Let’s freeze and build ‘core-updates’! Leo Famulari
2017-03-10 21:46 ` Marius Bakke
2017-03-11 3:10 ` Leo Famulari
2017-03-11 17:21 ` core-updates: Python build failures Leo Famulari
2017-03-11 19:50 ` Marius Bakke
2017-03-12 0:05 ` Leo Famulari
2017-03-12 17:44 ` Marius Bakke
2017-03-13 8:30 ` Ludovic Courtès
2017-03-20 18:41 ` Let’s freeze and build ‘core-updates’! Leo Famulari
2017-03-21 11:16 ` julien lepiller
2017-03-21 17:52 ` Leo Famulari
2017-03-21 21:19 ` Julien Lepiller
2017-03-21 22:02 ` Leo Famulari
2017-03-21 22:02 ` Ricardo Wurmus
2017-03-23 11:08 ` Thomas Danckaert
2017-03-23 12:38 ` Ricardo Wurmus
2017-03-29 13:41 ` Marius Bakke
2017-03-29 14:05 ` Marius Bakke
2017-03-29 20:49 ` Leo Famulari
2017-03-29 20:51 ` Leo Famulari
2017-03-30 6:23 ` Ricardo Wurmus
2017-03-30 8:36 ` Ricardo Wurmus
2017-03-30 9:18 ` Thomas Danckaert
2017-04-01 22:30 ` Ludovic Courtès
2017-04-01 23:09 ` Leo Famulari
2017-04-03 7:43 ` Ricardo Wurmus
2017-04-02 15:20 ` Marius Bakke
2017-04-02 15:42 ` Ricardo Wurmus
2017-04-02 21:23 ` Marius Bakke
2017-04-02 21:18 ` Marius Bakke
2017-04-02 22:39 ` ‘core-updates’ merged! Ludovic Courtès
2017-04-02 21:20 ` Greenisland & SDDM Ludovic Courtès
2017-04-02 21:31 ` Marius Bakke
2017-04-02 22:12 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2019-07-03 17:11 core-updates freeze Marius Bakke
2019-07-11 19:00 ` core-updates frozen! Marius Bakke
2019-07-11 21:06 ` Ludovic Courtès
2019-07-11 23:27 ` Marius Bakke
2019-07-13 22:17 ` Christopher Baines
2020-03-27 19:41 Marius Bakke
2020-03-28 7:33 ` Jan Nieuwenhuizen
2020-03-28 8:20 ` Marius Bakke
2020-03-28 12:35 ` Jan Nieuwenhuizen
2020-03-28 20:05 ` Marius Bakke
2020-03-29 14:53 ` Ludovic Courtès
2020-03-29 17:59 ` Jan Nieuwenhuizen
2020-03-28 8:26 ` Pierre Neidhardt
2020-03-28 12:29 ` Jan Nieuwenhuizen
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=20170227203059.GA2959@jasmine \
--to=leo@famulari.name \
--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.