Re: Bug Reporting Form - Mailing list pgsql-www

From Magnus Hagander
Subject Re: Bug Reporting Form
Date
Msg-id CABUevEyWmENQuZPtU2R0TV4Q_eQeNAvAqBdoPY9UYV7mBwSgWw@mail.gmail.com
Whole thread Raw
In response to Bug Reporting Form  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: Bug Reporting Form
List pgsql-www
On Sun, Jul 16, 2023 at 2:02 PM Andrew Dunstan <andrew@dunslane.net> wrote:
>
>
> Hi.
>
> After a couple of very inadequately described bugs I decided to take a look at the web site's bug reporting form.
ISTMwe could make a number of improvements. First, I think we could usefully add some text setting out exactly what
sortof detail should be provided. And second, I think there should be a field for "Steps to Reproduce". Probably some
textcloser to the form fields might also help. The reporting requirements might get a little lost in the paragraphs at
thetop of the page. 
>
> This certainly won't guarantee that reporters will give us enough information, but even if they don't it will put us
onfirmer ground when we kick back to them because they haven't done so. 

Agreed on all accounts.

Would you like to take a stab at suggesting some of those texts?

As for the form itself, yeah, definitely. And worth noticing is that
since we don't store the bug reports anywhere (that's a whole
different can of worms - but the only thing we store is a mapping of
bug id to messageid), we can trivially change and move around the
fields if we want to, as we have no old data we need to think about
transforming.

--
 Magnus Hagander
 Me: https://www.hagander.net/
 Work: https://www.redpill-linpro.com/



pgsql-www by date:

Previous
From: Akshat Jaimini
Date:
Subject: Re: Broken Urls present on the official PostgreSQL website (as reported by the Testing Harness Suite)
Next
From: "Jonathan S. Katz"
Date:
Subject: Re: Bug Reporting Form