Re: Two weeks to feature freeze

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>
Cc: Justin Clift <justin(at)postgresql(dot)org>, The Hermit Hacker <scrappy(at)postgresql(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, pgman(at)candle(dot)pha(dot)pa(dot)us, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Two weeks to feature freeze
Date: 2003-06-20 14:42:04
Message-ID: 17986.1056120124@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> writes:
> On Fri, 2003-06-20 at 06:59, Justin Clift wrote:
>> The only thing that makes me wince is that we have a protocol change at
>> PostgreSQL 7.4 release instead of 8.0.

> ...which is why I'd advocate making this release an 8.0 regardless of
> win32 or pitr.

<shrug> ... The backend will still talk to old clients, and libpq will
still talk to old backends, so I don't think the protocol change is
really going to cause a flag day for anyone. On a technical level it's
probably not an adequate reason to call this release 8.0.

On the other hand, I dislike the notion that we would call a release 8.0
simply because it now has a native Windows port. (And if there is a
short release cycle after this one, that might be about the only big new
thing there.) Considering that we aren't going to be recommending the
Windows port for production work, we should not let the release
numbering give the impression we think it's the greatest Postgres
feature ever to come down the pike.

I'm happy to keep calling 'em 7.* for the foreseeable future, myself.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nailah Ogeer 2003-06-20 15:00:42 Re: [HACKERS] psql
Previous Message Robert Treat 2003-06-20 14:31:53 Re: Two weeks to feature freeze