From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Commit Fest 2019-01 is now closed |
Date: | 2019-02-07 22:22:25 |
Message-ID: | CAH2-Wzkwhdm5A8Su5NL4SjjYDFTXgG_SnQvF_omHMe543rctWg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Feb 7, 2019 at 4:02 AM Andres Freund <andres(at)anarazel(dot)de> wrote:
> On 2019-02-07 12:53:39 +0100, Peter Eisentraut wrote:
> > What is the meaning of this? If something is meant for 13, shouldn't it
> > be moved to the next commit fest?
>
> Why? There's plenty stuff that's chugging along in development but ought
> to be processed at less urgency / by different people, than the stuff
> targeted to be committed soon. It's already frustrating to contribute to
> postgresql for new people, but if they don't get feedback for half a
> year because they submitted around December / January it's almost
> guaranteed that they vanish.
+1. Let's not disincentivize acknowledging that v13 is the target release.
I also don't think it's a good idea to force patch authors to take a
position. Novice authors are particularly likely to make the wrong
call.
--
Peter Geoghegan
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2019-02-07 22:33:22 | Re: [HACKERS][PATCH] Applying PMDK to WAL operations for persistent memory |
Previous Message | Peter Eisentraut | 2019-02-07 22:06:27 | Re: Allow some recovery parameters to be changed with reload |