| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Neil Conway <neilc(at)samurai(dot)com>, Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>, tgl(at)sss(dot)pgh(dot)pa(dot)us, jd(at)commandprompt(dot)com, scrappy(at)postgresql(dot)org, andrew(at)dunslane(dot)net, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Plan for feature freeze? |
| Date: | 2004-05-02 05:11:15 |
| Message-ID: | 409482F3.6080301@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> 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.
May I also make the point that I have only _just_ upgraded all our
production database servers to 7.4? Unless there are really compelling
new features in 7.5, I as yet see no reason to upgrade to 7.5 at any point.
As Postgres gets larger and postgres databases get larger, and we
properly maintain the previous versions, then the need to upgrade is
gone. It doesn't matter to me if it's a 1 year or 2 year development
cycle at the moment.
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2004-05-02 07:44:25 | Re: mingw configure failure workaround |
| Previous Message | Bruce Momjian | 2004-05-02 04:20:42 | Re: [PATCHES] FW: Timezone library |