| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Tomas Vondra <tomas(at)vondra(dot)me>, Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: new commitfest transition guidance |
| Date: | 2025-02-06 17:52:03 |
| Message-ID: | 1a4cd32f444019dac127b3b242599692bedcd411.camel@j-davis.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 2025-02-05 at 19:14 -0500, Peter Geoghegan wrote:
> I just don't think that this new policy makes sense. At least not as
> implemented.
Perhaps the answer is to go in the other direction, and the CF app
would just be a patch tracker without specific start and stop dates
(aside from a few deadlines like the feature submission deadline or the
feature freeze deadline)? We very briefly discussed that at the
meeting, as well.
It seems weird to have "new" commitfests but just bring over all of the
patches.
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jacob Brazeal | 2025-02-06 17:57:20 | Re: new commitfest transition guidance |
| Previous Message | Chapman Flack | 2025-02-06 17:08:36 | Re: "Type does not exist" error when returning array of type in non-public schema |