On Fri, Apr 8, 2016 at 11:00 AM, Andres Freund <andres@anarazel.de> wrote: > On 2016-04-08 10:56:28 -0400, Robert Haas wrote: >> On Fri, Apr 8, 2016 at 10:06 AM, David Steele <david@pgmasters.net> wrote: >> > On 4/8/16 10:00 AM, Tom Lane wrote: >> >> David Steele <david@pgmasters.net> writes: >> >>> So the commitfest is 84% complete with less than twelve hours to go. >> >> >> >> Have we set a particular time-of-day for closing the CF, and if so >> >> what is it exactly? >> > >> > From the referenced email: >> > >> > "Accordingly, the release management has decided that all >> > feature patches destined for PostgreSQL 9.6 must be committed no later >> > than April 8, 2016. Any patch not committed prior to 2016-04-09 >> > 00:00:00 GMT may not be committed to PostgreSQL 9.6 unless (a) it is a >> > bug fix, (b) it represents essential cleanup of a previously-committed >> > patch, or (c) the release management team has approved an extension to >> > the deadline for that particular patch." >> >> IOW, the deadline is 8pm US/Eastern time, or about 9 hours from now. >> >> Let's try not to introduce more bugs in the next 9 hours than we have >> in the preceding 9 months. > > I've finished polishing the Pin/Unpin patch. But the final polishing > happened on an intercontential flight, after days spent preparing my > move to SF. I'd be glad if you would allow me to look over the patch > again, before pushing it sometime this weekend; this stuff is subtle, > and I'm not exactly my best right now.
In view of these circumstances, the RMT has voted to extend the deadline for this particular patch by 2.5 days; that is, this patch may be committed with RMT approval no later than 2016-04-11 12:00:00 GMT, which I believe is approximately 4am Monday morning where you are.
Good to hear. Wise decision, because we really need this patch in 9.6.
------ Alexander Korotkov Postgres Professional: http://www.postgrespro.com The Russian Postgres Company
