Re: Numbering of the next release: 8.0 vs 7.4

From: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Justin Clift <justin(at)postgresql(dot)org>, PostgreSQL Hackers Mailing List <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Numbering of the next release: 8.0 vs 7.4
Date: 2003-03-12 14:55:35
Message-ID: 1047480935.23128.714.camel@camel
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 2003-03-12 at 01:26, Tom Lane wrote:
> Justin Clift <justin(at)postgresql(dot)org> writes:
> > Would it be cool to decide on the version numbering of our next release
> > like this:
> > + If it looks like we'll have Win32 and/or PITR recovery in time for
> > the next release, we call it PostgreSQL 8.0
> > + If not, we call it 7.4
>
> Works for me: release schedule is solid, what we call it gets decided
> at the last minute ;-)
>

Personally I think Justin is a little off base with his criteria, since
I see the FE/BE protocol changes as the real differentiator between an
8.0 and 7.4. Everyone is effected by a FE/BE protocol change, not nearly
so many are effected by either win32 or PITR. And think of this crazy
scenario: We release an 8.0 with PITR, then need either a 8.1 or a 9.0
with a FE/BE overhaul, then need a possible 10.0 because we've added
win32... yuk.

That said, I'll take Tom's position on this that we might as well worry
about whether it's going to be 7.4 or 8.0 once we hit feature freeze; by
then the whole discussion could be irrelevant.

Robert Treat

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dave Cramer 2003-03-12 14:55:49 Re: Roadmap for FE/BE protocol redesign
Previous Message Dave Page 2003-03-12 14:55:30 Re: Roadmap for FE/BE protocol redesign