On 06/05/2018 10:43 AM, Andres Freund wrote:
> 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.
>
Maybe we should just move everything that was there on say May 1 and not
accept anything new for July.
I note a substantial number of items in the bug fix category. It would
certainly be good to reduce that. On a positive note, as a result of
adding the new committers, quite a large number of patches now have a
committer as author and/or reviewer. So I'm somewhat hopeful we can
clear away a lot of the deadwood in July.
cheers
andrew
--
Andrew Dunstan https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services