From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Schedule of commit fests for PG14 |
Date: | 2020-05-21 14:02:27 |
Message-ID: | 26165.1590069747@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Michael Paquier <michael(at)paquier(dot)xyz> writes:
> Normally $subject would have been discussed at the developer meeting
> in Ottawa, but that's not going to happen per the current situation.
> For the last couple of years, we have been using the same timeline for
> for commit fests in a development cycle, so why not going with the
> same flow this year? This would mean 5 CFs:
> - 2020-07-01~2020-07-31
> - 2020-09-01~2020-09-30
> - 2020-11-01~2020-11-30
> - 2021-01-01~2021-01-31
> - 2021-03-01~2021-03-31
Yeah, nobody's expressed any great unhappiness with the schedule
recently, so let's just do the same thing again this year.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | David Steele | 2020-05-21 14:13:41 | Re: Schedule of commit fests for PG14 |
Previous Message | Robert Haas | 2020-05-21 13:41:54 | Re: WIP/PoC for parallel backup |