What is Bugzilla?

What is Bugzilla?
Bugzilla is a database with bugs. It allows users to report software bugs and forward them to appropriate developers. Developers can use Bugzilla to maintain
A priority table for what to do, as well as a timetable and tracking relevance.

Not all "buckets" are bugs. The content in some databases is used as an enhanced request (RFE ). An RFE is a critical level field set
The "bug" of "enhancement". People often say "bug", which actually refers to records in Bugzilla, so rfes is often called a bug. Based on Customer Enhancement
Bugzilla will help you track them and allow others to see what you will do. If others see your plan
They will avoid repeating your work and may help you solve the problem or give feedback to you.

Anatomy of a bug

Bugs and rfes are composed of many fields. The following are some introductions.
Component
Mozilla Applications consist of many different parts, such as network library functions, java scripts, and layout design engines.
Status Whiteboard
Used to write short bug notes
Keyword
Used to store some keywords.
Target milestone
Set by the person in charge of this bug
Dependency
If a bug can be repaired only after another bug is fixed, it is correlation.
Attachment
Adding an attachment is very useful. Test Events, screen display, and log records can help you identify bugs and help developers generate them again. If you
Fix the bug and install the patch with the bug. Because it makes it easy for others to find and test, it is a good way to track patches.

Survival cycle of a bug
Which of the following determines the report of a reported bug. The new Bugzilla account is created by default and has not been confirmed-this means that the QA department needs
It was found and confirmed before it was converted into a "new" bug. If you have been using Bugzilla for a while, I believe you know how to create a new
"Bug. When a bug becomes "new", developers may study the bug or accept or transfer it to others.
If this bug has not been handled in a week. Bugzilla will always harass its owner by email until it takes action. Whenever a bug is re-installed
When the specified content or content changes, its status is set back to "new ". The "New" status indicates that the bug is re-added to the work of a special developer.
The bug was reported again.
Those with permissions can modify all records of a bug (by default, you can only modify some records ). Whenever you modify a bug, you 'd better add some comments to solve it.
Explain what you are doing and why you are doing it. Every time you do something, such as modifying the content, re-assigning bugs, creating attachments, adding relevance and
The person made a backup and should make a note. When some people modify the bug report or add a comment, they will be added to the CC list, and the changes in the bug report will display
The email is displayed in the email to be sent to the owner, writer, and CC list.

When a bug is fixed, it is marked with resolved and has the following decisions.
Fixed
The bug fix has been written to the database and marked as fixed by the tested person.
Invalid
The problem described is not a bug or a Mozilla bug.
Wontfix
The problem described will never be fixed.
Later
The problem described will not be solved in the product version.
Remind
The problem described may not be solved in the product version, but it may also.
Duplicate
The problem described is a replica of an existing bug. The bug number marked as the bug that requires the bug to be restored. A comment and bug number will be added to the bug review.
.
Worksforme
All attempts to reproduce this bug are invalid. If more information appears, re-allocate the bug and archive it.
Moved
This bug is for a special mozilla-based version without affecting the mozilla.org code. This bug has been transferred to those that affect the origin of Mozilla.
The publisher's database.

QA finds the bugs that solves the problem and ensures that the correct method has been taken. If they agree, the bug is marked as verified. Before the product is released
The bugs remains in this status and is marked as closed. The bugs can return to reopened again.
When changing the bugs of others, pay attention to it. It is usually better to mark what you want to change as a comment so that the owner of the bug can see this and fix it by himself.
Change. For example, if you think a bug is a duplicate of another one, make a note in the additional comments section.
If you make a lot of useful comments to some people's bugs, they may trust your judgment and want you to modify them directly, but unless they wish
Yes, you 'd better be careful and just comment.

Bugzilla is open source software. Its source code complies with Mozilla Public License.

