Re: commitfest 2016-11 status summary - Mailing list pgsql-hackers

From Haribabu Kommi
Subject Re: commitfest 2016-11 status summary
Date
Msg-id CAJrrPGcGcKz4W5-pvROad41WTwQQEPPv6iikP7z24qSRYRjn+Q@mail.gmail.com
Whole thread Raw
In response to Re: commitfest 2016-11 status summary  (Haribabu Kommi <kommi.haribabu@gmail.com>)
Responses Re: commitfest 2016-11 status summary
Re: commitfest 2016-11 status summary
List pgsql-hackers
Hi All,


The commitfest status summary at the end of commitfest.

Needs review: 0
Waiting on author: 0
Ready for Commiter: 0
Commited: 41
Moved to next CF: 79
Rejected: 7
Returned with feedback: 20
TOTAL: 147

Overall progress of completion - 46% (doesn't include "moved to next CF")

Micheal,  I need your help in closing the commitfest.


I closed the commitfest using the following assumptions.

Moved to next CF with needs review.
1. patch doesn't receive any full review in the commitfest
2. Patch received feedback at the end of commitfest.

Moved to next CF with waiting on author:
1. Patch doesn't apply to HEAD, but didn't receive any feedback.

Returned with feedback:
1. Patch received feedback, but author hasn't responded yet.
2. Author is expected to share an updated patch.

Rejected:
1. Any -1 from committer to the approach of the patch

May be these assumptions needs to be updated, as this is the first
time as CFM for me. 

As I observed many patches that are keep on moving to next CF from previous
patches, is there any way in commitfest that can highlight those patches, so that
those patches gets the review first than the patches that are came late to the 
commitfest.

I definitely may missed judging the current state of the patch. Please feel free to
update the actual status.

Thanks everyone.

Regards,
Hari Babu
Fujitsu Australia

pgsql-hackers by date:

Previous
From: Ashutosh Bapat
Date:
Subject: Re: Transactions involving multiple postgres foreign servers
Next
From: Haribabu Kommi
Date:
Subject: Re: Transactions involving multiple postgres foreign servers