Name
Last commit
Last update
Bugzilla Bug 507493: checksetup.pl's output should use colors for missing and too old Perl modules - Patch by FrÃ:copyright::copyright:ric Buclin <LpSolit@gmail.com> r/a=mkanat
contrib Bug 493090 - Product disallownew should be converted to isactive
docs Bug 507957: Bugzilla admins should not create templates in the "default" directory on customization - Patch by A.A. Shimono (himorin) <shimono@mozilla.gr.jp> r/a=mkanat
extensions/example Bug 508199: A hook for page.cgi
images Bug 132383: Bugzilla should have a default favicon - Patch by Guy Pyrzak <guy.pyrzak@gmail.com> r/a=mkanat
js Bug 477464: Move JS code out of attachment/edit.html.tmpl - Patch by Nitish Bezzala <nbezzala@yahoo.com> r/a=LpSolit
lib Bug 399954: Make Bugzilla able to hold its dependencies in a local directory
skins Bug 504522: The search field on index.cgi is not cleared automatically when entering the field (IE 7 and older only) - Patch by FrÃ:copyright::copyright:ric Buclin <LpSolit@gmail.com> r=pyrzak r=mkanat a=LpSolit
t Bug 507389: [SECURITY] Users can see all products when editing bugs - Patch by FrÃ:copyright::copyright:ric Buclin <LpSolit@gmail.com> r=mkanat a=LpSolit
template Bug 507493: checksetup.pl's output should use colors for missing and too old Perl modules - Patch by FrÃ:copyright::copyright:ric Buclin <LpSolit@gmail.com> r/a=mkanat
.cvsignore Bug 396243: Allow extensions (aka plugins) to extend the WebService interface
Bugzilla.pm Bug 499103 - page_requires_login check uses undefined variable
QUICKSTART Bug 400729 Quick start guide suggests changing os list in localconfig
README Bug 503543: Merge README, QUICKSTART, UPGRADING - Patch by FrÃ:copyright::copyright:ric Buclin <LpSolit@gmail.com> r/a=mkanat
UPGRADING CHANGES move to "UPGRADING-pre-2.8"
UPGRADING-pre-2.8 Bug 409598: Explain our version numbers in UPGRADING-pre-2.8
admin.cgi Bug 399954: Make Bugzilla able to hold its dependencies in a local directory
attachment.cgi Bug 509045: Make "use_keywords" a global template variable instead of having to pass it to templates all the time
buglist.cgi Bug 509045: Make "use_keywords" a global template variable instead of having to pass it to templates all the time
bugzilla.dtd Bug 366059: Include the attachment size when viewing bugs in the XML format - Patch by FrÃ:copyright::copyright:ric Buclin <LpSolit@gmail.com> r=bkor a=myk
chart.cgi Bug 464992: Binary attachments, graphical reports and new charts are not displayed correctly on Windows - Patch by FrÃ:copyright::copyright:ric Buclin <LpSolit@gmail.com> r=mkanat a=LpSolit
checksetup.pl Bug 507493: checksetup.pl's output should use colors for missing and too old Perl modules - Patch by FrÃ:copyright::copyright:ric Buclin <LpSolit@gmail.com> r/a=mkanat
colchange.cgi Bug 509045: Make "use_keywords" a global template variable instead of having to pass it to templates all the time
collectstats.pl Bug 491467: Make Search.pm and buglist.cgi consistently take column ids for the "fields" and "order" arguments, to prevent problems with using SQL fragments in the order and columnlist.
config.cgi Bug 471880: More scripts should use the shadow DB instead of the master DB - Patch by FrÃ:copyright::copyright:ric Buclin <LpSolit@gmail.com> r=mkanat a=LpSolit
createaccount.cgi Loading commit data...
describecomponents.cgi Loading commit data...
describekeywords.cgi Loading commit data...
duplicates.cgi Loading commit data...
duplicates.xul Loading commit data...
editclassifications.cgi Loading commit data...
editcomponents.cgi Loading commit data...
editfields.cgi Loading commit data...
editflagtypes.cgi Loading commit data...
editgroups.cgi Loading commit data...
editkeywords.cgi Loading commit data...
editmilestones.cgi Loading commit data...
editparams.cgi Loading commit data...
editproducts.cgi Loading commit data...
editsettings.cgi Loading commit data...
editusers.cgi Loading commit data...
editvalues.cgi Loading commit data...
editversions.cgi Loading commit data...
editwhines.cgi Loading commit data...
editworkflow.cgi Loading commit data...
email_in.pl Loading commit data...
enter_bug.cgi Loading commit data...
importxml.pl Loading commit data...
index.cgi Loading commit data...
install-module.pl Loading commit data...
jobqueue.pl Loading commit data...
jsonrpc.cgi Loading commit data...
long_list.cgi Loading commit data...
mod_perl.pl Loading commit data...
page.cgi Loading commit data...
post_bug.cgi Loading commit data...
process_bug.cgi Loading commit data...
productmenu.js Loading commit data...
query.cgi Loading commit data...
quips.cgi Loading commit data...
relogin.cgi Loading commit data...
report.cgi Loading commit data...
reports.cgi Loading commit data...
request.cgi Loading commit data...
robots.txt Loading commit data...
runtests.pl Loading commit data...
sanitycheck.cgi Loading commit data...
sanitycheck.pl Loading commit data...
search_plugin.cgi Loading commit data...
setup.cgi Loading commit data...
show_activity.cgi Loading commit data...
show_bug.cgi Loading commit data...
showattachment.cgi Loading commit data...
showdependencygraph.cgi Loading commit data...
showdependencytree.cgi Loading commit data...
sidebar.cgi Loading commit data...
summarize_time.cgi Loading commit data...
testagent.cgi Loading commit data...
testserver.pl Loading commit data...
token.cgi Loading commit data...
userprefs.cgi Loading commit data...
votes.cgi Loading commit data...
whine.pl Loading commit data...
whineatnews.pl Loading commit data...
xml.cgi Loading commit data...
xmlrpc.cgi Loading commit data...
What is Bugzilla?
=================
Bugzilla is a free bug-tracking system that is developed by an active
community of volunteers in the Mozilla community. You can install and
use it without having to pay any license fee.

