Re: Commitfest 2023-03 starting tomorrow!

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Greg Stark <stark(at)mit(dot)edu>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Commitfest 2023-03 starting tomorrow!
Date: 2023-03-01 06:47:17
Message-ID: Y/709fpWZqxsA5uG@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Feb 28, 2023 at 01:45:27PM -0500, Greg Stark wrote:
> So I'm not sure if I'll be CFM this month but I'm assuming I will be
> at this point....

Okay, that's OK for me! Thanks for helping out.

> The next pass would be to grab any patches not marked Ready for
> Committer and if they look like they'll need more than a one round of
> feedback and a couple weeks to polish they'll probably get bounced to
> the next commitfest too. It sucks not getting feedback on your patches
> for so long but there are really just sooo many patches and so few
> eyeballs... It would be great if people could do initial reviews of
> these patches before we bounce them because it really is discouraging
> for developers to send patches and not get feedback. But realistically
> it's going to happen to a lot of patches.

I don't have many patches registered this time for the sole reason of
being able to spend more cycles on reviews and see what could make the
cut. So we'll see how it goes, I guess..

The CF would begin in more or less 5 hours as of the moment of this
message:
https://www.timeanddate.com/time/zones/aoe
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Julien Rouhaud 2023-03-01 06:55:27 Re: pg_upgrade and logical replication
Previous Message John Naylor 2023-03-01 06:37:01 Re: [PoC] Improve dead tuple storage for lazy vacuum