Re: Commitfest 2024-01 first week update

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: vignesh C <vignesh21(at)gmail(dot)com>, Daniel Gustafsson <daniel(at)yesql(dot)se>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Commitfest 2024-01 first week update
Date: 2024-02-07 13:51:53
Message-ID: CAA4eK1J8_h0O3ud7q5gAwu-Xzh0UVrSeqEGi19j2qGbHjSokhw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Feb 7, 2024 at 6:07 PM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)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.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2024-02-07 14:05:16 What about Perl autodie?
Previous Message Jelte Fennema-Nio 2024-02-07 13:49:01 Re: Possibility to disable `ALTER SYSTEM`