Re: Triage on old commitfest entries - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Triage on old commitfest entries
Date
Msg-id CA+TgmoY9hyv2zOVLrbM69=w5eQCrKK9UZF+_d4odr2YyA=qhew@mail.gmail.com
Whole thread Raw
In response to Re: Triage on old commitfest entries  (Jaime Casanova <jcasanov@systemguards.com.ec>)
List pgsql-hackers
On Tue, Oct 5, 2021 at 12:56 PM Jaime Casanova
<jcasanov@systemguards.com.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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Improved tab completion for PostgreSQL parameters in enums
Next
From: Robert Haas
Date:
Subject: Re: Extension relocation vs. schema qualification