New numbers on where we are with this CommitFest, at the end of the fourth week: 72 patches were submitted 3 patches were withdrawn (deleted) by their authors 12 patches were moved to CommitFest 2010-09 -- 57 patches in CommitFest 2010-07 -- 3 committed to 9.0 -- 54 patches for 9.1 -- 1 rejected 18 returned with feedback 28 committed for 9.1 -- 47 disposed -- 7 pending 2 ready for committer -- 5 will still need reviewer attention 1 waiting on author to respond to review -- 4 patches need review now and have a reviewer assigned With about 56 hours left until the close of the CommitFest, we're down to two "Ready for Committer" and three other potentially committable patches. Do we have a plan (with a time line) for producing an 9.1alpha1 release after the CF closes? (Have we even set a policy on whether we do that when we're still in beta testing for the release which hit feature freeze six months ago?) No patches were moved to the next CF this week, seven were committed, and one was returned with feedback. Two of the four patches in "Needs Review" status are WiP patches, and for both a review is long overdue by CF guidelines. The other two in "Needs Review" status had new patches posted yesterday which respond to committer feedback. The last action for the one patch in "Waiting on Author" status was feedback from Tom five days ago. Last week: > 72 patches were submitted > 3 patches were withdrawn (deleted) by their authors > 12 patches were moved to CommitFest 2010-09 > -- > 57 patches in CommitFest 2010-07 > -- > 3 committed to 9.0 > -- > 54 patches for 9.1 > -- > 1 rejected > 17 returned with feedback > 21 committed for 9.1 > -- > 39 disposed > -- > 15 pending > 9 ready for committer > -- > 6 will still need reviewer attention > 1 waiting on author to respond to review > -- > 5 patches need review now and have a reviewer assigned
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers