Re: Commitfest Manager for March

From: "Andrey M(dot) Borodin" <x4mmm(at)yandex-team(dot)ru>
To: wenhui qiu <qiuwenhuifx(at)gmail(dot)com>
Cc: Aleksander Alekseev <aleksander(at)timescale(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Commitfest Manager for March
Date: 2024-04-01 06:16:50
Message-ID: 362E8641-3F2D-41AE-9A30-59B9DF211F1E@yandex-team.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 20 Mar 2024, at 18:13, wenhui qiu <qiuwenhuifx(at)gmail(dot)com> wrote:
>
> Could you take a look at the patch (https://commitfest.postgresql.org/47/4284/),How about your opinion

The patch is currently in the "Ready for Committer" state. It's up to the committer to decide which one to pick. There are 22 proposed patches and many committers are dealing with the consequences of what has already been committed (build farm failures, open issues, post-commit notifications, etc.).
If I was a committer, I wouldn't commit a new join kind at the door of feature freeze. If I was the author of this patch, I'd consider attracting more reviewers and testers to increase chances of the patch in July CF.
Thanks for your work!

Best regards, Andrey Borodin.

PS. Plz post the answer below quoted text. That’s common practice here.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message vignesh C 2024-04-01 06:17:30 Re: Logical replication failure modes
Previous Message Zhijie Hou (Fujitsu) 2024-04-01 06:05:34 RE: Synchronizing slots from primary to standby