From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Plan for feature freeze? |
Date: | 2004-05-01 16:30:45 |
Message-ID: | 4093D0B5.4060705@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian wrote:
>Neil Conway wrote:
>
>
>>On 30-Apr-04, at 8:53 PM, Tatsuo Ishii wrote:
>>
>>
>>>For me even September 1st does not seem too late. Major version up
>>>bring users pains including backup/restore application
>>>imcompatibilty... IMO to justify those pains we need to give users
>>>major enhancements. Honestly I don't understand why we should rush the
>>>major version up.
>>>
>>>
>>Yeah, I completely agree. I think a feature freeze date of August or
>>September is definitely worth considering.
>>
>>
>
>Tatsuo brought up the an excellent point (that I have been saying for a
>long time), that the number of must-fix bugs from previous releases is
>shrinking, and the complexity of new features is increasing.
>
>This dictates the that length of our release process should lengthen
>over time.
>
>
Last year feature freeze was declared in July, IIRC. That means that the
release cycle is approaching a year. Even with major features I don't
think that's too short. And there's every reason to think we will need
some very intensive testing during the Beta period (Win32 and PITR for
starters surely need some hard testing), so we could end up releasing
around November, unless we're lucky.
In fact, the longer you make the release cycle the more people will get
upset if they miss one.
I still think middle of June is about right for feature freeze (even
though it's not my decision).
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Joe Conway | 2004-05-01 16:39:37 | Re: Plan for feature freeze? |
Previous Message | Tom Lane | 2004-05-01 15:45:20 | Re: pg ANY/SOME ambiguity wrt sql standard? |