On Tue, Sep 29, 2015 at 6:39 PM, Josh Berkus <josh@agliodbs.com> wrote:
> On 09/29/2015 03:08 PM, 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.
>
> Here are the problems I'd like to solve:
>
> 1. "Was this issue fixed in a Postgres update? Which one?"
>
> 2. Not losing track of minor bugs.
>
> 3. Having a better way to track bugs which require multi-part solutions
> (e.g. multixact).
>
> 4. Having a place for downstream projects/packagers to report bugs.
>
> 5. Not answering this question ever again: "Why doesn't your project
> have a bug tracker?"
Merlin,
I'm not sure if you are trolling me/us. I'm going to assume not and
interpret the comment from the prospective of: "the current process
works for those currently using the process"
That may be true (I'll leave it to someone more familiar with the
process to address). What that comment doesn't address is the needs of
those who are not currently involved or those who are not on this
email list. Just as "read the code" is an insufficient answer to a
user who is looking to use a feature, "read the mailing list" is an
insufficient answer to a query from a user about the state of bugs
past and present.
Given that, in addition to Josh's five points from an insider's
perspective I would add some from an outsider's perspective:
1/ Is the issue I'm having a known bug that can be fixed by an upgrade
to a more recent version, if so, which one?
2/ This project must be disorganized and/or not truly mature w/o a
central tracker
3/ No hints or help on what might be an easier place to start contributing
Hope that helps.
-Kam Lasater
@seekayel
