Re: [HACKERS] New version number 6.6 or 7.0 - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [HACKERS] New version number 6.6 or 7.0
Date
Msg-id 199907191435.KAA08696@candle.pha.pa.us
Whole thread Raw
In response to Re: [HACKERS] New version number 6.6 or 7.0  (The Hermit Hacker <scrappy@hub.org>)
Responses Re: [HACKERS] New version number 6.6 or 7.0
List pgsql-hackers
> > We've been making pretty steady progress over the last few releases.
> > I'd suggest that a bump to 7.0 should happen when we've accumulated
> > most of the fixes/improvements from the "hot list". We've worked
> > through most of those; here are the ones I'd like to see at or before
> > a 7.0 release:
> > 
> > o implement outer joins
> > o merge date/time types and deprecate the old 4-byte ones
> 
> My opinion is that MVCC should have jump'd us to 7.0 in the first
> place...
> 
> IMHO, release for October should be v7.0 ... if the above two get done,
> great, if not, no probs...

Due to overwhelming agreement, it is 6.6.  I personally vote for 7.0,
and so do you, but we are outnumbered.  We can revisit this as the
release gets closer, but to change it then, I am going to have to change
PG_VERSION, and that will require initdb for everyone.  Perhaps just
before we enter beta, we can discuss it, knowing then what our features
will be.

--  Bruce Momjian                        |  http://www.op.net/~candle maillist@candle.pha.pa.us            |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [ANNOUNCE] PostgreSQL status report
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] Why DEFAULT text 'now' does not work for TIMESTAMP columns