From 1c405dbab89089c11eaa3ef4347f7558805ec87d Mon Sep 17 00:00:00 2001 From: Frédéric Buclin Date: Thu, 8 Nov 2012 00:50:12 +0100 Subject: Bug 805645: Release notes for Bugzilla 4.4rc1 r=dkl --- template/en/default/pages/release-notes.html.tmpl | 699 +++++++++++++++++++++- 1 file changed, 687 insertions(+), 12 deletions(-) (limited to 'template') diff --git a/template/en/default/pages/release-notes.html.tmpl b/template/en/default/pages/release-notes.html.tmpl index d767a7a4e..3972723f0 100644 --- a/template/en/default/pages/release-notes.html.tmpl +++ b/template/en/default/pages/release-notes.html.tmpl @@ -6,7 +6,7 @@ # defined by the Mozilla Public License, v. 2.0. #%] -[% SET title = "$terms.Bugzilla 4.2 Release Notes" %] +[% SET title = "$terms.Bugzilla 4.4 Release Notes" %] [% INCLUDE global/header.html.tmpl title = title style_urls = ['skins/standard/page.css'] @@ -14,6 +14,471 @@

[% title FILTER html %]

+ + +

Introduction

+ +

Welcome to [% terms.Bugzilla %] 4.4! It has been almost a year since we + released [% terms.Bugzilla %] 4.2 on February 2012, and this new major + release comes with several new features and improvements. This release + contains major improvements to WebServices, which were our main target in + this release, a rewritten tagging system, a real MIME type auto-detection for + attachments, improved support for Oracle, performance improvements and lots + of other enhancements.

+ +

If you're upgrading, make sure to read Notes On + Upgrading From a Previous Version. If you are upgrading from a release + before 4.2, 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.

+ + + + +

Minimum Requirements

+ +

Any requirements that are new since 4.2 will look like + this.

+ + + +

Perl

+ +

Perl v5.8.1

+ +

IMPORTANT: This is the last major release to support + Perl 5.8.x! The next major release, [% terms.Bugzilla %] 5.0, will require + Perl 5.10.1 as a minimum.

+ +[% INCLUDE db_req db='mysql' %] + +[% INCLUDE db_req db='pg' dbd_new => 1 %] + +[% INCLUDE db_req db='oracle' %] + +[% INCLUDE db_req db='sqlite' %] + +

Required Perl Modules

+ +[% INCLUDE req_table reqs = REQUIRED_MODULES + updated = ['TimeDate', 'DBI', 'Email-Send'] %] + +

Optional Perl Modules

+ +

The following perl modules, if installed, enable various + features of [% terms.Bugzilla %]:

+ +[% INCLUDE req_table reqs = OPTIONAL_MODULES + new = ['Net-SMTP-SSL', 'HTML-FormatText-WithLinks', + 'File-MimeInfo', 'IO-stringy'] + include_feature = 1 %] + +

Optional Apache Modules

+ +

If you are using Apache as your webserver, [% terms.Bugzilla %] can + take advantage of some Apache features if you have the below Apache + modules installed and enabled. Currently, + certain [% terms.Bugzilla %] features + are enabled only if you have all of the following modules installed + and enabled:

+ + + +

On most systems (but not on Windows), checksetup.pl is able to + tell whether or not you have these modules installed, and it will tell + you.

+ + +

New Features and Improvements

+ + + +

Overhaul of the Tagging System

+ +

+ The old tagging system which was in the footer of all pages had severe design + and usability limitations and has been replaced by a shiny new one which lets + you tag [% terms.bugs %] from the [% terms.bug %] report directly. Tags now + mostly work like keywords, but with two major differences. First of all, they + are personal, meaning that tags you set on [% terms.bugs %] are only visible + by you, and nobody else is notified nor can see which tags you set. This + behavior is the same as the old tagging system and so this feature didn't + change. The second major difference is that the list of available tags is + unlimited and is in no way hardcoded by administrators. You can type either + a new tag of your choice, or you can select one from an auto-generated list + of tags which you already used in other [% terms.bugs %]. Again, this feature + was already present in the old tagging system, but its usability has been + greatly improved. In particular, this means that tags are now displayed in + [%+ terms.bug %] reports directly, so that you immediately know which tags + you already set for that [% terms.bug %]. This feature is new in this release. +

