Folks, As previously announced, CommitFest 2009-07 will begin on July 15th. For the sake of clarity, I'd like to propose that the deadline for patch submission be fixed at:
Wed Jul 15 00:00:00 UTC 2009 ...which is just under 26.5 hours from now. Barring objections, at that time, I (or someone) will change the status of the 2009-07 CommitFest from "Open" to "In Progress" and create a new, open commitfest scheduled for 2009-09. (We can change the date later if we decide that's not when we want to have it, but it didn't seem like there was a lot of opposition to the idea of having one every two months.) If you are a patch author, please make sure that your patches (1) have been sent to pgsql-hackers, (2) have been added to commitfest.postgresql.org, and (3) apply, compile, and pass regression tests against CVS HEAD. We could use a few volunteers to do quick sanity checks against the patches posted on the wiki - namely, it would be useful to verify that the latest "Patch" link from commitfest.postgresql.org actually is the latest version of the patch (i.e. link is not broken, the correct patch is present in the linked email, and no subsequent versions have been posted to -hackers without updating the status of the patch). Assuming that's the case, it would also be useful to verify that the patch applies to CVS HEAD, that you can compile it, and that it passes regression tests. If any of these steps fail, please do the following: 1. Email the patch author, explain which step failed, and copy pgsql-hackers. 2. Go to commitfest.postgresql.org and add a "Review" comment citing the message-ID generated in step 1. 3. Set the status of the patch to "Waiting on author" (use the "Edit Patch" link). If the patch passes your superficial examination, just add a comment so indicating, maybe something like this: "Applies, compiles, passes regression tests". ...Robert -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
