[OPEN-ILS-DEV] 1.6RC1 - Acquistions - possible bugs

[Wills,Steve]

Having a roadmap, version controlled source repository, and bug
tracking/testing that are available to a volunteer community are all key
components in successful OS, imho.

This list has mentioned Bugzilla and Trac many time.  Is there a general
preference?  My suggestion, when picking a tracking system is to suspend
disbelief that it will be used and pick it on merit.  How to manage
managing the managers is a separate issue from who to manage the bugs.
Again, in my opinion.

Steve Wills

-----Original Message-----
From: open-ils-dev-bounces at list.georgialibraries.org
[mailto:open-ils-dev-bounces at list.georgialibraries.org] On Behalf Of
Karen Schneider
Sent: Thursday, September 17, 2009 5:07 PM
To: Evergreen Development Discussion List
Subject: Re: [OPEN-ILS-DEV] 1.6RC1 - Acquistions - possible bugs

>> Something that came to mind recently (w/respect to the "release
process"
>> thread) is that we could set up a Testing/Qualit key componay
Assurance group of
>> volunteers who, as one of their powers, would have Trac accounts for
>> managing bugs like this. Other powers/responsibilities might be
vetting
>> bugs, reproducing bugs, adding tests to ensure bugs don't rear their
>> ugly heads again, etc. Just trying to work out how we can help the
>> broader community help the development team.

There's a natural bridge here to the documentation process, as well.
In the last DIG meeting we opened discussion about how to log bugs
discovered in the documentation process. It would seem a good use of
resources to empower some volunteers for Trac access, as part of the
documentation workflow.



-- 
-- 
| 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