Skip site navigation (1) Skip section navigation (2)

Re: 8.5 development schedule

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Greg Stark <gsstark(at)mit(dot)edu>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: 8.5 development schedule
Date: 2009-07-01 22:57:05
Message-ID: 200907012257.n61Mv5q12710@momjian.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Greg Stark wrote:
> On Tue, Jun 30, 2009 at 5:11 PM, Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 
> > I'm also not prepared to push a large and unstable feature into the tree
> > on the hope that it will get fixed.
> 
> I didn't have the impression it had any known problems, Simon and
> others spent a lot of time testing it already. The improvements Heikki
> was asking for were simplifications or cleanup type changes and every
> time he asked for something Simon had it done within a day or two.
> 
> The problem is I think this will *always* be a "large unstable
> feature" just because it's large. If we aren't happy having it in the
> tree for alpha releases then there's no circumstance we'll ever be
> happy having it in a real release. I think it's a *lot* better having
> it in the alpha releases when if we find problems we can revert it or
> fix the problems than dropping it at the last second before the betas
> when it has to be perfect and there's no second chances.

By that logic we would never have accepted large patches, but we have,
often.

-- 
  Bruce Momjian  <bruce(at)momjian(dot)us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2009-07-01 23:00:26
Subject: Re: 8.5 development schedule
Previous:From: Bruce MomjianDate: 2009-07-01 22:55:45
Subject: Re: 8.5 development schedule

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group