Tom Lane wrote:
> Stefan Kaltenbrunner <stefan@kaltenbrunner.cc> writes:
>> Point I want to make is - all those are cool features(and might be
>> critical for some) but I don't think they warrant a dramatic change in
>> the release cycle policy ...
>
> Any release is going to have some things that are compelling and some
> that aren't, for any particular person ... it's just that those things
> vary depending on who you are ...
>
> I was heard to gripe not long ago that feature freeze during August was
> bad timing. It would be interesting to try to do it during the spring
> instead, just to see if people have more free time then. So for me,
> +1 for a shorter-than-a-year cycle this time, independently of what
> features make it or don't.
Well on that same vein (with a +1), I know that we lost at least 8 weeks
of productivity from various vacations etc.. during the summer. When you
incorporate everyone else that is involved with postgresql, I could
easily see almost a full man year lost, by having freeze where it is now.
I think having a freeze more toward march/april makes a heck of a lot of
sense.
Joshua D. Drake
>
> regards, tom lane
>
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240 Providing the most comprehensive PostgreSQL
solutionssince 1997 http://www.commandprompt.com/