Tom Lane wrote:
> "Joshua D. Drake" <jd@commandprompt.com> writes:
>> Dave Page wrote:
>>> Actually thinking about it, I think we should plan the next cycle
>>> based on whatever ends up happening this time - eg. April freeze,
>>> Aug-Sept beta, Oct release.
>
>> I actually would be more inclined to have an even shorter cycle release
>> next time... e.g. January Freeze. The original idea was sound, make it
>> so we aren't testing in the middle of summer.
>
> I think part of the problem is exactly that the freeze period has
> stretched into summer, and so people aren't around for one reason or
> another, and so it's going slower than one could wish.
>
> As already noted, when we set the schedule we were not expecting to have
> so many large patches dropped on us at the very end of the devel cycle.
> What I'd like to think about is how can we avoid *that* happening again?
> Maybe there's no way, because human nature is to not finish stuff much
> before the deadline :-(. But dealing with a big patch logjam is
> obviously overwhelming the community's resources.
I'm confident we can address that over time. It's easy for companies
like NTT and EDB to start flooding us with big patches, but it takes
time for us to start to trust their developers enough that 'regular'
reviewers/committers can rely on them. We're already getting extremely
high quality reviews from people like Heikki and over coming cycles I
hope we'll get to trust more of the new flock of contributors who in
turn will help relieve some of the workload.
Regards, Dave
