GNU bug report logs - #75246
Request for merging "python-team" branch

Previous Next

Full log

Message #50 received at 75246 <at> debbugs.gnu.org (full text, mbox):

From: "jgart" <jgart <at> dismail.de>
To: "Leo Famulari" <leo <at> famulari.name>, "Ricardo Wurmus" <rekado <at> elephly.net>
Cc: Sharlatan Hellseher <sharlatanus <at> gmail.com>,
 Munyoki Kilyungi <me <at> bonfacemunyoki.com>, 75246 <at> debbugs.gnu.org,
 Lars-Dominik Braun <lars <at> 6xq.net>, Marius Bakke <marius <at> gnu.org>,
 Tanguy Le Carrour <tanguy <at> bioneland.org>
Subject: Re: [bug#75246] Request for merging "python-team" branch
Date: Fri, 17 Jan 2025 20:42:41 +0000

[Message part 1 (text/plain, inline)]

> 
> I think it's okay to trade "new with some failures" for "old with some
> failures" on the master branch. At least there will be more help to fix
> them.
> 
If this the state that we are already in on master then sounds good to me.

In the future, it would be great to have some hooks in place to prevent people from pushing updates to master that break packages or cause too many rebuilds.

In other words, I don't think we should be allowed to push commits to master that break the package graph accidentally.

How can we make such a thing happen? I don't have an answer at the moment :)

all best,

jgart

[Message part 2 (text/html, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.