| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Greg Stark <stark(at)mit(dot)edu>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Commitfest Update |
| Date: | 2022-03-30 19:38:59 |
| Message-ID: | 8498f959-e7a5-b0ec-7761-26984e581a51@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 30.03.22 20:41, Greg Stark wrote:
> Patches that are Waiting on Author and haven't had activity in months
> -- traditionally they were set to Returned with Feedback. It seems the
> feeling these days is to not lose state on them and just move them to
> the next CF. I'm not sure that's wise, it ends up just filling up the
> list with patches nobody's working on.
If you set them to Returned with Feedback now, they can still be
reawoken later by setting them to Needs Review and pulling them into the
then-next commit fest. That preserves all the state and context.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2022-03-30 19:44:20 | Re: Higher level questions around shared memory stats |
| Previous Message | Robert Haas | 2022-03-30 19:36:27 | Re: Possible fails in pg_stat_statements test |