+

+ Another new feature is that your personal tags can now be listed in buglists. + They can also be used as search criteria in your queries. If you decide to + share a saved search which uses tags as criteria, this will work too! Note + that when you add a new tag, no saved search based on this tag is created + anymore, as you can easily create it yourself if you really need it. +

+

+ The tags set with the old tagging system are automatically migrated to the + new system. +

+ +

Auto-Detection of the Attachment MIME Type

+ +

+ When a user uploads a new attachment and lets the "Content Type" field set to + "auto-detect", [% terms.Bugzilla %] now does its own MIME type detection + if the web browser tells him that the attachment is of type + "application/octet-stream", in an attempt to make a better guess than the web + browser. In all other cases, [% terms.Bugzilla %] still trusts what the browser + tells him. +

+

+ Check the list of optional Perl modules to + know which modules to install in order to enable MIME type sniffing. +

+ +

Saving Tabular and Graphical Reports

+ +

+ It is now possible to save tabular and graphical reports in the same way as + you save searches. Saved reports will appear in the footer of pages, below + saved searches. +

+

+ Unlike saved searches, it is not yet possible to share saved reports with + other users. +

+ +

Custom Columns in Whine Emails

+ +

+ The list of columns to display in buglists contained in emails sent by the + whining system on a regular basis is no longer hardcoded. If the saved + search used for whining emails contains a list of columns, these columns are + used to be displayed in the emails. If no custom list is found, the default + column list is used instead. +

+

+ This means that depending on the kind of email notifications you want, you + can fully customize data to return, on a per saved search basis! +

+ +

Improved WebServices

+ +

+ This release got major improvements in its WebServices interface. Many new + methods have been implemented to let third-party applications interact with + [%+ terms.Bugzilla %] even more closely. For instance, it is now possible to + know what parameters are set to using B[%%]ugzilla.parameters. + It is now also possible to update tags, products, groups or user accounts + using our API. +

+

+ Several existing methods have also been improved to return data which + weren't available till now, such as [% terms.bug %] and attachment flags + using B[%%]ug.get, B[%%]ug.attachments or + Product.get. Users can also get their saved searches and reports + using User.get; and much more, see the + detailed list below. +

+ +

New Apache Configuration

+ +

+ For improved security, [% terms.Bugzilla %] now prevents directory browsing + by default. If you run [% terms.Bugzilla %] under Apache (as most people do), + you most likely require a new Apache configuration for this + version of [% terms.Bugzilla %]. See the + Notes On Upgrading From a Previous Version + section for details. +

+ +

Other Enhancements and Changes

+ +

Enhancements for Users

+ + + +

Enhancements for Administrators and Developers

+ + + +

WebService Changes

+ + + + +

Outstanding Issues

+ + + + +

Notes On Upgrading From a Previous Version

+ +

IMPORTANT: Apache Configuration Change

+ +

+ For improved security, [% terms.Bugzilla %] now prevents directory browsing + by default. In order to do that, the root bugzilla/.htaccess file + now contains the Options -Indexes directive. By default, this + directive is not allowed in .htaccess and so you must configure + Apache to allow it. To do that, add Options to the + AllowOverride directive in httpd.conf. This means you + should now have something like this: +

+ AllowOverride Limit FileInfo Indexes Options +

+ Check the + documentation + for more information about how to configure Apache. +

+ +

Code Changes Which May Affect Customizations and Extensions

+ + + + +

[% terms.Bugzilla %] 4.2 Release Notes

+