[OPEN-ILS-DEV] Bug tracking (was: 1.6RC1 - Acquistions - possiblebugs)

[David Fiander]

Karen,

The good thing about a bug tracking system is that it can generate
email when new problems are reported, and can allow users to register
their interest in updates on the status of individual reports.

No matter what structure for handling questions and reports shakes out
in the long run, developers will have to continue to trawl the mailing
lists and create problem reports based on things that come up in the
mailing lists, because we will always as questions about stuff we're
confused about, and sometimes those questions will lead to newly
identified problems.

I like the idea of an address to which people can send messages
reporting problems, which Dan's "swinging gate" peer review committee
would all monitor and from which most problem reports would be
created.

- David

On Fri, Sep 18, 2009 at 11:52 AM, Karen Schneider <kgs at esilibrary.com> wrote:
>> Right, in my mind "wider community" would be a small team who would be
>> able to make that distinction based on questions / reports posted to the
>> mailing lists. We don't have to grant ticket management powers to
>> everyone. I think this was part of the problem with the old Bugzilla
>> instance: lots of noise that quickly became unmanageable.
>
> So just to be clear, questions/bug reports would still go to mailing lists?
>
> One thought I had about that approach (since I agree on noise
> reduction but also want the process to be easier) was making THAT more
> structured, and communicating that process back to the community. A
> separate mailing list, evergreen-ils-bugs?
>
> I worry developers will scream, but this is another situation where I
> see a single web forum working better than these individual mailing
> lists.
>
>
> --
> --
> | Karen G. Schneider
> | Community Librarian
> | Equinox Software Inc. "The Evergreen Experts"
> | Toll-free: 1.877.Open.ILS (1.877.673.6457) x712
> | kgs at esilibrary.com
> | Web: http://www.esilibrary.com
>