Re: Feature freeze progress report

From: Naz Gassiep <naz(at)mira(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Marc Munro <marc(at)bloodnok(dot)com>, heikki(at)enterprisedb(dot)com, pgsql-hackers(at)postgresql(dot)org, dpage(at)postgresql(dot)org, simon(at)2ndquadrant(dot)com, bruce(at)momjian(dot)us
Subject: Re: Feature freeze progress report
Date: 2007-05-02 05:38:03
Message-ID: 463823BB.9090902@mira.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> What is "approved to contrib"?
>
> The problem here is that having reasonable certainty that a patch is
> not malicious requires having gone over it in some detail; at which
> point you might as well apply the thing. Or if you didn't apply it,
> you bounced it for reasons that are unlikely to have anything to do
> with needing more automated testing.
>
> ISTM this idea can only work if we have a "second tier" of reviewers
> who are considered good enough to vet patches as safe, but not quite
> good enough to certify them as commitable. I'm not seeing a large pool
> of people volunteering to hold that position --- at best it'd be a
> transitory state before attaining committerdom. If you are relying
> on a constant large influx of new people, you are doomed to failure
> (see "Ponzi scheme" for a counterexample).
Yep. For the record, Ponzi died in poverty, so it's not a counter
example, just proves that any gains that are had will be short lived and
increase the size of the crash when crunch time comes. :)
- Naz.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavan Deolasee 2007-05-02 05:56:43 Re: Patch queue triage
Previous Message Tom Lane 2007-05-02 05:19:45 Re: Feature freeze progress report