Re: Commitfest closing

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Greg Stark <stark(at)mit(dot)edu>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Commitfest closing
Date: 2022-03-31 21:19:26
Message-ID: 840346.1648761566@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> On Mar 31, 2022, at 4:47 PM, Greg Stark <stark(at)mit(dot)edu> wrote:
>> So the last commitfest often runs over and "feature freeze" isn't
>> scheduled until April 7. Do committers want to keep the commitfest
>> open until then? Or close it now and focus it only on a few pending
>> features they're already working on?

> In past years the CF has been kept open. Let’s stick with that.

Yeah, I was assuming it would stay open till late next week.

We do have at least two patches in the queue that we want to put in
after everything else: my frontend logging patch, and the
PGDLLIMPORT-for-everything patch that I believe Robert has taken
responsibility for. So if we want those in before the nominal
feature freeze, other stuff is going to need to be done a day or
so beforehand. But that still gives us most of a week.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2022-03-31 21:20:51 Re: Extensible Rmgr for Table AMs
Previous Message Tom Lane 2022-03-31 21:12:33 Re: proposal: enhancing plpgsql debug API - returns text value of variable content