dbschema.jpg file is changing, though. git-svn-id: svn://10.0.0.236/trunk@100828 18797224-902f-48f8-a5cc-f745e15eee43
196 lines
6.5 KiB
HTML
196 lines
6.5 KiB
HTML
<HTML
|
|
><HEAD
|
|
><TITLE
|
|
>Red Hat Bugzilla</TITLE
|
|
><META
|
|
NAME="GENERATOR"
|
|
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
|
|
"><LINK
|
|
REL="HOME"
|
|
TITLE="The Bugzilla Guide"
|
|
HREF="index.html"><LINK
|
|
REL="UP"
|
|
TITLE="Bugzilla Variants"
|
|
HREF="variants.html"><LINK
|
|
REL="PREVIOUS"
|
|
TITLE="Bugzilla Variants"
|
|
HREF="variants.html"><LINK
|
|
REL="NEXT"
|
|
TITLE="Useful Patches and Utilities for Bugzilla"
|
|
HREF="patches.html"></HEAD
|
|
><BODY
|
|
CLASS="SECTION"
|
|
BGCOLOR="#FFFFFF"
|
|
TEXT="#000000"
|
|
LINK="#0000FF"
|
|
VLINK="#840084"
|
|
ALINK="#0000FF"
|
|
><DIV
|
|
CLASS="NAVHEADER"
|
|
><TABLE
|
|
WIDTH="100%"
|
|
BORDER="0"
|
|
CELLPADDING="0"
|
|
CELLSPACING="0"
|
|
><TR
|
|
><TH
|
|
COLSPAN="3"
|
|
ALIGN="center"
|
|
>The Bugzilla Guide</TH
|
|
></TR
|
|
><TR
|
|
><TD
|
|
WIDTH="10%"
|
|
ALIGN="left"
|
|
VALIGN="bottom"
|
|
><A
|
|
HREF="variants.html"
|
|
>Prev</A
|
|
></TD
|
|
><TD
|
|
WIDTH="80%"
|
|
ALIGN="center"
|
|
VALIGN="bottom"
|
|
>Chapter 7. Bugzilla Variants</TD
|
|
><TD
|
|
WIDTH="10%"
|
|
ALIGN="right"
|
|
VALIGN="bottom"
|
|
><A
|
|
HREF="patches.html"
|
|
>Next</A
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
><HR
|
|
ALIGN="LEFT"
|
|
WIDTH="100%"></DIV
|
|
><DIV
|
|
CLASS="SECTION"
|
|
><H1
|
|
CLASS="SECTION"
|
|
><A
|
|
NAME="RHBUGZILLA"
|
|
>7.1. Red Hat Bugzilla</A
|
|
></H1
|
|
><P
|
|
> Red Hat Bugzilla is probably the most popular Bugzilla variant, aside from Mozilla Bugzilla,
|
|
on the planet.
|
|
One of the major benefits of Red Hat Bugzilla is the ability to work with Oracle as a
|
|
database, as well as MySQL.
|
|
Here's what Dave Lawrence had to say about the status of Red Hat Bugzilla,
|
|
<A
|
|
NAME="AEN2143"
|
|
></A
|
|
><BLOCKQUOTE
|
|
CLASS="BLOCKQUOTE"
|
|
><P
|
|
CLASS="LITERALLAYOUT"
|
|
> Hello. I apologize that I am getting back to you so late. It has been difficult to keep<br>
|
|
up with email this past week. I have checked out your updated documentation and I will<br>
|
|
have to say very good work. A few notes and additions as follows.<br>
|
|
<br>
|
|
(ed: from the FAQ)<br>
|
|
>For the record, we are not using any template type implementation for the cosmetic changes <br>
|
|
>maded to Bugzilla. It is just alot of html changes in the code itself. I admit I may have <br>
|
|
>gotten a little carried away with it but the corporate types asked for a more standardized <br>
|
|
>interface to match up with other projects relating to Red Hat web sites. A lot of other web <br>
|
|
>based internal tools I am working on also look like Bugzilla. <br>
|
|
<br>
|
|
<br>
|
|
This should probably be changed since we are now in fact using Text::Template for most<br>
|
|
of the html rendering. You actually state this later in your numbered list.<br>
|
|
<br>
|
|
Also number 6 contradicts number 8 where number 6 would be the most up to date status<br>
|
|
on the Oracle port.<br>
|
|
<br>
|
|
Additional Information:<br>
|
|
-----------------------------<br>
|
|
1. Comments are now stored in varchar fields of 4k in size each. If the comment is more<br>
|
|
than 4k it is broken up into chunks and given a sort number so each comment can be re<br>
|
|
assembled in the correct order. This was done because originally I was storing the comments<br>
|
|
in a long datatype which unfortunately cannot be indexed or joined with another table. This<br>
|
|
cause the search of text within the long description to be disabled for a long time. That<br>
|
|
is now working and is nto showing any noticeble performance hit that I can tell. <br>
|
|
<br>
|
|
2. Work is being started on internationalizing the Bugzilla source we have to allow our<br>
|
|
Japanese customers to enter bug reports into a single bugzilla system. This will probably<br>
|
|
be done by using the nvarchar data types supported by Oracle which allows storage of<br>
|
|
double byte characters and also the use of the Accept-Language in the http header for <br>
|
|
detection by Bugilla of which language to render.<br>
|
|
<br>
|
|
3. Of course even more cosmetic changes. It is difficult to keep up with the ever <br>
|
|
changing faces of www.redhat.com.<br>
|
|
<br>
|
|
4. Some convenience enhancements in the administration utilities. And more integration<br>
|
|
with other internal/external Red Hat web sites.<br>
|
|
<br>
|
|
I hope this information may prove helpful for your documentation. Please contact<br>
|
|
me if you have any more question or I can do anything else.<br>
|
|
<br>
|
|
Regards<br>
|
|
</P
|
|
></BLOCKQUOTE
|
|
>
|
|
</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="NAVFOOTER"
|
|
><HR
|
|
ALIGN="LEFT"
|
|
WIDTH="100%"><TABLE
|
|
WIDTH="100%"
|
|
BORDER="0"
|
|
CELLPADDING="0"
|
|
CELLSPACING="0"
|
|
><TR
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="left"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="variants.html"
|
|
>Prev</A
|
|
></TD
|
|
><TD
|
|
WIDTH="34%"
|
|
ALIGN="center"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="index.html"
|
|
>Home</A
|
|
></TD
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="right"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="patches.html"
|
|
>Next</A
|
|
></TD
|
|
></TR
|
|
><TR
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="left"
|
|
VALIGN="top"
|
|
>Bugzilla Variants</TD
|
|
><TD
|
|
WIDTH="34%"
|
|
ALIGN="center"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="variants.html"
|
|
>Up</A
|
|
></TD
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="right"
|
|
VALIGN="top"
|
|
>Useful Patches and Utilities for Bugzilla</TD
|
|
></TR
|
|
></TABLE
|
|
></DIV
|
|
></BODY
|
|
></HTML
|
|
> |