Re: bugs and bug tracking

From: Craig Ringer <craig(at)2ndquadrant(dot)com>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: bugs and bug tracking
Date: 2015-10-07 09:23:00
Message-ID: CAMsr+YEOur1mtxxVXF0iuNn7tXWRoD5JDtpAy67J3Mk4WCzZEg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 6 October 2015 at 21:05, Nathan Wagner <nw+pg(at)hydaspes(dot)if(dot)org> wrote:

> A lot of the reports aren't bugs at all, but requests for help. My
> guess is that the users either don't know where to ask or don't
> understand the difference between a bug and not knowing how to do what
> they want to do. Perhaps a more thorough explaination on the submission
> form would be useful.

Based on experience elsewhere, not even "unless you are absolutely
certain this is a bug, post to pgsql-general" would work.

Unless there's a "post to pgsql-general" text box right there,
forum-like. Because that's the point IMO: it's easier to post to a web
form than think about mailing lists and subscriptions. You can't just
go "click, send". People are going to consistently ignore the fact
that it's a bug report form when there's no corresponding "ask a
question" web form.

I'm not really advocating a "send a question" web form though. More
like a link to Stack Overflow or something like that.

--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bernd Helmle 2015-10-07 09:59:28 Re: btreecheck extension
Previous Message Craig Ringer 2015-10-07 09:07:54 Re: Re: In-core regression tests for replication, cascading, archiving, PITR, etc.