all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: "jgart" <jgart@dismail.de>
Cc: tanguy@bioneland.org,
	"Sharlatan Hellseher" <sharlatanus@gmail.com>,
	rprior@protonmail.com, me@bonfacemunyoki.com,
	"Ludovic Courtès" <ludo@gnu.org>,
	71408@debbugs.gnu.org, lars@6xq.net, marius@gnu.org,
	"Nicolas Graves" <ngraves@ngraves.fr>
Subject: [bug#71408] Request for merging "python-team" branch
Date: Wed, 19 Jun 2024 14:45:22 +0100	[thread overview]
Message-ID: <87tthp3v2l.fsf@cbaines.net> (raw)
In-Reply-To: <330818cb39329dd4ded9d263f69d26e306b25f31@dismail.de> (jgart@dismail.de's message of "Tue, 18 Jun 2024 20:46:47 +0000")

[-- Attachment #1: Type: text/plain, Size: 1845 bytes --]

"jgart" <jgart@dismail.de> writes:

> Hi Python Team, Guix Team at large, and Parenphilic Pythonistas,
>
> This long lived python-team branch as of today has a lot of git
> conflicts if you try to rebase and/or merge it on to master.
>
> What do you think if we discuss an alternative team branch policy for
> the future for feature branches that target master?
>
> Here's a tentative proposal, with an example: 
>
> Instead of having a single python-team branch, with a wide variety of
> new Python features, what if we had, a python-team feature branch that
> we work on relatively quickly?
>
> In other words, we avoid long lived branches but try to merge for
> example, a new python-team-sphinx branch as soon as the "Sphinx
> feature" is ready. This python-team-sphinx branch will only contain
> the work required to bump sphinx to the latest version that we'd like
> to support. The reason I use python-sphinx as an example is because
> the python-sphinx package requires a lot of rebuilds across many
> language ecosystems that use Sphinx for documentation purposes.
>
> I think that keeping the team branches focused on a particular team
> sub-feature within that team's scope and not using long-lived and
> largely scoped branches will avoid a ton of frustration trying to fix
> merge conflicts when/before we announce a request to merge.

This aligns with the current (and previous) guidance on managing
branches [1]. Providing there's a consistent topic for the branch, any
name is fine (e.g. python-team-sphinx is fine).

1: https://guix.gnu.org/manual/devel/en/html_node/Managing-Patches-and-Branches.html

I'm also hoping the requirement to create a guix-patches issue
requesting to merge the branch when it's created will help avoid the
long lived branches that we've had over the last year.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]

  parent reply	other threads:[~2024-06-19 13:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-07  8:24 [bug#71408] Request for merging "python-team" branch Christopher Baines
2024-06-08 14:27 ` Ludovic Courtès
2024-06-08 21:04   ` Sharlatan Hellseher
2024-06-18 20:46 ` jgart via Guix-patches via
2024-06-19  7:28   ` Tanguy LE CARROUR
2024-06-19 13:45   ` Christopher Baines [this message]
2024-06-25 17:04     ` jgart via Guix-patches via
2024-06-25 18:06       ` Sharlatan Hellseher via Guix-patches
2024-09-24  7:25         ` Steve George
2024-06-30  7:31       ` Lars-Dominik Braun
2024-06-30  9:42       ` Christopher Baines
2024-09-18  9:09 ` [bug#71408] Postpone? Andreas Enge
2024-09-27  7:30   ` bug#71408: Postpone? Andreas Enge
2024-09-24 13:31 ` [bug#71408] Request for merging "python-team" branch Arseniy Zaostrovnykh
2024-09-26 21:54 ` [bug#71408] Update on Python team pt1 Steve George

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=87tthp3v2l.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --cc=71408@debbugs.gnu.org \
    --cc=jgart@dismail.de \
    --cc=lars@6xq.net \
    --cc=ludo@gnu.org \
    --cc=marius@gnu.org \
    --cc=me@bonfacemunyoki.com \
    --cc=ngraves@ngraves.fr \
    --cc=rprior@protonmail.com \
    --cc=sharlatanus@gmail.com \
    --cc=tanguy@bioneland.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.