From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Gregory Stark <stark(at)enterprisedb(dot)com> |
Cc: | Simon Riggs <simon(at)2ndQuadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Recovery Test Framework |
Date: | 2009-01-12 14:04:04 |
Message-ID: | 29031.1231769044@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Gregory Stark <stark(at)enterprisedb(dot)com> writes:
> ... But from my point of view it would
> just always be better to commit large patches immediately after forking a
> release instead of just before the beta to give them a whole release cycle of
> exposure to developers before beta testers.
I'm in favor of such an approach for this work, but it'll never fly as a
general project policy. People already dislike the fact that it takes
up to a year before their work gets reflected into a public release.
With such a policy we'd be telling developers "whatever you submit won't
see the light of day for one to two years". Not good for a project that
depends on the willingness of developers to scratch their own itches.
However, we are getting off onto a tangent. I wasn't trying to start
a discussion about general project policies, but about the specific
status of this particular group of patches.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Smith | 2009-01-12 14:05:59 | Re: Proposal: new border setting in psql |
Previous Message | Gregory Stark | 2009-01-12 14:03:09 | Re: [BUGS] Status of issue 4593 |