Minimum requirements
====================
It can be installed on Windows, Mac OS X, Linux and other Unix flavors.
Bugzilla is written in Perl, meaning that Perl must be installed on your system.
You will also need a web server as well as a DB server (see below).

Installation & Upgrading
========================
The documentation to install, upgrade, configure and use Bugzilla can be found
in different formats:
* docs/en/html/Bugzilla-Guide.html (HTML version)
* docs/en/txt/Bugzilla-Guide.txt (text version)
* docs/en/pdf/Bugzilla-Guide.pdf (PDF version)

If the documentation is missing, you can get it online by visiting
http://www.bugzilla.org/docs/ from where you can select the documentation
corresponding to the Bugzilla version you are installing.

Bugzilla Quick Start Guide
==========================
(or, how to get Bugzilla up and running in 10 steps)
Christian Reis <kiko@async.com.br>

This express installation guide is for "normal" Bugzilla installations,
which means a Linux or Unix system on which Apache, Perl, MySQL or PostgreSQL
and a Sendmail compatible MTA are available. For other configurations, please
see the "Installing Bugzilla" section of the Bugzilla Guide in the docs/ directory.

1. Decide from which URL and directory under your webserver root you
   will be serving the Bugzilla webpages.

2. Unpack the distribution into the chosen directory (there is no copying or
   installation involved).

3. Run ./checksetup.pl, look for unsolved requirements, and install them.
   You can run checksetup as many times as necessary to check if
   everything required has been installed.

   These will usually include assorted Perl modules, MySQL or PostgreSQL,
   and a MTA.

   After a successful dependency check, checksetup should complain that
   localconfig needs to be edited.

4. Edit the localconfig file, in particular the $webservergroup and
   $db_* variables. In particular, $db_name and $db_user will define
   your database setup in step 5.

5. Create a user permission for the name supplied as $db_user with
   read/write access to the database whose name is given by $db_name.

   If you are not familiar with MySQL permissions, it's a good idea to
   use the mysql_setpermission script that is installed with the MySQL
   distribution, and be sure to read Bugzilla Security - MySQL section
   in the Bugzilla Guide or PostgreSQL documentation.

6. Run checksetup.pl once more; if all goes well, it should set up the
   Bugzilla database for you. If not, return to step 5.

   checksetup.pl should ask you, this time, for the administrator's
   email address and password. These will be used for the initial
   Bugzilla administrator account.

7. Configure Apache (or install and configure, if you don't have it up
   yet) to point to the Bugzilla directory. You can choose between
   mod_cgi and mod_perl. The Bugzilla documentation has detailed information
   for both modes.

8. Visit the URL you chose for Bugzilla. Your browser should display the
   default Bugzilla home page. You should then log in as the
   administrator by following the "Log in" link and supplying the
   account information you provided in step 6.

9. Visit the "Parameters" page, as suggested by the page displayed to you.
   Set up the relevant parameters for your local setup.

10. That's it. If anything unexpected comes up:

    - read the error message carefully,
    - backtrack through the steps above,
    - check the official installation guide.

Support and installation questions should be directed to the
support-bugzilla@lists.mozilla.org mailing list.

Further support information is at http://www.bugzilla.org/support/