On 7/8/24 11:38, Joe Conway wrote:
On 7/3/24 12:51, Andrey M. Borodin wrote:
On 3 Jul 2024, at 01:08, Corey Huinker wrote:
I'll give it a shot.
Great, thank you! Do you have extended access to CF? Like activity log and
mass-mail functions?
If no I think someone from PG_INFRA can grant you n
On 7/3/24 12:51, Andrey M. Borodin wrote:
On 3 Jul 2024, at 01:08, Corey Huinker wrote:
I'll give it a shot.
Great, thank you! Do you have extended access to CF? Like activity log and
mass-mail functions?
If no I think someone from PG_INFRA can grant you necessary access.
I can do that, al
On 7/3/24 18:51, Andrey M. Borodin wrote:
>
>
>> On 3 Jul 2024, at 01:08, Corey Huinker
>> wrote:
>>
>> I'll give it a shot.
>
> Great, thank you! Do you have extended access to CF? Like activity
> log and mass-mail functions? If no I think someone from PG_INFRA can
> grant you necessary acces
> On 3 Jul 2024, at 01:08, Corey Huinker wrote:
>
> I'll give it a shot.
Great, thank you! Do you have extended access to CF? Like activity log and
mass-mail functions?
If no I think someone from PG_INFRA can grant you necessary access.
> On 3 Jul 2024, at 20:21, Tomas Vondra wrote:
>
>
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
I'll give it a shot.
On Mon, Jul 1, 2024 at 4:16 PM Kirill Reshke wrote:
> > Postgres 17
> 18
>
>
>
> Postgres 17
18
Hello everyone!
As Michael noted in e26810d01d4 [0] hacking for Postgres 17 has begun.
I’ve skimmed through hackers@ list. And it seems that so far role of the
commitfest manager is vacant.
Is anyone up for doing this community work? Make things moving :)
Best regards, Andrey Borodin.
[0] htt
