1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
|
<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN">-->
<chapter id="variants" xreflabel="Bugzilla Variants and Competitors">
<title>Bugzilla Variants and Competitors</title>
<para>I created this section to answer questions about Bugzilla
competitors and variants, then found a wonderful site which covers
an awful lot of what I wanted to discuss. Rather than quote it in
its entirety, I'll simply refer you here: <ulink
url="http://linas.org/linux/pm.html">http://linas.org/linux/pm.html</ulink></para>
<section id="rhbugzilla" xreflabel="Red Hat Bugzilla">
<title>Red Hat Bugzilla</title>
<para>
Red Hat Bugzilla is probably the most popular Bugzilla variant
on the planet. One of the major benefits of Red Hat Bugzilla is
the ability to work with Oracle, MySQL, and PostGreSQL databases
serving as the back-end, instead of just MySQL. Dave Lawrence
has worked very hard to keep Red Hat Bugzilla up-to-date, and
many people prefer the snappier-looking page layout of Red Hat
Bugzilla to the default Mozilla-standard formatting.
</para>
<para>URL: <ulink
url="http://bugzilla.redhat.com/bugzilla/">http://bugzilla.redhat.com/bugzilla/</ulink></para>
</section>
<section id="variant-fenris" xreflabel="Loki Bugzilla, a.k.a. Fenris">
<title>Loki Bugzilla (Fenris)</title>
<para>Fenris can be found at <ulink
url="http://fenris.lokigames.com/">http://fenris.lokigames.com</ulink>. It is a fork from Bugzilla.</para>
</section>
<section id="variant-issuezilla" xreflabel="Issuezilla">
<title>Issuezilla</title>
<para>Issuezilla is another fork from Bugzilla, and seems nearly
as popular as the Red Hat Bugzilla fork. Some Issuezilla team
members are regular contributors to the Bugzilla mailing
list/newsgroup. Issuezilla is not the primary focus of
bug-tracking at tigris.org, however. Their Java-based
bug-tracker, <xref linkend="variant-scarab" />, is under heavy development
and looks promising!</para>
<para>URL: <ulink url="http://issuezilla.tigris.org/servlets/ProjectHome">http://issuezilla.tigris.org/servlets/ProjectHome</ulink></para>
</section>
<section id="variant-scarab" xreflabel="Scarab, a newfangled Java-based issue tracker">
<title>Scarab</title>
<para>Scarab is a promising new bug-tracking system built using
Java Serlet technology. As of this writing, no source code has
been released as a package, but you can obtain the code from
CVS.
</para>
<para>URL: <ulink url="http://scarab.tigris.org/">http://scarab.tigris.org</ulink></para>
</section>
<section id="variant-perforce" xreflabel="Using Perforce to track bugs">
<title>Perforce SCM</title>
<para>Although Perforce isn't really a bug tracker, it can be used
as such through the <quote>jobs</quote> functionality.</para>
<para><ulink
url="http://www.perforce.com/perforce/technotes/note052.html"></ulink>http://www.perforce.com/perforce/technotes/note052.html</para>
</section>
<section id="variant-sourceforge" xreflabel="SourceForge">
<title>SourceForge</title>
<para>SourceForge is more of a way of coordinating geographically
distributed free software and open source projects over the
Internet than strictly a bug tracker, but if you're hunting for
bug-tracking for your open project, it may be just what the
software engineer ordered!</para>
<para>URL: <ulink
url="http://www.sourceforge.net">http://www.sourceforge.net</ulink></para>
</section>
</chapter>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-always-quote-attributes:t
sgml-auto-insert-required-elements:t
sgml-balanced-tag-edit:t
sgml-exposed-tags:nil
sgml-general-insert-case:lower
sgml-indent-data:t
sgml-indent-step:2
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
sgml-minimize-attributes:nil
sgml-namecase-general:t
sgml-omittag:t
sgml-parent-document:("Bugzilla-Guide.sgml" "book" "chapter")
sgml-shorttag:t
sgml-tag-region-if-active:t
End:
-->
|
