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

Re: damage control mode

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, David Fetter <david(at)fetter(dot)org>
Subject: Re: damage control mode
Date: 2010-01-10 12:55:09
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Sun, Jan 10, 2010 at 5:31 AM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>> But really if beta slips because we don't like the looks of our open issues
>> list, thats signicantly better than the last couple releases where we held
>> everything up just to get things into CVS months after feature freeze had
>> passed us by.
> It is, unless it's because we created those open items by committing
> things too late in the cycle, even though it wasn't quite ready, "so
> the author won't have to wait another year for a release".

Exactly.  Or even - it was ready, but even code that's ready can have
bugs.  The more time you give yourself before release, the more likely
you are to find a few of those.


In response to

pgsql-hackers by date

Next:From: Robert HaasDate: 2010-01-10 13:02:21
Subject: Re: damage control mode
Previous:From: Robert HaasDate: 2010-01-10 12:53:35
Subject: Re: damage control mode

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