unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ian Eure <ian@retrospec.tv>
To: Christopher Baines <mail@cbaines.net>
Cc: "Sergio Pastor Pérez" <sergio.pastorperez@outlook.es>,
	guix-devel <guix-devel@gnu.org>
Subject: Re: Request for assistance maintaining LibreWolf
Date: Mon, 19 Aug 2024 16:14:32 -0700	[thread overview]
Message-ID: <87ed6k3wqh.fsf@meson> (raw)
In-Reply-To: <87frr0q4fo.fsf@cbaines.net>


Christopher Baines <mail@cbaines.net> writes:

> [[PGP Signed Part:Undecided]]
> Ian Eure <ian@retrospec.tv> writes:
>
>>> We've had for many months a feature in QA [1] where people can 
>>> mark
>>> patches as being reviewed and looking like they're ready to be
>>> merged,
>>> which is personally what I hope will mitigate this feeling of 
>>> "I
>>> cannot
>>> help you since I don't have commit access", because you can 
>>> help,
>>> you
>>> can review the patches and if you think they're ready to 
>>> merge, you
>>> can
>>> record that, and this does help highlight patches that are 
>>> ready to
>>> merge.
>>>
>>
>> Yes, I’ve used it before.  Unfortunately, it doesn’t appear to 
>> be
>> making a material difference, as the size of the backlog 
>> continues to
>> grow[1].  Progress on this problem would result in the backlog
>> decreasing.  It doesn’t matter how many reviewers say it looks 
>> good --
>> a committer is required to actually push the changes.
>
> I think it's unfair to say it's not making a difference, I 
> really rely
> on it at least. I also think measuring the backlog and using 
> that as the
> success metric is unwise, what we really want is an increase in
> throughput.
>

Throughput of patch review is useless without considering the rate 
of new issues opened.  It doesn’t matter how much review 
throughput increases if the new issue rate increases faster.  What 
the graphs show is that the backlog has a trend of years-long 
growth -- that only happens when the open rate exceeds the close 
rate.  The problem will continue to grow as long as that remains 
the case.

Thanks,

  — Ian



  reply	other threads:[~2024-08-19 23:43 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-17 16:44 Request for assistance maintaining LibreWolf Ian Eure
2024-08-17 18:00 ` Sergio Pastor Pérez
2024-08-17 19:43   ` Ian Eure
2024-08-18  8:35   ` Christopher Baines
2024-08-18 16:50     ` Ian Eure
2024-08-19  1:53       ` Suhail Singh
2024-08-19  8:53       ` Christopher Baines
2024-08-19 23:14         ` Ian Eure [this message]
2024-09-12  1:01           ` Maxim Cournoyer
2024-08-19 17:01     ` Sergio Pastor Pérez
2024-08-18  8:37   ` Attila Lendvai
2024-08-18  9:07     ` Lars-Dominik Braun
2024-08-17 20:36 ` Ian Eure
2024-08-17 23:08 ` Suhail Singh
2024-08-18  4:07   ` Ian Eure
2024-08-18 21:17     ` Tomas Volf
2024-08-21 20:54       ` Ludovic Courtès
2024-08-22 15:00         ` Ian Eure
2024-08-28 20:48           ` Ludovic Courtès
2024-08-28 23:15             ` Ian Eure
2024-08-29  7:30               ` Tobias Geerinckx-Rice
2024-08-29 20:24                 ` [Browser-Team] " André Batista
2024-08-30 20:14                   ` Ludovic Courtès
2024-08-22 16:37         ` André Batista
2024-08-28 20:46           ` Ludovic Courtès
2024-08-30 20:18             ` Defining the role of teams Ludovic Courtès
2024-08-28 23:16           ` Request for assistance maintaining LibreWolf Ian Eure
     [not found] <mailman.5970.1723926982.21382.guix-devel@gnu.org>
2024-08-18  0:11 ` Andy Tai
2024-08-18  0:48   ` Ian Eure

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=87ed6k3wqh.fsf@meson \
    --to=ian@retrospec.tv \
    --cc=guix-devel@gnu.org \
    --cc=mail@cbaines.net \
    --cc=sergio.pastorperez@outlook.es \
    /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).