Thread: Schedule, feature freeze, etc

Okay folks, it's July 1, and the long-threatened feature freeze for 7.5
is now in place.  That means future patches that introduce new features
will be held off till the next development cycle.  Bug fixes, cleanup
of loose ends, and (ahem) documentation are of course still welcome.

Since we've just barely gotten some major patches in under the wire,
we're going to construe "no new features" pretty loosely.  For instance,
the syntax associated with nested transactions is still open for debate
and we aren't going to refuse to change it just because it's past
July 1 --- that will be considered to be in the "loose ends" category.
Same for PITR and Windows-related tweaks.

The core committee is hoping to see enough loose-end-fixup and
documentation-writing done in the next two weeks that we can put out
a first "official beta" around July 15.  We are going to shoot for
official release September 1 (though given the size of the changes,
it wouldn't be surprising if we have to slip that).
        regards, tom lane

Tom Lane wrote:

> Okay folks, it's July 1, and the long-threatened feature freeze for 7.5
> is now in place.  That means future patches that introduce new features
> will be held off till the next development cycle.  Bug fixes, cleanup
> of loose ends, and (ahem) documentation are of course still welcome.
> 
> Since we've just barely gotten some major patches in under the wire,
> we're going to construe "no new features" pretty loosely.  For instance,
> the syntax associated with nested transactions is still open for debate
> and we aren't going to refuse to change it just because it's past
> July 1 --- that will be considered to be in the "loose ends" category.
> Same for PITR and Windows-related tweaks.

What about features that have been submitting patches and trying to get 
included for a few weeks now.

Specificially, I'm concerned with pg_autovacuum backend integration.  I 
know people have been busy frying bigger fish, so the patch probably 
hasn't recieved much review yet, but it was submitted prior to July 1. 
Do you know how that will be handled?

Thanks,

Matthew

"Matthew T. O'Connor" <matthew@zeut.net> writes:
> Tom Lane wrote:
>> Okay folks, it's July 1, and the long-threatened feature freeze for 7.5
>> is now in place.

> What about features that have been submitting patches and trying to get 
> included for a few weeks now.

I already said that everything now in the queue is considered to be here
"on time" (though I think that was on -patches, so maybe you didn't
see the thread).  Part of the reason we need a couple more weeks before
beta is to get those patches reviewed and integrated ...
        regards, tom lane

Matthew T. O'Connor wrote:

>
> What about features that have been submitting patches and trying to 
> get included for a few weeks now.
>
> Specificially, I'm concerned with pg_autovacuum backend integration.  
> I know people have been busy frying bigger fish, so the patch probably 
> hasn't recieved much review yet,

Actually I'd have liked to see pg_autovacuum committed before July 1st, 
because it appears as the right place for auto serverlog rotation stuff 
as well.

Regards,
Andreas