GNU bug report logs - #60042
[PATCH] gnu: git: Update to 2.39.0.

Previous Next

Full log

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

From: Greg Hogan <code <at> greghogan.com>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 60042 <at> debbugs.gnu.org, zimoun <zimon.toutoune <at> gmail.com>
Subject: Re: bug#60042: [PATCH] gnu: git: Update to 2.39.0.
Date: Tue, 20 Dec 2022 11:38:40 -0500

On Tue, Dec 20, 2022 at 9:52 AM Ludovic Courtès <ludo <at> gnu.org> wrote:
> According to figures in the manual, it’s for ‘staging’ (info "(guix)
> Submitting Patches").  But I guess those figures are less appropriate
> now that the package collection and build farms have grown.  We’ll have
> to think about it!

I closed this ticket after noticing that Tobias had hotfixed the
update to the staging branch.

In addition to potentially increasing the dependent package
thresholds, we should consider alternatives to the process for
submitting, reviewing, and testing the patches for staging and
core-updates. I think just having an announced window for submissions
(perhaps 1 week for staging and 2 weeks for core-updates) would
eliminate some unnecessary work. There would be little benefit to
submitting simple package updates before the open window when an even
newer release may still become available. Also, this could encourage
more participation in the validation and testing process: similar to
how releases are branched off master, we could encourage developers
and users to test the pre-merge staging and (especially) core-updates.

Previous Next

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