From fab1e128fd61a78809ee967279e8acc6b6962f1e Mon Sep 17 00:00:00 2001 From: Frédéric Buclin Date: Tue, 19 Feb 2013 10:06:36 +0100 Subject: Bug 832262: Release notes for Bugzilla 4.4rc2 r=dkl a=LpSolit --- template/en/default/pages/release-notes.html.tmpl | 70 ++++++++++++++++++++++- 1 file changed, 67 insertions(+), 3 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 3972723f0..5fab4615c 100644 --- a/template/en/default/pages/release-notes.html.tmpl +++ b/template/en/default/pages/release-notes.html.tmpl @@ -81,7 +81,7 @@

Required Perl Modules

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

Optional Perl Modules

@@ -116,6 +116,8 @@

New Features and Improvements

+ + +

+ In the "Advanced Search" page, it is now possible to build queries using + multiple custom search criteria against the same field. In [% terms.Bugzilla %] + 4.2 and older, queries of the form +

+ "Status changed to VERIFIED" AND "Status changed by foo@bar.com" +

+ were returning all [% terms.bugs %] which had their status changed to VERIFIED + by some user and which were edited by foo@bar.com once, but both actions could + be independent. In [% terms.Bugzilla %] 4.4, you can now decide if both + criteria must match the exact same action or not, i.e. if you want + [%+ terms.bugs %] whose status has been set to VERIFIED by foo@bar.com himself. + In the same way, queries of the form +

+ "Flags changed to approval+" AND "Flags changed by foo@bar.com" +

+ can now return [% terms.bugs %] for which the approval flag has been set to + "+" by foo@bar.com himself. In previous versions, both actions were treated + independently and [% terms.bugs %] for which foo@bar.com set the approval flag + to "?" and which is then set to "+" by someone else were also returned. +

+

+ This new feature gives you the ability to build more accurate queries and to + get more relevant results. +

+ +

Improved Performance for Searches

+ +

+ The search system got a performance boost which in some cases decreases the + time spent to run queries from several minutes to a few seconds only. + The more complex your queries are, and the more visible the performance win + should be. +

+

Overhaul of the Tagging System

@@ -266,6 +305,8 @@ are no longer resolved to their [% terms.bug %] ID, meaning that it is no longer possible to connect an alias with its ID unless you can see the [%+ terms.bug %]. +

  • Searches: Custom multi-select fields are now available + in the "Search By Change History" section of the query page.
  • Searches: The changed by operator in boolean charts now accepts pronouns.
  • Searches: The requester and requestee fields in boolean @@ -283,6 +324,9 @@ notifications when the product or component of [% terms.abug %] changes.
  • Email Notifications: All [% terms.bug %]mails now have a X-Bugzilla-Flags email header, listing currently set flags.
  • +
  • Email Notifications: All [% terms.bug %]mails now have + a X-Bugzilla-Version email header with the current product + version.
  • Whining: The sort order of the saved search is used to sort [% terms.bugs %] in the emails.
  • User Accounts: To confirm an email address change, the @@ -297,6 +341,9 @@ X-Priority email headers to increase or decrease the initial priority of the [% terms.bug %], unless the priority is already explicitly set in the email itself.
  • +
  • Skins: [% terms.Bugzilla %] no longer fetches all skins + available when viewing a page. It only loads the skin selected by the user + in his preferences, which results in less requests to the server.
  • Enhancements for Administrators and Developers

    @@ -330,6 +377,9 @@
  • Administration: Target milestones can now be 64 characters long, for consistency with versions (previously was limited to 20 characters only).
  • +
  • Administration: The result code returned by + contrib/bugzilla-queue.rhel when it's not running is now 2 + instead of 0.
  • Database: Support for Oracle has been greatly improved.
  • Security: For improved security, the "X-Content-Type-Options: nosniff" and "X-XSS-Protection: block" @@ -347,6 +397,8 @@ B[%%]ugzilla.parameters, B[%%]ugzilla.last_audit_time, Classification.get, Group.update, Product.update, User.update.
  • +
  • B[%%]ug.add_attachment now only returns the ID of the newly + created attachments instead of all the attachment data.
  • B[%%]ug.attachments now also returns the size field containing the size of the attachment.
  • B[%%]ug.attachments and B[%%]ug.get now return @@ -436,6 +488,9 @@ tables and columns are joined in queries. In combination with the buglist_columns hook, this permits to customize the list of columns to display in buglists.
  • +
  • There is a new code hook bug_start_of_update which is called + after object_end_of_update but before bug_end_of_update + for a better control on how to update [% terms.bugs %].
  • There is a new code hook bug_url_sub_classes to support additional URLs in the See Also field.
  • There is a new code hook error_catch to catch errors thrown @@ -446,6 +501,15 @@
  • It is now illegal to have a product with no components and no versions. Trying to delete the last component or version of a product is now rejected.
  • +
  • Trying to set the component, target milestone or version of [% terms.abug %] + to a disabled value is no longer accepted. The change will be rejected.
  • +
  • The comment box now checks the returned value of check_can_change_field() + to determine if it should be displayed or not. This means its visibility + can now be controlled by the bug_check_can_change_field hook.
  • +
  • Flags now checks the returned value of check_can_change_field() to + determine if they should appear as editable or not. This means their + visibility can now be controlled by the bug_check_can_change_field + hook.
  • Quips can no longer exceed 512 characters. Existing quips longer than that are automatically truncated when upgrading.
  • The static bugzilla.dtd file has been replaced by a dynamic @@ -467,8 +531,8 @@
  • It is now legal to call B[%%]ugzilla::Version->check({ id => $id }) and B[%%]ugzilla::Milestone->check({ id => $id }) to validate and get an object using its ID.
  • -
  • Rows in the dependencies DB table are now enforced to be - unique.
  • +
  • Rows in the dependencies, flaginclusions and + flagexclusions DB tables are now enforced to be unique.
  • The b[%%]ugs_activity and profiles_activity DB tables now have an auto-incremented primary key named id.
  • A custom B[%%]ugzilla.pm module has been added into -- cgit v1.2.3-24-g4f1b