Re: damage control mode

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: <jd(at)commandprompt(dot)com>,"Robert Haas" <robertmhaas(at)gmail(dot)com>
Cc: "Greg Smith" <greg(at)2ndquadrant(dot)com>, "Josh Berkus" <josh(at)agliodbs(dot)com>, "David Fetter" <david(at)fetter(dot)org>, "Peter Eisentraut" <peter_e(at)gmx(dot)net>, "Dimitri Fontaine" <dfontaine(at)hi-media(dot)com>, "Bruce Momjian" <bruce(at)momjian(dot)us>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: damage control mode
Date: 2010-01-12 18:05:02
Message-ID: 4B4C656E020000250002E2E0@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Joshua D. Drake" <jd(at)commandprompt(dot)com> wrote:
> On Tue, 2010-01-12 at 12:52 -0500, Robert Haas wrote:

>> I think I was pretty clear about what I was proposing in the
>> message with which I started this thread - bump some or all the
>> big, outstanding patches to leave more time for stabilizing the
>> tree.
>>
>> Almost everyone said "no". That's the community's decision and I
>> accept it, but IMHO it's a tacit decision to slip the release.
>
> Agreed. (although I think we should bump the big outstanding
> patches)

I'm also inclined to think that it would be wiser not to try to
include large patches first submitted to the last commitfest, at
least if they pose any significant risk of destabilizing the code or
pulling people qualified to review HS or SR off of those areas
before release.

-Kevin

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2010-01-12 18:13:40 Re: planner or statistical bug on 8.5
Previous Message Bruce Momjian 2010-01-12 17:58:48 Re: damage control mode