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

Re: damage control mode

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: damage control mode
Date: 2010-01-08 18:38:20
Message-ID: 201001081838.o08IcKF03274@momjian.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Robert Haas wrote:
> >> We discussed doing this at the very beginning of 8.4 release cycle
> >> and, the more I think about it, the more I think it's not fair not to
> >> go ahead and do it. ?Otherwise, we're rewarding people for ignoring a
> >> guideline that was discussed, and punishing (1) the people who have
> >> refrained from submitting large patches at the last minute, (2) people
> >> who would like to see their already-committed patches released on a
> >> reasonable time frame, and (3) people who don't want the tree to be
> >> frozen for a near-eternity while we shake out all the bugs that these
> >> large, last-minute patches introduce. ?We're also increasing the
> >> chances the the final release will contain undiscovered bugs, since
> >> they will have had ONLY the beta period, and no part of the
> >> development cycle, to shake out.
> >
> > Doing what? ?Not including HS an SR in 8.5?
> 
> No.  Pushing off large patches that weren't submitted until the last
> CommitFest to the next release.

Sorry, I am still confused.  "Last" is the previous commit-fest,
November, or the final commit-fest, January.  Please restate your
opinion in full.  Thanks.

-- 
  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

Responses

pgsql-hackers by date

Next:From: Robert HaasDate: 2010-01-08 18:55:39
Subject: Re: damage control mode
Previous:From: Kevin GrittnerDate: 2010-01-08 18:36:44
Subject: Re: Serializable Isolation without blocking

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