If your machine already has MySQL and MySQL-related Perl packages, the installation is very straightforward. If you have not installed these basic
Software, the first thing you need to do is install them. The next thing is to create a web server to run CGI scripts.
To run Bugzilla correctly, install the following software:
1. MySQL server and client software.
2. Perl (5.004 or later ).
3. DBI Perl module.
4. Data: dumper Perl module.
5. MySQL related Perl module collection.
6. TimeDate Perl module collection.
7. Gd Perl module (1.18 or later)
8. Chart: Base Perl module (0.99 or later ).
9. web server software of your choice
1.1 download and create a MySQL database.
MySQL databases are installed in most Linux versions by default, which is not described here. However, if you need mysqld to receive a 64 K long package
Add "-O max_allowed_packet = 1 m ".
1.2 Perl (5.004 or later)
The same is true.
1.3dbi Perl Module
The DBI module is a general Perl module used by other database-related Perl modules. After downloading this module.
1. Unpack the package to a directory.
2. Enter the following command:
Perl makefile. pl
Make
Make Test
Make install
This applies to the installation of Most Perl modules. If there is no error, proceed to the next step.
1.4 data: dumper Perl Module
This module provides data structure consistency for Perl. The installation process after download is the same as above.
1.5 MySQL related Perl module collection
Install the same as above. Note that only MySQL is selected, and msql is not selected.
1.6 TimeDate Perl module collection
The installation is the same as above.
1.7gd Perl module (1.18 or later)
Do not forget to download the GD module while downloading the gd-1.8.3, unpackage and copy the path_gd.pl In the GD package to the gd-1.8.3 directory, and execute Perl
Path_gd.pl, then compile in the gd-1.8.3 first
#./Configure -- enable-JPEG -- enable-FreeType -- enable-XPM
# Make
# Make install
Then, go to the GD directory and compile the Perl module as above.
1.8 chart: Base Perl module (version 0.99 or later)
After the download, the DBI module compilation process is the same.
1.9http server program settings.
Unpackage the bugzilla program to a directory, and add ScriptAlias/Bugzilla to SRM. conf in HTTP server settings.
"/Home/httpd/Bugzilla/", in access. conf, the bugzilla Directory should have the options execcgi option.
2. Install the bugzilla File
You should unpack the bugzilla file to a directory that can be written by the owner (probably nobody) of the default web server.
3. Create a MySQL database
Bugzilla often logs on to the user "bugs" without a password. It is complicated to maintain MySQL permissions. I have disabled them. If you want to do the same
Run the following command (replace hostname with the name of the machine running MySQL)
# MySQL
Delete from host;
Delete from user;
Insert into host values ('localhost', '%', 'y ', 'y', 'y ');
Insert into host values (hostname, '%', 'y ', 'y', 'y', 'y ');
Insert into user values
('Localhost', 'root', '', 'y ', 'y', 'y ');
Insert into user values (hostname, '','', 'y ', 'y', 'y ');
Insert into user values
(Hostname, 'root', '', 'y ', 'y', 'y ');
Insert into user values
('Localhost', '','', 'y ', 'y', 'y ');

The quantity of "Y" depends on the version. Version 3.22.23b is correct. After running, run mysqladmin reload to reload the license list.
The line of the magic checksetup. pl script is very appealing to Holger.
Schurig writes this script, which will reasonably set permissions and create a "data" directory. When it runs for the first time, it will create a file named "localconfig,
You may need to check and modify it. re-run this script and it will actually work. If the database is not successfully created, you may need to manually create the database and use it
The script in the MySQL directory under the bugzilla directory creates a table. (there may be a small problem. I believe it will be easy to solve if you know some SQL statements)
If all of these are successful, you can use web browsing. You need to register first (the first 11 users are special users, there are parameters to change, add project and other functions), and enter
Enter your email address, and it will call Sendmail (that is, you need to install Sendmail, or you have to change the program) to send your password to your mailbox
In the future, you will use this password to log on. Also, the bugzilla for MySQL is downloaded from RedHat. If you want to use it, you have to change it by yourself.
Interface, you should also consider MySQL security. I will not talk about it here.
The above tests were completed on turbolinux workstation 6.1. The download URL is as follows.

Appendix A. Required Software Download Links

All of these sites are current as of February 17,199 9. Hopefully
They'll stay current for a while.

MySQL: http://www.mysql.org

Perl: http://www.perl.org

CPAN: http://www.cpan.org

DBI Perl module: ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/DBI/

Data: dumper module:
Ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Data/

MySQL related Perl modules:
Ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Mysql/

TimeDate Perl module collection:
Ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Date/

GD Perl module: ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/GD/

Chart: base module:
Ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Chart/

RedHat Bugzilla: ftp://people.redhat.com/dkl/