Re: Commitfest overflow

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Greg Stark <stark(at)mit(dot)edu>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Commitfest overflow
Date: 2021-08-04 01:49:23
Message-ID: CA+hUKGJ=JQvhNy-zt3LUgJequAymdWaGXfGzZxOJ7MVNzJ7tgA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Aug 4, 2021 at 8:23 AM Greg Stark <stark(at)mit(dot)edu> wrote:
> On Tue, 3 Aug 2021 at 11:56, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>
> > I wonder if our lack of in-person developer meetings is causing some of
> > our issues to not get closed.
>
> That's an interesting thought. Every year there are some especially
> contentious patches that don't get dealt with until the in-person
> meeting which pushes people to make a call. However it seems like
> that's only a handful and not really enough to explain the volume.

I think there might be a higher number of work-in-progress patches
these days, which represent ongoing collaborative efforts, and are not
expected to be committed soon, but are registered to attract the
attention of humans and robots. Perhaps if there were a separate
status for that, it would be clearer. Or perhaps they don't belong in
the "commit" fest.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2021-08-04 01:51:25 Re: Lowering the ever-growing heap->pd_lower
Previous Message Andres Freund 2021-08-04 01:33:08 Re: Slow standby snapshot