Re: commitfest 2018-07 - Mailing list pgsql-hackers

From Andres Freund
Subject Re: commitfest 2018-07
Date
Msg-id 20180605144330.7twel6h43tvwygaz@alap3.anarazel.de
Whole thread Raw
In response to Re: commitfest 2018-07  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: commitfest 2018-07
Re: commitfest 2018-07
List pgsql-hackers
On 2018-06-05 10:20:55 -0400, Tom Lane wrote:
> Andres Freund <andres@anarazel.de> writes:
> > I'd rather create a new 2018-07, and just manually move old patches to
> > it. Otherwise we'll not really focus on the glut of old things, but
> > everyone just restarts working on their own new thing.
> 
> I thought the idea was to clear out the underbrush of small, ready-to-go
> patches.  How old they are doesn't enter into that.
> 
> There's a separate issue about what to do to prioritize old patches so
> they don't linger indefinitely.  We had a discussion about that at the
> dev meeting, but I don't think any specific mechanism was agreed to?

I think we've not fully agreed on that.  I'd argue we should manually
filter things into the next CF. And both small patches and older things
should qualify.

Greetings,

Andres Freund


pgsql-hackers by date:

Previous
From: Amit Khandekar
Date:
Subject: Re: Concurrency bug in UPDATE of partition-key
Next
From: Joe Conway
Date:
Subject: Re: commitfest 2018-07