From: mkanat%bugzilla.org <> Date: Wed, 8 Jul 2009 10:09:22 +0000 (+0000) Subject: Bug 494037: Release Notes for Bugzilla 3.4rc1 X-Git-Tag: bugzilla-3.4rc1~2 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=65c164aa8109543cda32d2b1d26159d716e3884b;p=thirdparty%2Fbugzilla.git Bug 494037: Release Notes for Bugzilla 3.4rc1 Patch by Max Kanat-Alexander r=LpSolit, a=mkanat --- diff --git a/docs/lib/Pod/Simple/HTMLBatch/Bugzilla.pm b/docs/lib/Pod/Simple/HTMLBatch/Bugzilla.pm index ab298a05b7..c8309d70e1 100644 --- a/docs/lib/Pod/Simple/HTMLBatch/Bugzilla.pm +++ b/docs/lib/Pod/Simple/HTMLBatch/Bugzilla.pm @@ -31,8 +31,8 @@ BEGIN { *esc = \&Pod::Simple::HTML::esc } # Note that if you leave out a category here, it will not be indexed # in the contents file, even though its HTML POD will still exist. use constant FILE_TRANSLATION => { - Files => ['importxml', 'contrib', 'checksetup', 'email_in', 'install-module', - 'sanitycheck'], + Files => ['importxml', 'contrib', 'checksetup', 'email_in', + 'install-module', 'sanitycheck', 'jobqueue'], Modules => ['bugzilla'], Extensions => ['extensions'], }; diff --git a/template/en/default/pages/release-notes.html.tmpl b/template/en/default/pages/release-notes.html.tmpl index 3353ab45d1..6699018739 100644 --- a/template/en/default/pages/release-notes.html.tmpl +++ b/template/en/default/pages/release-notes.html.tmpl @@ -19,12 +19,464 @@ [% PROCESS global/variables.none.tmpl %] [% INCLUDE global/header.html.tmpl - title = "$terms.Bugzilla 3.2.3 Release Notes" + title = "$terms.Bugzilla 3.4 Release Notes" style_urls = ['skins/standard/release-notes.css'] %]

Table of Contents

+ + +

Introduction

+ +

This is [% terms.Bugzilla %] 3.4! [% terms.Bugzilla %] 3.4 brings a lot + of great enhancements for [% terms.Bugzilla %] over previous versions, + with various improvements to the user interface, lots of interesting new + features, and many long-standing requests finally being addressed.

+ +

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

+ +

We would like to thank Canonical + Ltd. for funding development of one new feature, and NASA for funding + development of several new features through the + San Jose State University + Foundation.

+ +

Minimum Requirements

+ +

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

+ + + +

Perl

+ +

Perl v5.8.1

+ +[% INCLUDE db_req db='mysql' %] + +[% INCLUDE db_req db='pg' %] + +[% INCLUDE db_req db='oracle' %] + +

Required Perl Modules

+ +[% INCLUDE req_table reqs = REQUIRED_MODULES + new = ['URI', 'DateTime', 'DateTime-TimeZone', + 'Digest-SHA'] + updated = [] %] + +

Optional Perl Modules

+ +

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

+ +[% INCLUDE req_table reqs = OPTIONAL_MODULES + new = ['TheSchwartz', 'Daemon-Generic'] + updated = [] + include_feature = 1 %] + +

New Features and Improvements

+ + + +

Simple [% terms.Bug %] Filing

+ +

When entering a new [% terms.bug %], the vast majority of fields are + now hidden by default, which enormously simplifies the bug-filing form. + You can click "Show Advanced Fields" to show all the fields, if you want + them. [%+ terms.Bugzilla %] remembers whether you last used the "Advanced" + or "Simple" version of the [% terms.bug %]-entry form, and will display the + same version to you again next time you file [% terms.abug %].

+ +

New Home Page

+ +

[% terms.Bugzilla %]'s front page has been redesigned to be better at + guiding new users into the activities that they most commonly want to + do. Further enhancements to the home page are coming in future versions + of [% terms.Bugzilla %].

+ +

Email Addresses Hidden From Logged-Out + Users

+ +

To help prevent spam to [% terms.Bugzilla %] users, all email addresses + stored in [% terms.Bugzilla %] are now displayed only if you are logged in. + If you are logged out, only the part before the "@" of the email address is + displayed. This includes [% terms.bug %] lists, viewing [% terms.bugs %], the + XML format of [% terms.abug %], and any other place in the web interface that + an email address could appear.

+ +

Email addresses are not filtered out of [% terms.bug %] comments. + The WebService still returns full email addresses, even if you are logged + out.

+ +

Shorter Search URLs

+ +

When submitting a search, all the unused fields are now stripped from + the URL, so search URLs are much more meaningful, and much shorter.

+ +

Asynchronous Email Sending

+ +

The largest performance problem in former versions of [% terms.Bugzilla %] + was that when updating [% terms.bugs %], email would be sent immediately + to every user who needed to be notified, and process_bug.cgi + would wait for the emails to be sent before continuing.

+ +

