From: Marius Bakke <mbakke@fastmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Let's merge staging!
Date: Mon, 03 Jun 2019 17:10:30 +0200 [thread overview]
Message-ID: <87a7ey902h.fsf@devup.no> (raw)
In-Reply-To: <87y32qwr9m.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1170 bytes --]
Ludovic Courtès <ludo@gnu.org> writes:
> Hi!
>
> Marius Bakke <mbakke@fastmail.com> skribis:
>
>> The staging branch has been accumulating updates for a while now.
>> We have Mesa 19, Sphinx 2.0, GStreamer 1.16, ALSA 1.1.9, as well as some
>> Python updates. See `git shortlog -n master..staging` for the scoop.
>>
>> I suggest we "freeze" (meaning no further updates, only bugfixes) this
>> branch tomorrow at midnight UTC, and then merge it once the CI lights
>> are green.
>>
>> Anything missing before the freeze?
>
> Not from me, go for it! You can monitor:
>
> guix weather -c10
>
> or similar for that branch.
The weather looks good (< 5% missing substitutes). I pushed a merge of
master just now to try and gain a better understanding of what is
missing before actually merging it.
I suspect it's just the changes from 'master' since it was previously
merged to staging a while back, but Cuirass still is not as convenient
as Hydra for finding regressions, so better safe than sorry.
I will merge it later today if things look OK.
Note to self: it would be good to have more frequent merges during the
freeze period.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-06-03 15:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-25 11:06 Let's merge staging! Marius Bakke
2019-05-25 18:15 ` Arun Isaac
2019-05-26 6:31 ` Marius Bakke
2019-05-26 18:55 ` Arun Isaac
2019-05-28 15:08 ` Ludovic Courtès
2019-06-03 15:10 ` Marius Bakke [this message]
2019-06-03 17:02 ` Pierre Neidhardt
2019-06-03 18:10 ` Marius Bakke
2019-06-03 18:31 ` Pierre Neidhardt
2019-06-03 18:44 ` Marius Bakke
2019-06-05 14:13 ` 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=87a7ey902h.fsf@devup.no \
--to=mbakke@fastmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@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.