Re: [ros-general] Bug-tracking systems

[Casper H. <ch...@us...>]

s=F8n, 2002-05-05 kl. 17:06 skrev KJK::Hyperion:
> At 14.53 05/05/2002, you wrote:
>=20
> First of all, I've found a bug in Scarab: it doesn't prevent accidental=20
> double submission of an issue (double-click on the submit button). Maybe =
it=20
> should assign an internal non-sequential id/GUID to every issue in additi=
on=20
> to the id (but it sounds more and more complicated as I write it)

Yes, this feature is missing.

>=20
> >Bugzilla is perl based and Scarab is based on Java servlet technology.
>=20
> Frankly, I don't give a damn ;-) Seriously, I think the only that should =
be=20
> worried about an implementation are the implementors (maintainers and=20
> contributors) and the deployers (administrators). We users don't care as=20
> long as it looks cool and it's easy to use ;-) Entirely your choice here,=
 IMHO

You are right about this.

> >* Scarab is more generel in it's choice of names and more flexible. In=20
> >Bugzilla you create bug reports, in Scarab you create issues. In Scarab=20
> >you can define an issue called bug report and define your own attributes=
=20
> >for this issue (like description, sverity and status). You can even defi=
ne=20
> >their input type (basicly how they are displayed) to string, integer,=20
> >drop-down list, etc. And best of all, they are searchable too!
>=20
> Actually, I find Scarab's terminology still very confusing. For example, =
in=20
> all bug tracking systems I come across, I measure how hard is finding out=
=20
> ALL bugs/issues in a module, sorted by date. Sadly, in Scarab it's still=20
> very counter-intuitive, and I have to resort to the help to find out how =
to=20
> do it

Having not used any bug-tracking system before I find neither of the two
terminologies harder than the other.

It seems that you can search for issues in a date range, but they only
be sorted by issue ID (ascending or descending). To see the creation
date for an issue you must click on it.

>=20
> And some templates/schemas have to be customized for ReactOS. For example=
,=20
> the "operating system" attribute doesn't really make sense for issues in=20
> the core OS module ;-)

Yes, the difference is that with Bugzilla we have to change the perl
code to remove this attribute. In Scarab, we just don't add it ;o)

>=20
> >* And finally, the Scarab UI look is kick ass nice ;o)
>=20
> Right. I think it's even better than reactos.com's (personal opinion: tho=
se=20
> blurred bitmaps and pastel colors suck). Still, Wine HQ's site is cooler=20
> than both ;-)
>=20
> We should (could?) standardize on a color/font scheme, for the web site a=
nd=20
> user interface. I mean, IBM has the white and deep blue, Microsoft has th=
e=20
> sky blue and sand gray, Sun has the eggplant purple and gray, etc. We hav=
e=20
> a logo (well, if the radioactive warning symbol is definitive ;-), we mis=
s=20
> a color scheme

I agree, is there an artist on the list?