| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
| Cc: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, Greg Stark <stark(at)mit(dot)edu>, David Steele <david(at)pgmasters(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>, Daniel Gustafsson <daniel(at)yesql(dot)se>, Jeff Davis <pgsql(at)j-davis(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Commitfest manager for 2022-03 |
| Date: | 2022-02-27 09:02:01 |
| Message-ID: | Yhs+CaSEUaLzyDvX@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Feb 27, 2022 at 04:51:16PM +0800, Julien Rouhaud wrote:
> I don't really understand what that field is supposed to mean. But now that
> we're in the final pg15 commit fest, wouldn't it be simpler to actually move
> the patches for which there's a agreement that they can't make it to pg15?
> Tagging them and letting them rot for a month isn't helpful for the authors or
> the CFMs, especially when there are already 250 patches that needs to be
> handled.
Yes, I don't see any point in having a new tag just to mark patches
that will have to be moved to the next CF anyway. These should just
be moved to the July one rather than stay in the March one.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2022-02-27 09:10:45 | Re: Checkpointer sync queue fills up / loops around pg_usleep() are bad |
| Previous Message | Julien Rouhaud | 2022-02-27 08:51:16 | Re: Commitfest manager for 2022-03 |