Re: Commit Fest 2019-01 is now closed - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: Commit Fest 2019-01 is now closed
Date
Msg-id CAH2-Wzkwhdm5A8Su5NL4SjjYDFTXgG_SnQvF_omHMe543rctWg@mail.gmail.com
Whole thread Raw
In response to Re: Commit Fest 2019-01 is now closed  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On Thu, Feb 7, 2019 at 4:02 AM Andres Freund <andres@anarazel.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


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Allow some recovery parameters to be changed with reload
Next
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS][PATCH] Applying PMDK to WAL operations for persistentmemory