| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | Daniel Gustafsson <daniel(at)yesql(dot)se>, Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: 2021-09 Commitfest |
| Date: | 2021-10-02 15:24:52 |
| Message-ID: | 3691058.1633188292@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> I think if we all agree that this is a desired workflow, then we should
> update the app to allow WoA patches to be moved to next CF.
I'm fairly astonished that anyone would have thought that that
*wasn't* an expected case. For example, if someone reviews a
patch and sets the status to WoA on the last day of the CF,
what then? You can't expect the patch author to respond
instantaneously.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-10-02 15:32:01 | Re: 2021-09 Commitfest |
| Previous Message | Alvaro Herrera | 2021-10-02 15:20:09 | Re: 2021-09 Commitfest |