unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: Leo Famulari <leo@famulari.name>,
	Felix Lechner <felix.lechner@lease-up.com>,
	guix-devel@gnu.org
Subject: Re: Branch and release process
Date: Wed, 15 Mar 2023 14:37:39 +0100	[thread overview]
Message-ID: <ZBHKI0nM4LqUNKLp@jurong> (raw)
In-Reply-To: <87o7oujg1v.fsf@gmail.com>

Am Wed, Mar 15, 2023 at 09:32:44AM -0400 schrieb Maxim Cournoyer:
> 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?

Exactly!

Andreas



  reply	other threads:[~2023-03-15 13:37 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             ` Branch and release process Maxim Cournoyer
2023-03-15 13:37               ` Andreas Enge [this message]
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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZBHKI0nM4LqUNKLp@jurong \
    --to=andreas@enge.fr \
    --cc=felix.lechner@lease-up.com \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    --cc=maxim.cournoyer@gmail.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).