From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | vignesh C <vignesh21(at)gmail(dot)com> |
Cc: | 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 12:37:29 |
Message-ID: | 202402071237.komah6yafast@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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.
--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
"The problem with the future is that it keeps turning into the present"
(Hobbes)
From | Date | Subject | |
---|---|---|---|
Next Message | Maiquel Grassi | 2024-02-07 12:41:56 | RE: Psql meta-command conninfo+ |
Previous Message | Pavel Luzanov | 2024-02-07 12:35:34 | Re: Psql meta-command conninfo+ |