From: | Andrew Sullivan <ajs(at)commandprompt(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Patch: plan invalidation vs stored procedures |
Date: | 2008-08-19 20:22:43 |
Message-ID: | 20080819202242.GV9771@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Aug 19, 2008 at 12:42:29PM -0700, Joshua Drake wrote:
> Generally speaking we adhere to the following guideline for patches.
> * Security fixes are applied to all applicable branches.
> * Bugfixes are applied to all applicable branches
> * Note: A patch that addresses a known limitation is generally
> not backpatched
> * New features are always applied to -HEAD only.
>
> This is not a policy as much as a legend for developers to consider
> before they submit their patch.
But it's meaningless. "Bugfixes are applied to all applicable
branches," is either false or trivially true. It's trivially true if
you interpret "applicable branches" to mean "the ones that get the
patch". It's false if you mean "bugfix" to mean "every patch that
fixes a bug". I can think of bugs that we have lived with in older
releases because fixing them was too risky or because the bug was so
tiny or unusual as to make the risk greater than the reward.
A formal policy that's any more detailed than what's in the FAQ today
is a solution in search of a problem.
A
--
Andrew Sullivan
ajs(at)commandprompt(dot)com
+1 503 667 4564 x104
http://www.commandprompt.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 2008-08-19 20:25:51 | Re: Patch: plan invalidation vs stored procedures |
Previous Message | Dimitri Fontaine | 2008-08-19 20:22:01 | Re: Patch: plan invalidation vs stored procedures |