| From: | Greg Smith <greg(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Jay Levitt <jay(dot)levitt(at)gmail(dot)com>, Alex <ash(at)commandprompt(dot)com>, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Bug tracker tool we need |
| Date: | 2012-04-18 04:01:19 |
| Message-ID: | 4F8E3C8F.8030301@2ndQuadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 04/17/2012 11:44 PM, Tom Lane wrote:
> At the same time, I think we'd likely be a lot better off squirting this
> data into bugzilla or another standard tracker, instead of building our
> own infrastructure.
Perhaps. It just struck me that a lot of the custom bits needed here
regardless could be built/added to the usual workflow bottom-up. You
don't have to assume that either a full tracker or something like my
simple POC idea will show up at the end to get started. Making goal #1
involve just mining for the data that's already around and squirting it
onto a web page would be a useful exercise, one that's likely to benefit
any tracker adoption.
--
Greg Smith 2ndQuadrant US greg(at)2ndQuadrant(dot)com Baltimore, MD
PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Brendan Jurd | 2012-04-18 04:57:09 | Re: Bug tracker tool we need |
| Previous Message | Tom Lane | 2012-04-18 03:44:11 | Re: Bug tracker tool we need |