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

Re: damage control mode

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, David Fetter <david(at)fetter(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: damage control mode
Date: 2010-01-09 21:01:07
Message-ID: 1263070867.1339.18.camel@vanquo.pezone.net (view raw or flat)
Thread:
Lists: pgsql-hackers
On lör, 2010-01-09 at 14:12 -0500, Robert Haas wrote:
> If we accept large patches at the very end of the development cycle,
> that's when people will submit them.  You've previously criticized the
> high proportion of the release cycle that is set aside for CommitFest
> and beta, so I'm surprised to see you advocating for a policy that
> seems likely to lengthen the time for which the tree is closed.

Just to clarify: I am for sticking to the agreed dates.  If some things
are not ready by the necessary date plus/minus one, they won't make the
release.  If it's obvious earlier that something won't make the date, it
shouldn't be committed, and maybe put on the backburner right now.  But
AFAICT, that's independent of when it was submitted.  Some things that
were submitted just the other day might be almost ready, some things
that were first submitted many months ago are still not ready.


In response to

Responses

pgsql-hackers by date

Next:From: Peter EisentrautDate: 2010-01-09 21:06:59
Subject: Re: Setting oom_adj on linux?
Previous:From: Roger LeighDate: 2010-01-09 20:57:56
Subject: Re: Add .gitignore files to CVS?

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