Re: Not 7.5, but 8.0 ? - Mailing list pgsql-advocacy

From Christopher Browne
Subject Re: Not 7.5, but 8.0 ?
Date
Msg-id m3smkmct8i.fsf@wolfe.cbbrowne.com
Whole thread Raw
In response to Not 7.5, but 8.0 ?  (Josh Berkus <josh@agliodbs.com>)
Responses Re: Not 7.5, but 8.0 ?
Re: Not 7.5, but 8.0 ?
List pgsql-advocacy
Oops! josh@agliodbs.com (Josh Berkus) was seen spray-painting on a wall:
> Given all that, don't people think it's time to jump to 8.0?  Seems
> like even 7.4 is hardly recognizable as the same database as 7.0.

If wishes were fishes...  Shouldn't we see what interesting features
actually _do_ make it in?

If Win32 support does get ready, and we get recursive queries (I'll
point out different TODO items :-)) and Slony-1, PITR, and cache
improvements make it in, then perhaps it's time to call it 8.0.  A
"cvs update -Pd" doesn't get me that yet, so it seems early.

I'd _almost_ buy the story that 7.4 should have been called 8.0,
although that _didn't_ happen because it 'just missed' PITR and Win32.

The amusing approach would be to jump straight to 8.1 :-).
--
wm(X,Y):-write(X),write('@'),write(Y). wm('cbbrowne','acm.org').
http://www.ntlug.org/~cbbrowne/postgresql.html
..you could spend *all day* customizing the title bar.  Believe me.  I
speak from experience." -- Matt Welsh

pgsql-advocacy by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Not 7.5, but 8.0 ?
Next
From: Gavin Sherry
Date:
Subject: Press coverage in Australia