Re: Triage on old commitfest entries

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Triage on old commitfest entries
Date: 2021-10-06 14:41:43
Message-ID: CA+TgmoY9hyv2zOVLrbM69=w5eQCrKK9UZF+_d4odr2YyA=qhew@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Oct 5, 2021 at 12:56 PM Jaime Casanova
<jcasanov(at)systemguards(dot)com(dot)ec> wrote:
> > > psql - add SHOW_ALL_RESULTS option 11
> > > Last substantive discussion 2021-09, currently passing cfbot
> > >
> > > This got committed and reverted once already. I have to be
> > > suspicious of whether this is a good design.
> > >
> >
> > No activity after last patch
> >
>
> Moved to next CF

This seems like the kind of thing we should not do. Patches without
activity need to be aggressively booted out of the system. Otherwise
they just generate a lot of noise that makes it harder to identify
patches that should be reviewed and perhaps committed.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2021-10-06 14:44:44 Re: Extension relocation vs. schema qualification
Previous Message Tom Lane 2021-10-06 14:34:45 Re: Improved tab completion for PostgreSQL parameters in enums