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

From Andres Freund
Subject Re: Commit Fest 2019-01 is now closed
Date
Msg-id 20190207120202.gyryedq5ckmsylsf@alap3.anarazel.de
Whole thread Raw
In response to Re: Commit Fest 2019-01 is now closed  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: Commit Fest 2019-01 is now closed  (Peter Geoghegan <pg@bowt.ie>)
Re: Commit Fest 2019-01 is now closed  (Robbie Harwood <rharwood@redhat.com>)
List pgsql-hackers
Hi,

On 2019-02-07 12:53:39 +0100, Peter Eisentraut wrote:
> On 06/02/2019 21:09, Magnus Hagander wrote:
> > This has now been pushed and is available. I've set it up with stable,
> > 12 and 13 as possible versions for now, but I have not added any tags to
> > the existing patches (except for one, in order to test it).
> 
> 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.  Additionally, there's an increasing amount
of development projects that are too large to complete in a single
cycle, and if we just stop looking at them for half a year, they'll also
not succeed.

Greetings,

Andres Freund


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Commit Fest 2019-01 is now closed
Next
From: Michael Paquier
Date:
Subject: Re: [HACKERS] REINDEX CONCURRENTLY 2.0