| From: | Joe Conway <mail(at)joeconway(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Simon Riggs <simon(at)2ndQuadrant(dot)com> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Thomas Kellerer <spam_eater(at)gmx(dot)net>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: No Issue Tracker - Say it Ain't So! |
| Date: | 2015-09-25 16:55:56 |
| Message-ID: | 56057C9C.50100@joeconway.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 09/25/2015 09:32 AM, Tom Lane wrote:
> 2. There's no visibility for outsiders as to what issues are open or
> recently fixed. Not being outsiders, I'm not sure that we are terribly
> well qualified to describe this problem precisely or identify a good
> solution --- but I grant that there's a problem there.
>
> I do not know how much emphasis the project should place on point #2.
> By definition, fixing that will not return any direct benefit to us.
I would argue that there is some benefit for us in terms of advocacy. We
certainly get criticized for our lack of a bug tracker. I don't know of
anyone who specifically rejected Postgres because of that fact, but
would not be surprised if has happened.
Joe
--
Crunchy Data - http://crunchydata.com
PostgreSQL Support for Secure Enterprises
Consulting, Training, & Open Source Development
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-09-25 17:09:46 | Re: No Issue Tracker - Say it Ain't So! |
| Previous Message | Nikolay Shaplov | 2015-09-25 16:46:40 | Re: pageinspect patch, for showing tuple data |