<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Your rant is my rant. I am not a casual user but I have not seen too
many that I like. No make that none.<br>
Some of the things that I look for in a bug report:<br>
Date of submission<br>
Name and address of the submitter, so we can ask questions.<br>
Description of the problem.<br>
The rest are to be done by the development team.(done by development
team:<br>
Classification of problem (Installer, xslt, ....)<br>
Severity/Urgency of the problem.<br>
Who is tasked to fix the problem.<br>
Release that the fix is targeted for.<br>
Status of the fix.<br>
Dated notes.<br>
Mail of changes.<br>
Most importantly, easily searchable and easy to generate reports.<br>
<br>
As I said before,<br>
Simple to use.<br>
The more visible the better.<br>
<br>
Mark Goodwin wrote:<br>
<blockquote cite="midb0ca56fe0408280230419e41a1@mail.gmail.com"
type="cite">
<pre wrap="">I need to get a bugtracker set up for a couple of other projects I am
working on.
I saw two choices:
1) Use Scarab
2) Modify a simple system written by Gareth Morgan (a friend of mine).
I'd already eliminated Bugzilla because I wanted a system that was
useable by 'normal' people (the UI makes me want to cry; Scarab is a
little better). I also wanted to use a Java solution if possible.
I'd already eliminated non-free things because some of these other
projects are non-free and I can't afford the licenses.
I'm guessing that we're going to want something a bit more
sophisticated than Gareth's tool (he wrote it in an hour or two as an
excercise when learning Hibernate / Spring); if I were to use it I
would be making some enhancements, but that would be five or six weeks
off. It already does mail notifications, issue assignment, comments,
etc. but It's still not quite real-world useful. If you want to see
it in it's current state I can deploy it somewhere.
Anyway, given that I have to have an issue tracking system set up for
my own needs, if we're wanting to install Scarab at crosswire, I'm
happy to sort it out; I'm needing to do this elsewhere anyway.
The only problem I can see with this; we'd need to install an RDBMS on
the crosswire server (is there one already there?). I'd pick
PostgreSQL but MySQL would do...
MarkG
P.S.
<rant>
I've never yet come across a bug tracking tool I'm happy with; for
some reason it doesn't seem to have occurred to the people that write
these tools that there is a difference between the casual user (i.e.
the people who report the majority of post release bugs) and the
development team.
Things like Scarab and Bugzilla are absolutely fine for QA folk and
other members of the dev team as once they've gone through the (not
inconsiderable) pain of familiarising themselves with the gazillion
fields and options in each form, they're afforded a fiarly large
degree of flexibility.
The trouble is that in all free software projects, (along with most
bespoke projects and many POTS products) a large proportion of the
issues are reported by end users rather than members of the dev team.
Users do not want to learn how to use something just to give you
feedback, which makes bugzilla almost useless (it took a friend of
mine over half an hour to report a bug in Red Hat Linux).
This is why I am still seriously considering a 2 hour hack over such
things as Bugzilla and Scarab for my own use; basic though it is, it
just works.
</rant>
On Sat, 28 Aug 2004 04:15:24 -0400, DM Smith <a class="moz-txt-link-rfc2396E" href="mailto:dmsmith555@yahoo.com"><dmsmith555@yahoo.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Two thoughts:
The simpler the better.
The more visible the better.
I don't have a preference.
Joe Walker wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I think we need a better bug tracker than bugs.txt, because I bet my
edits will crash with yours, and because leading up to 1.0 it will
become important that we can prioritize our work.
Options I can think of:
- Install bugzilla at crosswire
- Install scarab at crosswire
- Install jira at crosswire (<a class="moz-txt-link-freetext" href="http://www.atlassian.com/software/jira/">http://www.atlassian.com/software/jira/</a>)
- Use the bugzilla that we have at sourceforge There are 3 SF projects
that we have, ProjectB, J-Sword (not set up by me, not even sure if
I'm an admin) and BibleDesktop (unused other that to book the name)
- Try to get an account at tigris.org or java.net to use their
instance of Scarab.
- Find someone willing to host Jira for us.
My experience of buzilla/scarab/jira is between small and
non-existent. I've setup bugzilla and scarab at work. Bugzilla is easy
on Linux, Scarab is somewhat harder.
The Scarab UI is probably better than the Buzilla one, and from the
Jira demo, it is way ahead of both of them.
I don't have strong feelings that we ought to use an OSS one - mostly
because, of the time I spend on this project, I want to minimize the
non-productive time. If we spend ages messing with scarab (or
something) then I'm not working on J-Sword, but if others do have
strong feelings then I'm not going to argue too much.
Thoughts?
----- Original Message -----
From: DM Smith <a class="moz-txt-link-rfc2396E" href="mailto:dmsmith555@yahoo.com"><dmsmith555@yahoo.com></a>
Date: Sat, 28 Aug 2004 00:39:05 -0400
Subject: Re: [jsword-devel] Bible Desktop Comments
To: Java SWORD Developers Mailing List <a class="moz-txt-link-rfc2396E" href="mailto:jsword-devel@crosswire.org"><jsword-devel@crosswire.org></a>
Most excellent. Thanks. Since I have been modifying bugs.txt (our
wish list and bug report list), I will add this to it. Maybe we should
check it in as is, along side of bugs.txt.
Eric Galluzzo wrote:
Folks, I just took the application for a fairly extensive test run --
my first in a long time! Here are some notes I took as I was doing so
about things that could be improved, and some suggestions for new
features. I should be able to help out with implementing some of these
suggestions too. (Famous last words....) Thanks, Eric
________________________________
_______________________________________________ jsword-devel mailing
list <a class="moz-txt-link-abbreviated" href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a>
<a class="moz-txt-link-freetext" href="http://www.crosswire.org/mailman/listinfo/jsword-devel">http://www.crosswire.org/mailman/listinfo/jsword-devel</a>
_______________________________________________
jsword-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a>
<a class="moz-txt-link-freetext" href="http://www.crosswire.org/mailman/listinfo/jsword-devel">http://www.crosswire.org/mailman/listinfo/jsword-devel</a>
_______________________________________________
jsword-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a>
<a class="moz-txt-link-freetext" href="http://www.crosswire.org/mailman/listinfo/jsword-devel">http://www.crosswire.org/mailman/listinfo/jsword-devel</a>
</pre>
</blockquote>
<pre wrap="">_______________________________________________
jsword-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a>
<a class="moz-txt-link-freetext" href="http://www.crosswire.org/mailman/listinfo/jsword-devel">http://www.crosswire.org/mailman/listinfo/jsword-devel</a>
</pre>
</blockquote>
<pre wrap=""><!---->_______________________________________________
jsword-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a>
<a class="moz-txt-link-freetext" href="http://www.crosswire.org/mailman/listinfo/jsword-devel">http://www.crosswire.org/mailman/listinfo/jsword-devel</a>
</pre>
</blockquote>
</body>
</html>