Re: damage control mode

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Dimitri Fontaine <dfontaine(at)hi-media(dot)com>
Cc: Marko Tiikkaja <marko(dot)tiikkaja(at)cs(dot)helsinki(dot)fi>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org, David Fetter <david(at)fetter(dot)org>
Subject: Re: damage control mode
Date: 2010-02-08 15:25:36
Message-ID: 20100208152535.GF4113@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Dimitri Fontaine wrote:
> Marko Tiikkaja <marko(dot)tiikkaja(at)cs(dot)helsinki(dot)fi> writes:
> > The documentation has definitely improved from the last time Robert
> > looked at it, but I fear it still needs some more work. I'm willing to
> > do that work, but I need something concrete.
>
> It seems to me documentation is required to get into the source tree
> before beta, and as we see with some other patches it's definitely the
> case even with our newer procedures that some code gets in without its
> documentation properly finished. I guess this amounts to the commiter
> willing to fill up the docs later on.

Eh? Previously we allowed code to go in with documentation to be
written after feature freeze. Is this no longer acceptable?

--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2010-02-08 15:31:57 Re: damage control mode
Previous Message Tom Lane 2010-02-08 15:15:47 Re: [COMMITTERS] pgsql: Create a "relation mapping" infrastructure to support changing