Re: September 2015 Commitfest - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: September 2015 Commitfest
Date
Msg-id CAB7nPqScG6CnaX29sc8TpFFNa6nkG7OxDKJgneQdn4AT2vkyZw@mail.gmail.com
Whole thread Raw
In response to Re: September 2015 Commitfest  (Andres Freund <andres@anarazel.de>)
Responses Re: September 2015 Commitfest  (Robert Haas <robertmhaas@gmail.com>)
Re: September 2015 Commitfest  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On Sat, Oct 31, 2015 at 12:55 AM, Andres Freund <andres@anarazel.de> wrote:
> On 2015-10-31 00:42:54 +0100, Michael Paquier wrote:
>> On Fri, Oct 30, 2015 at 2:02 PM, Robert Haas wrote:
>> > On Fri, Oct 30, 2015 at 10:47 AM, Michael Paquier wrote:
>> >> On Thu, Oct 22, 2015 at 9:21 AM, Andres Freund wrote:
>> >>>> Among the five patches marked as ready for committer, one is a bug fix
>> >>>> that should be back-patched (ahem). Shouldn't we move on with those
>> >>>> entries first?
>> >>>
>> >>> I think at this point we essentially can just move all entries to the
>> >>> next. Will do that, and note down which patches haven't gotten any real
>> >>> review.
>> >>
>> >> We are close to the end of the month. Should I move on to do the
>> >> vacuuming or are you planning to do it? At this stage, to be fair with
>> >> people whose patches are in "waiting on author" state and because
>> >> there is not much time until the next CF begins, I propose to remove
>> >> all the remaining 43 entries with the same status as currently listed:
>> >> Needs review: 26. Waiting on Author: 11. Ready for Committer: 6.
>>
>> So, seeing nothing happening I have done the above, opened 2015-11 CF
>> and closed the current one.
>
> You seemingly moved all entries, even the ones which were
> waiting-on-author for a long while, over? I think we should return items
> on there with lot of prejudice. Otherwise we're never going to get
> anywhere.

I know. We should normally begin the cleanup activity far earlier IMO,
like at the end of the commit fest month to give patch authors a
couple of weeks to rework what they have if they would like to resend
something for the next commit fest. At this stage this seems a little
bit too abrupt to just return with feedback patches without notice,
this gives patch authors no room to submit new patches, assuming that
authors were waiting for the patch to be marked as returned with
feedback to move on to a new approach suggested by the reviewers.
-- 
Michael



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Freeze avoidance of very large table.
Next
From: Robert Haas
Date:
Subject: Re: ParallelContexts can get confused about which worker is which