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

[Soulliere, Robert]

I would vote for trac for all the points that Mike made. From my perspective, trac is a great system for tracking code changes and fixing bugs by downloading the updated files from trac or editing parts of files based on the code changes displayed in trac. If it can be made so that we and others in the community can help the developers more by allowing a testing feedback and bug reporting system, that would be great.

Robert Soulliere
Systems Librarian
robert.soulliere at mohawkcollege.ca
Tel: 905-575-1212 X3936

Library at Mohawk
Connect * Learn * Succeed
brain.mohawkcollege.ca

-----Original Message-----
From: open-ils-dev-bounces at list.georgialibraries.org [mailto:open-ils-dev-bounces at list.georgialibraries.org] On Behalf Of Mike Rylander
Sent: September 18, 2009 10:17 AM
To: Evergreen Development Discussion List
Subject: Re: [OPEN-ILS-DEV] 1.6RC1 - Acquistions - possible bugs

On Fri, Sep 18, 2009 at 10:12 AM, Wills,Steve <wills at nelinet.net> wrote:
> 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.

On that score, I think trac has the lead over bugzilla for a couple reasons:

* it's already set up
* it's simpler
* it sits right on top of the authoritative source repo
* it's much MUCH easier to hack on if we need it to do more than the
stock version

IMO, as well.

--miker

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



--
Mike Rylander
 | VP, Research and Design
 | Equinox Software, Inc. / The Evergreen Experts
 | phone:  1-877-OPEN-ILS (673-6457)
 | email:  miker at esilibrary.com
 | web:  http://www.esilibrary.com

This E-mail contains privileged and confidential information intended
only for the individual or entity named in the message.  If the reader
of this message is not the intended recipient, or the agent responsible
to deliver it to the intended recipient, you are hereby notified that
any review, dissemination, distribution or copying of this communication
is prohibited.  If this communication was received in error, please
notify the sender by reply E-mail immediately, and delete and destroy
the original message.