Re: Commitfest 2024-01 first week update - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Commitfest 2024-01 first week update
Date
Msg-id CAA4eK1J8_h0O3ud7q5gAwu-Xzh0UVrSeqEGi19j2qGbHjSokhw@mail.gmail.com
Whole thread Raw
In response to Re: Commitfest 2024-01 first week update  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-hackers
On Wed, Feb 7, 2024 at 6:07 PM Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
>
> On 2024-Feb-04, vignesh C wrote:
>
> > We should do something about these kinds of entries, there were few
> > suggestions like tagging under a new category or so, can we add a new
> > status to park these entries something like "Waiting for direction".
> > The threads which have no discussion for 6 months or so can be flagged
> > to this new status and these can be discussed in one of the developer
> > meetings or so and conclude on these items.
>
> Maybe a new status is appropriate ... I would suggest "Stalled".  Such a
> patch still applies and has no pending feedback, but nobody seems
> interested.  Making a patch no longer stalled means there's discussion
> that leads to:
>
> 1. further development?  Perhaps the author just needed more direction.
> 2. a decision that it's not a feature we want, or maybe not in this
>    form.  Then we close it as rejected.
> 3. a reviewer/committer finding time to provide additional feedback.
>

+1. This suggestion sounds reasonable. I think we probably need to
decide the time when the patch's status should be changed to
"Stalled".

--
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: Jelte Fennema-Nio
Date:
Subject: Re: Possibility to disable `ALTER SYSTEM`
Next
From: Peter Eisentraut
Date:
Subject: What about Perl autodie?