| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Merlin Moncure <mmoncure(at)gmail(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Kam Lasater <ckl(at)seekayel(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: No Issue Tracker - Say it Ain't So! |
| Date: | 2015-09-29 22:46:11 |
| Message-ID: | 10057.1443566771@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> Merlin Moncure wrote:
>> I've read this email about three times now and it's not clear at all
>> to me what a issue/bug tracker brings to the table.
> In my opinion, this thread is about a bug tracker, not a patch tracker.
> We already have a patch tracking system which works very well.
Mumble ... the CF app works, but I'm not sure if it works "very well".
There's some ease-of-use issues I think, though we've now damped them
down to the point where the only really major stumbling block is getting
a patch into the CF app initially.
One thing to think about if we do adopt a bug tracker is how will it
interact with the CF app. Ideally, patches that represent responses
to issues in the BT would be tracked more or less automatically by
both apps, if indeed we don't merge them altogether.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | zhangjinyu | 2015-09-29 23:01:56 | Re: BRIN Scan: Optimize memory allocation in function 'bringetbitmap' |
| Previous Message | Josh Berkus | 2015-09-29 22:41:33 | Re: Idea for improving buildfarm robustness |