unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: Staging freeze
Date: Wed, 04 Jan 2017 23:31:28 +0100	[thread overview]
Message-ID: <87shoyfoe7.fsf@gnu.org> (raw)
In-Reply-To: <20170104084505.GB5126@jasmine> (Leo Famulari's message of "Wed, 4 Jan 2017 03:45:05 -0500")

Leo Famulari <leo@famulari.name> skribis:

> On Fri, Dec 23, 2016 at 12:23:39AM -0500, Leo Famulari wrote:
>> The last staging branch was merged into the master branch on December
>> 11.
>> 
>> According to the 3 week staging cycle we are trying to adhere to [0],
>> this would mean we freeze the current branch on December 25 and try to
>> merge it on January 1.
>> 
>> These dates are inconvenient for many people. I propose we freeze the
>> branch and start building on December 27, and try to merge on January 3.
>
> Update:
>
> We are having some issues with the armhf and mips64el build machines
> that are keeping us from building all the packages.

That should be more or less solved.

I’ve just merged ‘master’ into ‘staging’ and started a new evaluation.

Ludo’.

  reply	other threads:[~2017-01-04 22:31 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-23  5:23 Staging freeze Leo Famulari
2016-12-23  6:00 ` John Darrington
2016-12-26 18:16   ` Leo Famulari
2016-12-27 23:56 ` Leo Famulari
2016-12-28  4:13   ` Leo Famulari
2016-12-28  9:17     ` John Darrington
2016-12-29 17:16       ` Leo Famulari
2016-12-29 17:51       ` Ludovic Courtès
2016-12-29 18:42         ` Leo Famulari
2016-12-31 11:12           ` Ludovic Courtès
2017-01-04  8:45 ` Leo Famulari
2017-01-04 22:31   ` Ludovic Courtès [this message]
2017-01-07 11:50     ` Let’s fix build failures on ‘staging’! Ludovic Courtès
2017-01-07 17:15       ` Fix python-pygpgme FTBFS [was Re: Let’s fix build failures on ‘staging’!] Leo Famulari
2017-01-07 21:31         ` Ludovic Courtès
2017-01-07 21:46           ` Leo Famulari
2017-01-07 17:22       ` Let’s fix build failures on ‘staging’! Leo Famulari
2017-01-07 17:35       ` Leo Famulari
2017-01-07 21:32         ` Ludovic Courtès
2017-01-07 21:46           ` Leo Famulari
2017-01-08 17:19       ` Leo Famulari
2017-01-07 18:10     ` [PATCH 1/2] Revert "gnu: Add threaded variants of fftw and fftwf for Ardour and mod-host." David Craven
2017-01-07 18:10       ` [PATCH 2/2] gnu: ardour: Add eudev dependency David Craven
2017-01-07 19:11       ` [PATCH 1/2] Revert "gnu: Add threaded variants of fftw and fftwf for Ardour and mod-host." Ricardo Wurmus
2017-01-07 22:43         ` David Craven
2017-01-07 22:45           ` David Craven
2017-01-08 10:57             ` Ludovic Courtès
2017-01-08  7:23           ` Ricardo Wurmus
  -- strict thread matches above, loose matches on Subject: below --
2020-10-13 21:54 staging freeze Marius Bakke
2020-10-13 21:57 ` Julien Lepiller
2020-10-13 22:28   ` Marius Bakke
2020-10-15 12:33 ` zimoun

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=87shoyfoe7.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /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).