@@ -1637,10 +1637,10 @@
Optional Apache Modules
-If you are using Apache as your webserver, [% terms.Bugzilla %] can
+
If you are using Apache as your webserver, Bugzilla can
now take advantage of some Apache features if you have the below Apache
modules installed and enabled. Currently,
- certain [% terms.Bugzilla %] features
+ certain Bugzilla features
are enabled only if you have all of the following modules installed
and enabled:
@@ -1682,11 +1682,11 @@
[%+ terms.Bugs %]
When filing [% terms.abug %], as soon as you start typing in the summary
- field, [% terms.Bugzilla %] will suggest possible duplicates of the
+ field, Bugzilla will suggest possible duplicates of the
[%+ terms.bug %] you are filing.
In order for this feature to work, all pre-requisites for JSON-RPC
- support must be installed on your [% terms.Bugzilla %]. It will be
+ support must be installed on your Bugzilla. It will be
much faster on installations that run under mod_perl than it will
be on other installations.
@@ -1715,7 +1715,7 @@
[%+ field_descs.qa_contact FILTER html %], or
[%+ field_descs.assigned_to FILTER html %] fields), a list will appear
containing all of the users whose real names or usernames match what you are
- typing. Your [% terms.Bugzilla %] must have all of the optional Perl
+ typing. Your Bugzilla must have all of the optional Perl
modules required for JSON-RPC support installed, though, in order for
this feature to work. Also, this feature will be much
faster on installations that run under mod_perl than it will be on
@@ -1727,14 +1727,14 @@
General Usability Improvements
In addition to the enhancements listed above, there have been
- many improvements made across the [% terms.Bugzilla %]
+ many improvements made across the Bugzilla
user interface. For a list of specific enhancements that were significant,
see the Other Enhancements and Changes
section.
New Default Status Workflow
-For new installations of [% terms.Bugzilla %], the default set of
+
For new installations of Bugzilla, the default set of
statuses will now be:
@@ -1754,7 +1754,7 @@
can run after you use checksetup.pl to upgrade. The
whineatnews.pl and bugzilla-submit scripts
will probably not work properly if you continue to use the old workflow
- (though most other parts of [% terms.Bugzilla %] will still function
+ (though most other parts of Bugzilla will still function
normally).
For more information about the workflow and our rationale for changing
@@ -1766,25 +1766,25 @@
"Last Search" Now Remembers Multiple Searches
-At the top of every [% terms.bug %] in [% terms.Bugzilla %], there are
+
At the top of every [% terms.bug %] in Bugzilla, there are
links that look like: "First", "Last", "Prev", "Next", and
- "Show last search results". In earlier versions of [% terms.Bugzilla %],
+ "Show last search results". In earlier versions of Bugzilla,
if you did two separate searches in separate windows, these links would
- only work for the last search you did. Now, [% terms.Bugzilla %]
+ only work for the last search you did. Now, Bugzilla
will "remember" which search result you came from and give you the right
"last search results" or "next [% terms.bug %]" from that list,
instead of always using your most recent search.
-There are still some situations where [% terms.Bugzilla %] will have to
+
There are still some situations where Bugzilla will have to
"guess" which search you are trying to navigate through, but it does its
best to get it right.
Cross-Domain WebServices with JSONP
-[% terms.Bugzilla %] now supports making WebService calls from
+
Bugzilla now supports making WebService calls from
another domain, inside of a web browser, thanks to support for
JSONP.
- This will allow for web "mash-ups" to use [% terms.Bugzilla %] data.
+ This will allow for web "mash-ups" to use Bugzilla data.
When using JSONP, you may only call functions that get data,
you may not call functions that change data.
@@ -1809,46 +1809,46 @@
Voting Is Now An Extension
-All of the code for voting in [% terms.Bugzilla %] has been moved
+
All of the code for voting in Bugzilla has been moved
into an extension, called "Voting", in the extensions/Voting/
directory. To enable it, you must remove the disabled file
from that directory, and run checksetup.pl.
-In a future version of [% terms.Bugzilla %], the Voting extension will
- be moved outside of the [% terms.Bugzilla %] core code, so we are looking
+
In a future version of Bugzilla, the Voting extension will
+ be moved outside of the Bugzilla core code, so we are looking
for somebody who has an interest in the Voting system and would like to
maintain it as a separate extension. There are many enhancement requests
that have been made against the Voting system, and the best way for those
to get addressed is for somebody to step up and offer to maintain the
- system outside of [% terms.Bugzilla %]'s core code.
+ system outside of Bugzilla's core code.
Users Get New CSS and Javascript
Automatically
-In past versions of [% terms.Bugzilla %], if you changed
- [%+ terms.Bugzilla %]'s CSS or Javascript files, then every user of
- [%+ terms.Bugzilla %] would have to clear their cache in order to get
+
In past versions of Bugzilla, if you changed
+ Bugzilla's CSS or Javascript files, then every user of
+ Bugzilla would have to clear their cache in order to get
the updated files. Now, if you are using Apache as your webserver and
you have the optional Apache modules
installed and enabled, users will automatically get every new version of
- [%+ terms.Bugzilla %]'s Javascript and CSS without having to clear
+ Bugzilla's Javascript and CSS without having to clear
their caches.
This feature also gives a slight performance speedup to
- [%+ terms.Bugzilla %] in some cases, and so we recommend that all
+ Bugzilla in some cases, and so we recommend that all
administrators install and enable the optional Apache modules if possible.
Many New Hooks
Many new code hooks have been added for use by Extensions,
- in [% terms.Bugzilla %] 4.0. Now Extensions can access and modify
- nearly every part of [% terms.Bugzilla %].
+ in Bugzilla 4.0. Now Extensions can access and modify
+ nearly every part of Bugzilla.
New Apache Configuration
-If you run [% terms.Bugzilla %] under Apache (as most people do),
+
If you run Bugzilla under Apache (as most people do),
you most likely require a new Apache configuration
- for this version of [% terms.Bugzilla %]. See the
+ for this version of Bugzilla. See the
Notes On Upgrading From a Previous Version
section for details.
@@ -1857,7 +1857,7 @@
Enhancements for Users
- - Now, everywhere in [% terms.Bugzilla %] where you can enter a date,
+
- Now, everywhere in Bugzilla where you can enter a date,
there is a Calendar widget where you can select the date on a
calendar.
- The big icons on the front page have been replaced with much nicer
@@ -1874,9 +1874,9 @@
- [% terms.Bugs %]: There is now a user preference
for whether the comment box appears above or below the existing
comments.
- - [% terms.Bugs %]: [% terms.Bugzilla %] will now
+
- [% terms.Bugs %]: Bugzilla will now
send an email for every comment that you mark or un-mark as being
- private. (Previous versions of [% terms.Bugzilla %] did not send emails
+ private. (Previous versions of Bugzilla did not send emails
to users about this change.) The state of comments being made private
is also now stored in [% terms.abug %]'s history.
- [% terms.Bugs %]: The box to "Add [% terms.Bug %] URLs"
@@ -1922,14 +1922,14 @@
- When using the Reports interface, you can now choose many more fields
as the X, Y, or Z axis of a report, including custom fields.
- - [% terms.Bugzilla %] now prevents
+
- Bugzilla now prevents
Internet Explorer 8 and later from attempting to render
text/plain attachments as HTML.
- If you receive a Whine mail that is empty, there will now be a brief
message explaining that your search found no results.
- The Field Help Page now
contains a description of every single field that can be on
- [%+ terms.abug %] in [% terms.Bugzilla %].
+ [%+ terms.abug %] in Bugzilla.
Enhancements for Administrators and Developers
@@ -1937,11 +1937,11 @@
- The system for moving [% terms.bugs %] between installations has been
moved into an extension called OldBugMove. This system was used
- by very few [% terms.Bugzilla %] installations--if you aren't certain
+ by very few Bugzilla installations--if you aren't certain
whether or not you are using it, you're not using it. To enable the system,
you have to remove the file extensions/OldBugMove/disabled
- and then run checksetup.pl. In a future version of [% terms.Bugzilla %],
- this extension may be moved outside of the core [% terms.Bugzilla %] code,
+ and then run checksetup.pl. In a future version of Bugzilla,
+ this extension may be moved outside of the core Bugzilla code,
so if you are interested in maintaining it, please let us know.
- Custom Fields: "[% terms.Bug %] ID" custom fields can
now represent relationships between [% terms.bugs %], similarly to how the
@@ -1961,15 +1961,15 @@
defaults for everything so that people do not have to specify any field
values when filing [% terms.abug %] via email.)
- Installation: If you are using a localized version of
- [%+ terms.Bugzilla %] and your terminal does not understand Unicode,
+ Bugzilla and your terminal does not understand Unicode,
checksetup.pl will now attempt to output its messages in your
terminal's character set.
- - Installation: [% terms.Bugzilla %] no longer needs empty
+
- Installation: Bugzilla no longer needs empty
"placeholder" CSS in the skins/custom directory and other
directories. When you update, checksetup.pl will remove these.
This also significantly reduces the number of HTTP requests required to
- load a page for the first time in [% terms.Bugzilla %].
- - Installation: For Windows users, [% terms.Bugzilla %]
+ load a page for the first time in Bugzilla.
+ - Installation: For Windows users, Bugzilla
now supports Strawberry Perl fully.
- Installation: Now, whenever checksetup.pl
throws an error, it will be printed in the color red, to make it
@@ -1979,25 +1979,25 @@
almost anything it does.
- Installation: The process of adding foreign keys
to a table is now much faster. This will particularly improve the speed
- of upgrading from [% terms.Bugzilla %] 3.4 or earlier.
+ of upgrading from Bugzilla 3.4 or earlier.
- If you are using jobqueue.pl and email gets heavily delayed
for some reason, those emails will now have a Date header reflecting the
time they were supposed to be sent, instead of when they actually
were sent.
- ./jobqueue.pl install now works on SuSE Linux.
- - [% terms.Bugzilla %] now runs much better in Apache's suexec mode
+
- Bugzilla now runs much better in Apache's suexec mode
than it used to. As part of this, checksetup.pl sets
- much stricter permissions on all the files in [% terms.Bugzilla %]
- than it used to. In particular, any files that [% terms.Bugzilla %]
+ much stricter permissions on all the files in Bugzilla
+ than it used to. In particular, any files that Bugzilla
does not know about will not be readable by the webserver.
- The sendmailnow parameter has been removed, as it was
not necessary for any modern version of Sendmail or other Mail Transfer
Agent.
- When editing a user via the Users administration panel, you can now
see if they are a Default CC on any component.
- - For new installations of [% terms.Bugzilla %], all users will be
+
- For new installations of Bugzilla, all users will be
able to see and use the Whining system by default.
- - When you are using SSL with [% terms.Bugzilla %], you can now
+
- When you are using SSL with Bugzilla, you can now
turn on the strict_transport_security parameter to
send the
Strict-Transport-Security
@@ -2009,19 +2009,19 @@
and object_validators. The colchange_columns hook has been removed,
as it is no longer necessary (buglist_columns will be used for data
about which columns can be on the [% terms.bug %] list).
- - When [% terms.Bugzilla %] throws certain types of errors, it will
+
- When Bugzilla throws certain types of errors, it will
now include a "traceback" of where exactly the error occurred in the
code, to help administrators and developers debug problems.
- There is now a test, xt/search.t, that assures that all
of the functionality of Bugzilla::Search is working properly.
- If you customize the search functionality of [% terms.Bugzilla %],
+ If you customize the search functionality of Bugzilla,
you may wish to run this test to assure that your changes are correct.
You can see more information about running this test by doing
perldoc xt/search.t at the command line.
- - [% terms.Bugzilla %] now sends the
+
- Bugzilla now sends the
X-Frame-Options: SAMEORIGIN
header
with every page request in order to prevent "clickjacking" attacks. Note
- that this prevents other domains from displaying [% terms.Bugzilla %]
+ that this prevents other domains from displaying Bugzilla
in an HTML frame.
@@ -2047,7 +2047,7 @@
and exclude_fields arguments: B[% %]ug.get,
B[% %]ug.search, and B[% %]ug.attachments. Also,
server-side performance of the WebService is actually increased when
- using these arguments, now, as [% terms.Bugzilla %] will no longer
+ using these arguments, now, as Bugzilla will no longer
get data from the database for fields you haven't asked for.
- You can now mark the initial description of [% terms.abug %] as
private when filing [% terms.abug %] via the B[% %]ug.create
@@ -2062,7 +2062,7 @@
- There is a new, undocumented B[% %]ug.possible_duplicates
function that helps implement the automatic duplicate detection
system. Because this function is not documented, its API may change
- between releases of [% terms.Bugzilla %].
+ between releases of Bugzilla.
- You can no longer search using the votes argument in
B[% %]ug.search.
- B[% %]ug.attachments now returns the attachment's description
@@ -2070,12 +2070,12 @@
consistent with the fact that [% terms.bug %] summaries are called
"summary". The value is still also returned as "description",
for backwards compatibility, but this backwards compatibility will go
- away in [% terms.Bugzilla %] 5.0.
+ away in Bugzilla 5.0.
- In the return values of various B[% %]ug functions, the author
of comments, [% terms.bugs %], and attachments is now called "creator",
instead of sometimes being called "reporter", "author", or "attacher".
The old names are retained for backwards-compatibility, and will stay
- around until [% terms.Bugzilla %] 5.0.
+ around until Bugzilla 5.0.
Outstanding Issues
@@ -2104,10 +2104,10 @@
mod_cgi
-If you run [% terms.Bugzilla %] under mod_cgi (this is the most common
+
If you run Bugzilla under mod_cgi (this is the most common
configuration, involving a <Directory> block in your Apache config
file), you will need to update the configuration of Apache for
- [%+ terms.Bugzilla %]. In particular, this line in the [% terms.Bugzilla %]
+ Bugzilla. In particular, this line in the Bugzilla
<Directory> block:
AllowOverride Limit
@@ -2116,14 +2116,14 @@
AllowOverride Limit FileInfo Indexes
-For full details on how to configure Apache for [% terms.Bugzilla %],
+
For full details on how to configure Apache for Bugzilla,
see the
Configuration
- section of the [% terms.Bugzilla %] Guide.
+ section of the Bugzilla Guide.
mod_perl
-If your [% terms.Bugzilla %] runs under mod_perl, the required Apache
+
If your Bugzilla runs under mod_perl, the required Apache
configuration is now simpler. The line that used to look like:
PerlSwitches -w -T -I/var/www/html/bugzilla
@@ -2137,16 +2137,16 @@
New .htaccess file
-In previous versions of [% terms.Bugzilla %], there was a file
- in [% terms.Bugzilla %]'s root directory called ".htaccess" that was
+
In previous versions of Bugzilla, there was a file
+ in Bugzilla's root directory called ".htaccess" that was
generated by checksetup.pl. This file is now shipped with
- [%+ terms.Bugzilla %] instead of being generated during installation.
+ Bugzilla instead of being generated during installation.
If you update via CVS or bzr, you will get a message that your existing
.htaccess file conflicts with the new one. You must
remove your existing .htaccess file and use the new one
instead. Continuing to use your old .htaccess file will cause certain new
- features of [% terms.Bugzilla %] to not work properly, and may also lead
+ features of Bugzilla to not work properly, and may also lead
to security issues for your system in the future.
Code Changes Which May Affect Customizations and
@@ -2158,9 +2158,9 @@
(For example, extensions/Foo/web/). checksetup.pl
sets permissions on extensions much more strictly now, and files in
other locations (such as your base extensions/Foo/ directory)
- will no longer be available to [% terms.Bugzilla %] users via the web
+ will no longer be available to Bugzilla users via the web
under certain configurations.
-
Previous versions of [% terms.Bugzilla %] used to allow putting a
+ Previous versions of Bugzilla used to allow putting a
single file into the "skins" directory and having that be an entire
skin. That is no longer allowed, and on upgrade, checksetup.pl
will convert any such skins into a directory with a single
@@ -2193,7 +2193,7 @@
that were passed in, while an object is being created. For an example of
how to use VALIDATOR_DEPENDENCIES, see
Bugzilla/Field.pm.
- In previous versions of [% terms.Bugzilla %], you had to call
+ In previous versions of Bugzilla, you had to call
Bugzilla->template_inner("")
after any time
that you called template_inner for a specific language.
It is no longer necessary to do this second template_inner
@@ -2209,17 +2209,17 @@
now be easier to customize.
The Bugzilla::Util::lsearch function is gone. Use
firstidx from List::MoreUtils, instead.
- [% terms.Bugzilla %] now includes YUI 2.8.2.
+ Bugzilla now includes YUI 2.8.2.
long_list.cgi, showattachment.cgi and
xml.cgi are deprecated scripts which are no longer actively
- used since [% terms.Bugzilla %] 2.19. These scripts will be removed in
- [%+ terms.Bugzilla %] 4.2.
+ used since Bugzilla 2.19. These scripts will be removed in
+ Bugzilla 4.2.
Release Notes For Previous Versions
Release Notes for
- [%+ terms.Bugzilla %] 3.x and Earlier
+ Bugzilla 3.x and Earlier
[% INCLUDE global/footer.html.tmpl %]
--
cgit v1.2.3-24-g4f1b