| From: | Neil Conway <neilc(at)samurai(dot)com> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, Ericson Smith <eric(at)did-it(dot)com>, Bruno Wolff III <bruno(at)wolff(dot)to>, Dmitry Tkach <dmitry(at)openratings(dot)com>, PostgreSQL General <pgsql-general(at)postgresql(dot)org>, Patrick MacDonald <patrickm(at)redhat(dot)com> |
| Subject: | Re: 7.4? |
| Date: | 2003-03-06 16:58:00 |
| Message-ID: | 1046969879.10528.40.camel@tokyo |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, 2003-03-06 at 11:50, Bruce Momjian wrote:
> So you were thinking of beta for May 1?
Rather than picking an arbitrary date for the beta, wouldn't it make
more sense to simply put out the beta when a particular set of features
are finished (say, Win32 + PITR + ...)
The potential downside is that the development period will drag on and
on, waiting for the delinquent features to be implemented.
The upside is that when we actually do make the release, we'll be sure
that we have enough features to justify an upgrade. As has been often
remarked, upgrading PostgreSQL is somewhat painful. I'd much rather make
periodic releases with major feature improvements than more frequent,
incremental releases -- because the initdb/reload pain will be the same
in either case.
Anyway, just throwing it out there... :-)
Cheers,
Neil
--
Neil Conway <neilc(at)samurai(dot)com> || PGP Key ID: DB3C29FC
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Johnson, Shaunn | 2003-03-06 17:02:05 | table accountability |
| Previous Message | Tom Lane | 2003-03-06 16:55:47 | Re: 7.4? |