| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: "Bugs" CF? |
| Date: | 2015-05-08 01:42:45 |
| Message-ID: | 16478.1431049365@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> On 5/7/15 9:44 AM, Stephen Frost wrote:
>> a) make sure we don't lose track of bug-fix patches
>> b) make it clear where bug-fix patches should be submitted
>> c) provide a view of bug-fix patches for people to look at outside of
>> CF time
>> d) continue to have a single view which includes all active patches
>> with bug fixes listed first
> I think these goals are valid, but are adequately served by the current
> setup.
Not sure I agree with that ...
> I think having a separate bucket for bugs would just lead to lots of
> discussions over what qualifies as a bug.
... but I do agree with this. With our current methodology there's
not a lot of need to decide a-priori whether something is a feature
or a bug (in particular, the way it's categorized in the CF app is
not a high-stakes decision). I think that's just as well.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2015-05-08 01:43:46 | Re: commitfest app bug/feature |
| Previous Message | Michael Paquier | 2015-05-08 01:40:50 | subxcnt defined as signed integer in SnapshotData and SerializeSnapshotData |