unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "jgart" <jgart@dismail.de>
To: "Sharlatan Hellseher" <sharlatanus@gmail.com>,
	"Ricardo Wurmus" <rekado@elephly.net>
Cc: "Lars-Dominik Braun" <lars@6xq.net>,
	"guix-devel" <guix-devel@gnu.org>,
	"Nicolas Graves" <ngraves@ngraves.fr>,
	"Felix Gruber" <felgru@posteo.net>
Subject: Re: Status of python-team branch
Date: Mon, 02 Sep 2024 20:16:50 +0000	[thread overview]
Message-ID: <912c9926608b0d88c96460d00996be52ee99a7a5@dismail.de> (raw)
In-Reply-To: <CAO+9K5oNQpFfBw98K-=DdX_h7Er13Lzaw9ShTh_qW2xBeYYaOw@mail.gmail.com>

> I may volunteer myself to that

Hi Oleg,

Feel free to send a request for merging.

I don't have the bandwidth at the moment to work on fixing that branch.

That said,

I'll be happy to help in approving the team branch and reviewing qa in order to facilitate you merging it.

In the future, I think we should have smaller topic branches. 

For example, we could request to update particular python packages with large rebuilds on a dedicated branch such as python-team-python-sphinx, one request at a time. I think that breaking up the team branch merge request into smaller chunks could help with focusing on getting branches merged and preventing them from growing large or becoming long lived.

If I do large python updates in the future, I will take this approach myself.

Thanks for working on it.

all the best,

jgart

https://whereis.みんな/


      reply	other threads:[~2024-09-02 20:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-12 10:27 Status of python-team branch Sharlatan Hellseher
2024-08-12 16:24 ` Lars-Dominik Braun
2024-08-12 19:42   ` Ricardo Wurmus
2024-09-02 16:00     ` Ricardo Wurmus
2024-09-02 17:45       ` Sharlatan Hellseher
2024-09-02 20:16         ` jgart [this message]

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=912c9926608b0d88c96460d00996be52ee99a7a5@dismail.de \
    --to=jgart@dismail.de \
    --cc=felgru@posteo.net \
    --cc=guix-devel@gnu.org \
    --cc=lars@6xq.net \
    --cc=ngraves@ngraves.fr \
    --cc=rekado@elephly.net \
    --cc=sharlatanus@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).