On Fri, 2006-09-22 at 14:16 +0100, Dave Page wrote:
Following the recent discussion on this list and another on pgsql-core,
we have decided that we would like to aim to meet the following schedule
for the release of PostgreSQL 8.3:
April 1st 2007 - Feature freeze
May 1st 2007 - Beta 1
Following the recent discussion on this list and another on pgsql-core,
we have decided that we would like to aim to meet the following schedule
for the release of PostgreSQL 8.3:
April 1st 2007 - Feature freeze
May 1st 2007 - Beta 1 release
June 1st 2007 - Release
This will obviously be a
Dave Page wrote:
Following the recent discussion on this list and another on pgsql-core,
we have decided that we would like to aim to meet the following schedule
for the release of PostgreSQL 8.3:
April 1st 2007 - Feature freeze
May 1st 2007 - Beta 1 release
June 1st 2007 - Release
-Original Message-
From: Bruce Momjian [mailto:[EMAIL PROTECTED]
Sent: 22 September 2006 15:26
To: Dave Page
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] 8.3 Development Cycle
Sounds fine, but announcing this now is almost certain to reduce the
number of people
Dave Page wrote:
-Original Message-
From: Bruce Momjian [mailto:[EMAIL PROTECTED]
Sent: 22 September 2006 15:26
To: Dave Page
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] 8.3 Development Cycle
Sounds fine, but announcing this now is almost certain
Bruce Momjian wrote:
Dave Page wrote:
-Original Message-
From: Bruce Momjian [mailto:[EMAIL PROTECTED]
Sent: 22 September 2006 15:26
To: Dave Page
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] 8.3 Development Cycle
Sounds fine, but announcing this now is almost
-Original Message-
From: Bruce Momjian [mailto:[EMAIL PROTECTED]
Sent: 22 September 2006 15:35
To: Dave Page
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] 8.3 Development Cycle
Err right - if you had said this yesterday when we
discussed the idea I
could have
Dave Page wrote:
-Original Message-
From: Bruce Momjian [mailto:[EMAIL PROTECTED]
Sent: 22 September 2006 15:26
To: Dave Page
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] 8.3 Development Cycle
Sounds fine, but announcing this now is almost certain to reduce the
number
Dave Page wrote:
This will obviously be a short development cycle which will allow us to
get some of the features that just missed 8.2 out of the door, as well
as giving us the opportunity to try releasing before the summer (for
those in the northern hemisphere) rather than after.
Joshua's
Bruce, Dave,
This will likely stop people from migrating to 8.2, but so what? It
isn't going to stop new users and existing users in real production
setting will likely wait for 8.3 anyway.
And at this point most production users are only upgrading every 2-3
releases anyway (something which
-Original Message-
From: Tom Dunstan [EMAIL PROTECTED]
To: Dave Page dpage@vale-housing.co.uk
Cc: pgsql-hackers@postgresql.org pgsql-hackers@postgresql.org
Sent: 22/09/06 17:21
Subject: Re: [HACKERS] 8.3 Development Cycle
will other features be considered if
they're ready?
Yes, normal
Tom,
I'm obviously thinking of enums which was ready (for review at least) a
few weeks ago, but has probably bitrotted slightly since then given the
number of patches that have landed in the tree. I intended to brush it
up as soon as the 8.3 tree was open and resubmit it. Will that be a
waste
Tom Dunstan [EMAIL PROTECTED] writes:
Joshua's original mail suggested that only certain features would go in.
Is that still on the cards, or will other features be considered if
they're ready?
You'll note that Dave's mail said no such thing.
There has been some talk of trying to agree on a
Tom Dunstan wrote:
Dave Page wrote:
This will obviously be a short development cycle which will allow us to
get some of the features that just missed 8.2 out of the door, as well
as giving us the opportunity to try releasing before the summer (for
those in the northern hemisphere) rather than
Josh Berkus josh@agliodbs.com writes:
Bruce, Dave,
This will likely stop people from migrating to 8.2, but so what? It
isn't going to stop new users and existing users in real production
setting will likely wait for 8.3 anyway.
And at this point most production users are only upgrading
On Fri, Sep 22, 2006 at 02:16:53PM +0100, Dave Page wrote:
Following the recent discussion on this list and another on
pgsql-core, we have decided that we would like to aim to meet the
following schedule for the release of PostgreSQL 8.3:
April 1st 2007 - Feature freeze
^
We
Josh Berkus wrote:
I'm obviously thinking of enums which was ready (for review at least) a
few weeks ago, but has probably bitrotted slightly since then given the
number of patches that have landed in the tree. I intended to brush it
up as soon as the 8.3 tree was open and resubmit it. Will that
Josh Berkus wrote:
Tom,
I'm obviously thinking of enums which was ready (for review at least) a
few weeks ago, but has probably bitrotted slightly since then given the
number of patches that have landed in the tree. I intended to brush it
up as soon as the 8.3 tree was open and resubmit it.
Tom Lane wrote:
Tom Dunstan [EMAIL PROTECTED] writes:
Joshua's original mail suggested that only certain features would go in.
Is that still on the cards, or will other features be considered if
they're ready?
You'll note that Dave's mail said no such thing.
No, but it did explicitly
Tom,
Pretty sure. :) Why the oops? They haven't been mentioned in some PR
material or something have they?
No, I'd just been confused and thought the patch was submitted before
feature freeze.
--
--Josh
Josh Berkus
PostgreSQL @ Sun
San Francisco
---(end of
On Friday 22 September 2006 12:40, Tom Lane wrote:
Tom Dunstan [EMAIL PROTECTED] writes:
Joshua's original mail suggested that only certain features would go in.
Is that still on the cards, or will other features be considered if
they're ready?
You'll note that Dave's mail said no such
Robert Treat wrote:
On Friday 22 September 2006 12:40, Tom Lane wrote:
Tom Dunstan [EMAIL PROTECTED] writes:
Joshua's original mail suggested that only certain features would go in.
Is that still on the cards, or will other features be considered if
they're ready?
You'll note that
Bruce Momjian [EMAIL PROTECTED] writes:
Agreed, but my guess is that we are going to introduce shorter varlena
headers for 8.3. It will hard to reject an optimization like that, and
that will probably change the disk format for most columns.
Well, several of the proposals that have been made
23 matches
Mail list logo
