[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: branch master updated (2bea3f2562 -> 6745d692d4)
From: |
Ricardo Wurmus |
Subject: |
Re: branch master updated (2bea3f2562 -> 6745d692d4) |
Date: |
Fri, 10 May 2024 14:36:16 +0200 |
User-agent: |
mu4e 1.12.4; emacs 29.3 |
Christopher Baines <mail@cbaines.net> writes:
> Ricardo Wurmus <rekado@elephly.net> writes:
>
>>> These changes from r-updates have effectively jumped the queue past
>>> those on the core-updates and gnome-team branches, and since there was
>>> never a "Request for merging" issue opened [1], the bordeaux build farm
>>> is going to be delayed in building gnome-team as it tries to catch up
>>> with master.
>>>
>>> 1:
>>> https://guix.gnu.org/manual/devel/en/html_node/Managing-Patches-and-Branches.html
>>
>> Oh, this is new to me. I've just read it. (Good to know also for the
>> upcoming merge of the python-team branch!)
>>
>> My apologies for not following this process for r-updates. I'm hearing
>> about this for the first time now. (I hope the previous wip-python-team
>> didn't cause too many problems for bordeaux.)
>
> Is there anything you can think of that can be done to better
> communicate about process changes in the future?
Simon proposed an RFC process, which presumably would also result in
RFC-specific announcements separate from the deluge of emails on
guix-devel, which I cannot keep up with.
--
Ricardo