5dc53c472d
------------------------------------- - 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)
24 lines
884 B
Text
24 lines
884 B
Text
===========================================================================
|
|
$NetBSD: MESSAGE,v 1.5 2017/03/17 16:26:30 mef Exp $
|
|
|
|
To complete the setup you will need to read the Bugzilla-Guide.txt in order
|
|
to setup Database counter-part properly. In particular secion 2.2.2 of the
|
|
document deals with database setup. After the initial setup of the database
|
|
you can then check the settings in ${BZDIR}/localconfig and with super user
|
|
privilege,
|
|
|
|
cd ${BZDIR};
|
|
./checksetup.pl
|
|
|
|
You will need to make Bugzilla accessible through your HTTP server.
|
|
If you are running Apache then you may add the following lines to httpd.conf:
|
|
|
|
Include ${PKG_SYSCONFDIR}/bugzilla.conf
|
|
|
|
to make Bugzilla accessible through:
|
|
|
|
http://localhost/bugzilla/index.cgi
|
|
|
|
IMPORTANTLY: CHANGE YOUR DATABASE PASSWORD FROM THE DEFAULT !!
|
|
|
|
===========================================================================
|