------------------------------------- - please note devel/bugzilla3 has now 3.6.8 - Below is a Release note for 5.0.1 to 5.0.3 from: https://www.bugzilla.org/releases/5.0.3/release-notes.html ------------------------------------- Bugzilla 5.0.3 Release Notes * Introduction * Updates in this 5.0.x Release .. (original has more sections, but omitted, see above URL for more info) Introduction Welcome to Bugzilla 5.0! It has been slightly over two years since we released Bugzilla 4.4 in May of 2013. This new major release comes with many new features and improvements to WebServices and performance. If you're upgrading, make sure to read Notes On Upgrading From a Previous Version. If you are upgrading from a release before 4.4, make sure to read the release notes for all the previous versions in between your version and this one, particularly the Upgrading section of each version's release notes. Updates in this 5.0.x Release 5.0.3 This release fixes one security issue. See the Security Advisory for details. This release also contains the following bug fixes: * A regression in Bugzilla 5.0.2 caused whine.pl to be unable to send emails due to a missing subroutine. (Bug 1235395) * The Encode module changed the way it encodes strings, causing email addresses in emails sent by Bugzilla to be encoded, preventing emails from being correctly delivered to recipients. We now encode email headers correctly. (Bug 1246228) * Fix additional taint issues with Strawberry Perl. (Bug 987742 and bug 1089448) * When exporting a buglist as a CSV file, fields starting with either "=", "+", "-" or "@" are preceded by a space to not trigger formula execution in Excel. (Bug 1259881) * An extension which allows user-controlled data to be used as a link in tabs could trigger XSS if the data is not correctly sanitized. Bugzilla no longer relies on the extension to do the sanity check. A vanilla installation is not affected as no tab is user-controlled. (Bug 1250114) * Extensions can now easily override the favicon used for the Bugzilla website. (Bug 1250264) 5.0.2 This release fixes two security issues. See the Security Advisory for details. This release also contains the following bug fixes: * mod_perl now works correctly with mod_access_compat turned off on Apache 2.4. To regenerate the .htaccess files, you must first delete all existing ones in subdirectories: find . -mindepth 2 -name .htaccess -exec rm -f {} \; You must then run checksetup.pl again to recreate them with the correct syntax. (Bug 1223790) * Emails sent by Bugzilla are now correctly encoded as UTF-8. (Bug 714724) * Strawberry Perl is now fully supported on Windows. (Bug 1089448 and bug 987742) * The XML-RPC API now works with IIS on Windows. (Bug 708252) * Some queries should now be faster on PostgreSQL. (Bug 1184431) 5.0.1 This release fixes one security issue. See the Security Advisory for details. This release also contains the following bug fixes: * Users whose login name is not an email address could not log in on installations which use LDAP to authenticate users. (Bug 1179160) * If a mandatory custom field was hidden, it was not possible to create a new bug or to edit existing ones. (Bug 1183398 and bug 1196969) * A user editing his login name to point to a non-existent email address could cause Bugzilla to stop working, causing a denial of service. (Bug 1194987) * Emails generated during a transaction made PostgreSQL stop working. (Bug 1186700) * Bugs containing a comment with a reference to a bug ID larger than 2^31 could not be displayed anymore using PostgreSQL. (Bug 1191937) * The date picker in the "Time Summary" page was broken. (Bug 1181649) * If Test::Taint or any other Perl module required to use the JSON-RPC API was not installed or was too old, the UI to tag comments was displayed anyway, you could tag comments, but tags were not persistent (they were lost on page reload). Now the UI to tag comments is not displayed at all until the missing Perl modules are installed and up-to-date. (Bug 1183227) * Custom fields of type INTEGER now accept negative integers. (Bug 1198659) * On Windows, the checksetup.pl installation script no longer asks for a SMTP server. It can be set after the installation is complete. (Bug 1191255)
90 lines
4.2 KiB
Text
90 lines
4.2 KiB
Text
|
|
# If you are using Apache as your web server, Bugzilla can create .htaccess
|
|
# files for you that will instruct Apache not to serve files that shouldn't
|
|
# be accessed from the web (like your local configuration data and non-cgi
|
|
# executable files). For this to work, the directory your Bugzilla
|
|
# installation is in must be within the jurisdiction of a <Directory> block
|
|
# in the httpd.conf file that has 'AllowOverride Limit' in it. If it has
|
|
# 'AllowOverride All' or other options with Limit, that's fine.
|
|
# (Older Apache installations may use an access.conf file to store these
|
|
# <Directory> blocks.)
|
|
# If this is set to 1, Bugzilla will create these files if they don't exist.
|
|
# If this is set to 0, Bugzilla will not create these files.
|
|
$create_htaccess = 1;
|
|
|
|
# This is the group your web server runs as.
|
|
# If you have a Windows box, ignore this setting.
|
|
# If you do not have access to the group your web server runs under,
|
|
# set this to "". If you do set this to "", then your Bugzilla installation
|
|
# will be _VERY_ insecure, because some files will be world readable/writable,
|
|
# and so anyone who can get local access to your machine can do whatever they
|
|
# want. You should only have this set to "" if this is a testing installation
|
|
# and you cannot set this up any other way. YOU HAVE BEEN WARNED!
|
|
# If you set this to anything other than "", you will need to run checksetup.pl
|
|
# asroot, or as a user who is a member of the specified group.
|
|
$webservergroup = '@BZ_WEB_GROUP@';
|
|
|
|
# What SQL database to use. Default is mysql. List of supported databases
|
|
# can be obtained by listing Bugzilla/DB directory - every module corresponds
|
|
# to one supported database and the name corresponds to a driver name.
|
|
$db_driver = '@DBDRIVER@';
|
|
|
|
# The DNS name of the host that the database server runs on.
|
|
$db_host = 'localhost';
|
|
|
|
# The name of the database
|
|
$db_name = 'bugs';
|
|
|
|
# Who we connect to the database as.
|
|
$db_user = 'bugs';
|
|
|
|
# Enter your database password here. It's normally advisable to specify
|
|
# a password for your bugzilla database user.
|
|
# If you use apostrophe (') or a backslash (\) in your password, you'll
|
|
# need to escape it by preceding it with a '\' character. (\') or (\)
|
|
# (Far simpler just not to use those characters.)
|
|
$db_pass = '';
|
|
|
|
# Sometimes the database server is running on a non-standard port. If that's
|
|
# the case for your database server, set this to the port number that your
|
|
# database server is running on. Setting this to 0 means "use the default
|
|
# port for my database server."
|
|
$db_port = 0;
|
|
|
|
# MySQL Only: Enter a path to the unix socket for MySQL. If this is
|
|
# blank, then MySQL's compiled-in default will be used. You probably
|
|
# want that.
|
|
$db_sock = '';
|
|
|
|
# Should checksetup.pl try to verify that your database setup is correct?
|
|
# (with some combinations of database servers/Perl modules/moonphase this
|
|
# doesn't work)
|
|
$db_check = 1;
|
|
|
|
# With the introduction of a configurable index page using the
|
|
# template toolkit, Bugzilla's main index page is now index.cgi.
|
|
# Most web servers will allow you to use index.cgi as a directory
|
|
# index, and many come preconfigured that way, but if yours doesn't
|
|
# then you'll need an index.html file that provides redirection
|
|
# to index.cgi. Setting $index_html to 1 below will allow
|
|
# checksetup.pl to create one for you if it doesn't exist.
|
|
# NOTE: checksetup.pl will not replace an existing file, so if you
|
|
# wish to have checksetup.pl create one for you, you must
|
|
# make sure that index.html doesn't already exist
|
|
$index_html = 0;
|
|
|
|
# For some optional functions of Bugzilla (such as the pretty-print patch
|
|
# viewer), we need the cvs binary to access files and revisions.
|
|
# Because it's possible that this program is not in your path, you can specify
|
|
# its location here. Please specify the full path to the executable.
|
|
$cvsbin = '@CVS@';
|
|
|
|
# For some optional functions of Bugzilla (such as the pretty-print patch
|
|
# viewer), we need the interdiff binary to make diffs between two patches.
|
|
# Because it's possible that this program is not in your path, you can specify
|
|
# its location here. Please specify the full path to the executable.
|
|
$interdiffbin = '@PREFIX@/bin/interdiff';
|
|
|
|
# The interdiff feature needs diff, so we have to have that path.
|
|
# Please specify the directory name only; do not use trailing slash.
|
|
$diffpath = '/usr/bin';
|