Re: Commitfest manager for July 2024

From: Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>
To: Corey Huinker <corey(dot)huinker(at)gmail(dot)com>, Kirill Reshke <reshkekirill(at)gmail(dot)com>
Cc: "Andrey M(dot) Borodin" <x4mmm(at)yandex-team(dot)ru>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Commitfest manager for July 2024
Date: 2024-07-03 15:21:23
Message-ID: f0d7d135-1c59-428b-882a-c2af953ae442@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

This reminded me that one of the changes proposed at pgconf.dev was
having multiple CF managers, each responsible for a subset of the CF
entries. Do we want to do try that?

IIRC the idea was that it's not really feasible to shepherd ~400 patches
(the current count for 2024-07), especially if the person has other
things to do too, and spreading this over multiple people would make it
more manageable - perhaps even allowing more people to participate.

If we wanted to try this, would that require some improvements in the CF
app, e.g. to track which CF manager is responsible for each entry?

regards

--
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Marat Bukharov 2024-07-03 16:04:40 Re: [PATCH] Add min/max aggregate functions to BYTEA
Previous Message Tom Lane 2024-07-03 15:16:42 Re: Add a GUC check hook to ensure summarize_wal cannot be enabled when wal_level is minimal