all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: Felix Lechner <felix.lechner@lease-up.com>,  guix-devel@gnu.org
Subject: Re: Branch and release process
Date: Wed, 15 Mar 2023 09:32:44 -0400	[thread overview]
Message-ID: <87o7oujg1v.fsf@gmail.com> (raw)
In-Reply-To: <ZBGt6zFct4IRjxfk@3900XT> (Efraim Flashner's message of "Wed, 15 Mar 2023 13:37:15 +0200")

Hi Efraim,

Efraim Flashner <efraim@flashner.co.il> writes:

> On Tue, Mar 14, 2023 at 11:30:52PM -0400, Maxim Cournoyer wrote:
>> Hi,
>> 
>> Leo Famulari <leo@famulari.name> writes:
>> 
>> > On Tue, Mar 14, 2023 at 09:10:33PM -0400, Maxim Cournoyer wrote:
>> >> Felix Lechner <felix.lechner@lease-up.com> writes:
>> >> > With the core-updates process now abandoned, I retitled the issue to
>> >> 
>> >> Could you share the reference of that?  I'm not against it, but our
>> >> currently documented process still mention the good old staging and
>> >> core-updates branches.
>> >
>> > At the Guix Days in February, we discussed the branching workflow and
>> > reached a rough consensus that for non-core packages (defined in
>> > %core-packages), we should try to adopt a more targeted "feature branch"
>> > workflow. That's actually what we used to do, before we outgrew our old
>> > build farm, after which we were barely able to build one branch at a
>> > time (IIRC, we would stop building master in order to build core-updates
>> > or staging).
>> >
>> > The discussion was summarized by Andreas here:
>> >
>> > https://lists.gnu.org/archive/html/guix-devel/2023-02/msg00066.html
>> 
>> Thanks!  I had missed it.  It sounds promising!
>> 
>> > Currently we are demo-ing this workflow in the wip-go-updates branch and
>> > go-team Cuirass jobset.
>> 
>> So the review happens first on the ML, then the changes land to the team
>> branch, and then finally the feature branch gets merged to master?  If
>> the review has already happened and the package been tested (and built
>> by QA), why is a feature branch needed?
>
> So we can group a couple of larger related changes together.

I see; so it'd be useful for the integration of package changes
impacting multiple others; some kind of staging or core-updates
topic-focused branches.  Simple leaf package updates could still be
merged directly to master without going through the go-team branch,
right?

-- 
Thanks,
Maxim


  reply	other threads:[~2023-03-15 13:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-13  1:26 gnu: inetutils: Update to 2.4 Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-03-14 15:52 ` Maxim Cournoyer
2023-03-14 16:37   ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-03-14 19:49     ` Andreas Enge
2023-03-15  1:10     ` Maxim Cournoyer
2023-03-15  2:49       ` Leo Famulari
2023-03-15  3:30         ` Branch and release process (was: gnu: inetutils: Update to 2.4.) Maxim Cournoyer
2023-03-15 11:37           ` Efraim Flashner
2023-03-15 13:32             ` Maxim Cournoyer [this message]
2023-03-15 13:37               ` Branch and release process Andreas Enge
2023-03-15 11:56           ` Branch and release process (was: gnu: inetutils: Update to 2.4.) Leo Famulari
2023-03-15 12:04             ` Christopher Baines
2023-03-15  7:48       ` gnu: inetutils: Update to 2.4 Andreas Enge
2023-03-15 13:37         ` Maxim Cournoyer
2023-03-16 20:43       ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-03-17 16:32         ` 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=87o7oujg1v.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=felix.lechner@lease-up.com \
    --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 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.