all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Josselin Poiret <dev@jpoiret.xyz>
Cc: guix-devel <guix-devel@gnu.org>,
	 GNU Guix maintainers <guix-maintainers@gnu.org>
Subject: Re: staging merge into master
Date: Wed, 12 Apr 2023 21:26:18 -0400	[thread overview]
Message-ID: <87leiwlghx.fsf@gmail.com> (raw)
In-Reply-To: <87y1mwu7dp.fsf@jpoiret.xyz> (Josselin Poiret's message of "Wed,  12 Apr 2023 23:18:26 +0200")

Hello,

Josselin Poiret <dev@jpoiret.xyz> writes:

> Hi Maxim,
>
> Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
>
>> Hello,
>>
>> I'm planning to merge staging into master soon (tomorrow or friday),
>> unless someone has a problem with it.  It includes at least two CVE
>> fixes as well as a bunch of updates such as a newer gstreamer, ffmpeg,
>> qt 5, python-cryptography and a few others, and seems to be close to
>> master in terms of coverage (currently 68% for staging vs 73% for
>> master, according to https://ci.guix.gnu.org/).
>>
>> I was able to reconfigure my system with it, and haven't seen issues so
>> far.  Testing welcome!
>
> I'm a bit conflicted on this one, as:
> + this could let us get rid of staging as well!
> + this might fix some build issues and package errors on core-updates
> (as well as fix CVEs!)
> - this might create some build issues and package errors on core-updates
> - we might not have time for a full CI run on core-updates before this
> week-end.
>
> I don't have a particularly strong opinion either way, but if you do
> merge it, could you make sure to also merge master into c-u and launch a
> CI evaluation right afterwards?  Thanks for taking care of staging!

Sounds good.  If I feel confident tomorrow I'll merge it to master and
tackle the probably tricky merge to core-updates at the same time.

Thanks for tipping in along with Andreas!

-- 
Thanks,
Maxim


  parent reply	other threads:[~2023-04-13  1:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-12 20:38 staging merge into master Maxim Cournoyer
2023-04-12 21:18 ` Josselin Poiret
2023-04-12 21:27   ` Andreas Enge
2023-04-13  9:26     ` Simon Tournier
2023-04-13  1:26   ` Maxim Cournoyer [this message]
2023-04-12 21:20 ` Andreas Enge
2023-04-13  1:27   ` Maxim Cournoyer

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=87leiwlghx.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=dev@jpoiret.xyz \
    --cc=guix-devel@gnu.org \
    --cc=guix-maintainers@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.