[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Changes to the branching workflow

From: zimoun
Subject: Re: Changes to the branching workflow
Date: Thu, 04 Mar 2021 23:01:59 +0100

Hi, Chris,

On Thu, 04 Mar 2021 at 16:05, Christopher Lemmer Webber 
<> wrote:

> I wonder if we should formalize it.  What about adding a section to the 
> "Contributing" section of the manual explaining what the different
> branches are, and when you have a patch that's been approved, when to
> push it to which branch?

Do you mean something like #8 in [1] and then [2]?

1: <>
2: <>

In [2], it reads:

        For patches that just add a new package, and a simple one, it’s
        OK to commit, if you’re confident (which means you successfully
        built it in a chroot setup, and have done a reasonable copyright
        and license auditing). Likewise for package upgrades, except
        upgrades that trigger a lot of rebuilds (for example, upgrading
        GnuTLS or GLib).

which I understand as: the ’staging’ or ’core-update’ patches should go
to guix-patches and not be pushed directly.  Especially when one has
commit access and does not follow closely enough to know the status of
the very branch.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]