Now [% terms.Bugzilla %] is capable of queueing emails to be sent + while [% terms.abug %] is being updated, and sending them in the + background. This requires the administrator to run a daemon + that comes with [% terms.Bugzilla %], named + jobqueue.pl, + and to enable the + use_mailer_queue parameter.

+ +

Using the background email-sending daemon instead of sending mail directly + should result in a very large speed-up for updating [% terms.bugs %], + particularly on larger installations.

+ +

Dates and Times Displayed In User's Time + Zone

+ +

Users can now select what time zone they are in and [% terms.Bugzilla %] + will adjust displayed times to be correct for their time zone. However, + times the user inputs are unfortunately still in [% terms.Bugzilla %]'s + time zone.

+ +

Custom Fields That Only Appear When + Another Field Has a Particular Value

+ +

When creating a new custom field (or updating the definition of + an existing custom field), you can now say that "this field only + appears when field X has value Y". (In the future, you will be able + to select multiple values for "Y", so a field will appear when any + one of those values is selected.)

+ +

This feature only hides fields--it doesn't make their values go away. + So [% terms.bugs %] will still show up in searches for that field's + value, but the field won't appear in the user interface.

+ +

This is a good way of making Product-specific fields.

+ +

Custom Fields Whose List of Values + Change Depending on the Value of Another Field

+ +

When creating a drop-down or multiple-selection custom field, you can + now specify that another field "controls the values" of this field. + Then, when adding values to this field, you can say that a particular + value only appears when the other field is set to a particular + value.

+ +

Here's an example: Let's say that we create a field called "Colors", + and we make the Product field "control the values" for Colors. Then we + add Blue, Red, Black, and Yellow as legal values for the "Colors" field. + Now we can say that "Blue" and "Red" only appear as valid choices in + Product A, "Yellow" only appears in Product B, but "Black" always + appears.

+ +

One thing to note is that this feature only controls what values appear in + the user interface. [% terms.Bugzilla %] itself will still accept + any combination of values as valid, in the backend.

+ +

New Custom Field Type: [% terms.Bug %] + ID

+ +

You can now create a custom field that holds a reference to a single + valid [% terms.bug %] ID. In the future this will be enhanced to allow + [%+ terms.bugs %] to refer to each other via this field.

+ +

"See Also" Field

+ +

We have added a new standard field called "See Also" to + [% terms.Bugzilla %]. In this field, you can put URLs to multiple + [% terms.bugs %] in any [% terms.Bugzilla %] installation, to indicate + that those [% terms.bugs %] are related to this one. It also supports + adding URLs to [% terms.bugs %] in + Launchpad.

+ +

Right now, the field just validates the URLs and then displays them, but + in the future, it will grab information from the other installation about + the [% terms.bug %] and display it here, and possibly even update the + other installation.

+ +

If your installation does not need this field, you can hide it by disabling + the use_see_also + parameter.

+ +

Re-order Columns in Search Results

+ +

There is a new interface for choosing what columns appear in search + results, which allows you to change the order in which columns appear + from left to right when viewing the [% terms.bug %] list.

+ +

Search Descriptions

+ +

When displaying search results, [% terms.Bugzilla %] will now show + a brief description of what you searched for, at the top of the + [%+ terms.bug %] list.

+ +

Other Enhancements and Changes

+ +

Enhancements for Users

+ + + +

Enhancements for Administrators and Developers

+ + + +

WebService Changes

+ + + +

Outstanding Issues

+ + + +

Notes On Upgrading From a Previous + Version

+ +

When upgrading to 3.4, checksetup.pl will create foreign keys + for many columns in the database. Before doing this, it will check the + database for consistency. If there are an unresolvable consistency + problems, it will tell you what table and column in the database contain + the bad values, and which values are bad. If you don't know what else to do, + you can always delete the database records which contain the bad values by + logging in to your database and running the following command:

+ +

DELETE FROM table WHERE column IN + (1, 2, 3, 4)

+ +

Just replace "table" and "column" with the name of the table + and column that checksetup.pl mentions, and "1, 2, 3, 4" + with the invalid values that checksetup.pl prints out.

+ +

Remember that you should always back up your database before doing + an upgrade.

+ +

Code Changes Which May Affect + Customizations

+ + + + + + + + + +

[% terms.Bugzilla %] 3.2 Release Notes

+ +

Table of Contents

+ -

Release Notes For Previous Versions

- -

[% terms.Bugzilla %] 3.0.x Release Notes

+

[% terms.Bugzilla %] 3.0.x Release Notes

Table of Contents

@@ -611,7 +1191,7 @@ previous versions in between your version and this one.

-

Updates in this 3.0.x Release

+

Updates in this 3.0.x Release

This section describes what's changed in the most recent bug-fix releases of [% terms.Bugzilla %] after 3.0. We only list the @@ -1401,7 +1981,6 @@

[% terms.Bugzilla %] 3.0.4 contains three security fixes. For details, see the Security Advisory.

-

3.0.3

@@ -1625,7 +2204,7 @@ sub y { $var++ } [% BLOCK db_req %] [% SET m = DB_MODULE.$db %] -

For [% m.name FILTER html %] +

For [% m.name FILTER html %] Users