| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Gregory Stark (as CFM)" <stark(dot)cfm(at)gmail(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Commitfest 2023-03 starting tomorrow! |
| Date: | 2023-04-09 01:50:49 |
| Message-ID: | 3673629.1681005049@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Gregory Stark (as CFM)" <stark(dot)cfm(at)gmail(dot)com> writes:
> Some of these, especially the last category, are challenging for me to
> determine. If I move forward a patch of yours that you think makes
> sense to treat as an open issue that should be resolved in this
> release then feel free to say.
I think that's largely independent. We don't look back at closed-out CFs
as a kind of TODO list; anything that's left behind there is basically
never going to be seen again, until the author makes a new CF entry.
Anything that's to be treated as an open item for v16 should get added
to the wiki page at
https://wiki.postgresql.org/wiki/PostgreSQL_16_Open_Items
It's not necessary that a patch exist to do that.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-04-09 01:54:38 | Re: Proposal: %T Prompt parameter for psql for current time (like Oracle has) |
| Previous Message | Gregory Stark (as CFM) | 2023-04-09 01:45:04 | Re: Commitfest 2023-03 starting tomorrow! |