Skip to content

bugzilla
bugzilla
Commit bea91992 authored by mkanat%bugzilla.org's avatar mkanat%bugzilla.org
Browse files
Options

Bug 432331: Release Notes for Bugzilla 3.2

Patch By Max Kanat-Alexander <mkanat@bugzilla.org> r=LpSolit, a=LpSolit
parent d4913056
Hide whitespace changes
Inline Side-by-side
Showing with 630 additions and 16 deletions
template/en/default/pages/release-notes.html.tmpl
View file @ bea91992
......@@ -19,13 +19,493 @@
[% PROCESS global/variables.none.tmpl %]
[% INCLUDE global/header.html.tmpl
title = "$terms.Bugzilla 3.0.4 Release Notes"
title = "$terms.Bugzilla 3.2 Release Notes"
style_urls = ['skins/standard/release-notes.css']
%]
<h2>Table of Contents</h2>
<ul class="bz_toc">
<li><a href="#v32_introduction">Introduction</a></li>
<li><a href="#v32_req">Minimum Requirements</a></li>
<li><a href="#v32_feat">New Features and Improvements</a></li>
<li><a href="#v32_issues">Outstanding Issues</a></li>
<li><a href="#v32_upgrading">How to Upgrade From An Older Version</a></li>
<li><a href="#v32_code_changes">Code Changes Which May Affect
Customizations</a></li>
<li><a href="#v32_previous">Release Notes for Previous Versions</a></li>
</ul>
<h2><a name="v32_introduction"></a>Introduction</h2>
<p>Welcome to [% terms.Bugzilla %] 3.2! This is our first major feature
release since [% terms.Bugzilla %] 3.0, and it brings a lot of great
improvements and polish to the [% terms.Bugzilla %] experience.</p>
<p>If you're upgrading, make sure to read <a href="#v32_upgrading">How to
Upgrade From An Older Version</a>. If you are upgrading from a release
before 3.0, make sure to read the release notes for all the
<a href="#v32_previous">previous versions</a> in between your version
and this one, <strong>particularly the "Notes For Upgraders" section of each
version's release notes</strong>.</p>
<h2><a name="v32_req"></a>Minimum Requirements</h2>
<p>Any requirements that are new since 3.0.5 will look like
<span class="req_new">this</span>.</p>
<ul>
<li><a href="#v32_req_perl">Perl</a></li>
<li><a href="#v32_req_mysql">For MySQL Users</a></li>
<li><a href="#v32_req_pg">For PostgreSQL Users</a></li>
<li><a href="#v32_req_oracle">For Oracle Users</a></li>
<li><a href="#v32_req_modules">Required Perl Modules</a></li>
<li><a href="#v32_req_optional_mod">Optional Perl
Modules</a></li>
</ul>
<h3><a name="v32_req_perl"></a>Perl</h3>
<p>Perl <span class="req_new">v<strong>5.8.1</strong></span></p>
[% INCLUDE db_req db='mysql' dbd_new = 1 %]
[% INCLUDE db_req db='pg' %]
[% INCLUDE db_req db='oracle' %]
<h3><a name="v32_req_modules"></a>Required Perl Modules</h3>
[% INCLUDE req_table reqs = REQUIRED_MODULES
new = []
updated = ['Template-Toolkit', 'Email-MIME',
'Email-MIME-Modifier'] %]
<h3><a name="v32_req_optional_mod"></a>Optional Perl Modules</h3>
<p>The following perl modules, if installed, enable various
features of [% terms.Bugzilla %]:</p>
[% INCLUDE req_table reqs = OPTIONAL_MODULES
new = ['SASL-Authen', 'RadiusPerl']
updated = []
include_feature = 1 %]
<h2><a name="v32_feat"></a>New Features and Improvements</h2>
<ul>
<li><a href="#v32_feat_ui">Major UI Improvements</a></li>
<li><a href="#v32_feat_skin">New Default Skin: Dusk</a></li>
<li><a href="#v32_feat_status">Custom Status Workflow</a></li>
<li><a href="#v32_feat_fields">New Custom Field Types</a></li>
<li><a href="#v32_feat_install">Easier Installation</a></li>
<li><a href="#v32_feat_oracle">Experimental Oracle Support</a></li>
<li><a href="#v32_feat_utf8">Improved UTF-8 Support</a></li>
<li><a href="#v32_feat_grcons">Group Icons</a></li>
<li><a href="#v32_feat_other">Other Enhancements and Changes</a></li>
</ul>
<h3><a name="v32_feat_ui"></a>Major UI Improvements</h3>
<p>[% terms.Bugzilla %] 3.2 has had some UI assistance from the NASA
Human-Computer Interaction department and the new
<a href="http://wiki.mozilla.org/Bugzilla:UE">[% terms.Bugzilla %]
User Interface Team</a>.</p>
<p>In particular, you will notice a massively redesigned [% terms.bug %]
editing form, in addition to our <a href="#v32_feat_skin">new skin</a>.</p>
<h3><a name="v32_feat_skin"></a>New Default Skin: Dusk</h3>
<p>[% terms.Bugzilla %] 3.2 now ships with a skin called "Dusk" that is
a bit more colorful than old default "Classic" skin.</p>
<p>Upgrading installations will still default to the "Classic"
skin--administrators can change the default in the Default Preferences
control panel. Users can also choose to use the old skin in their
Preferences (or using the View :: Page Style menu in Firefox).</p>
<p>The changes that [% terms.Bugzilla %] required for Dusk made
[%+ terms.Bugzilla %] much easier to skin. See the
<a href="http://wiki.mozilla.org/Bugzilla:Addons#Skins">Addons page</a>
for additional skins, or try making your own!</p>
<h3><a name="v32_feat_status"></a>Custom Status Workflow</h3>
<p>You can now customize the list of statuses in [% terms.Bugzilla %],
and transitions between them.</p>
<p>You can also specify that a comment must be made on certain transitions.</p>
<h3><a name="v32_feat_fields"></a>New Custom Field Types</h3>
<p>[% terms.Bugzilla %] 3.2 has support for three new types of
custom fields:</p>
<ul>
<li>Large Text: Adds a multi-line textbox to your [% terms.bugs %].</li>
<li>Multiple Selection Box: Adds a box that allows you to choose
multiple items from a list.</li>
<li>Date/Time: Displays a date and time, along with a JavaScript
calendar popup to make picking a date easier.</li>
</ul>
<h3><a name="v32_feat_install"></a>Easier Installation</h3>
<p>[% terms.Bugzilla %] now comes with a script called
<kbd>install-module.pl</kbd> that can automatically download
and install all of the required Perl modules for [% terms.Bugzilla %].
It stores them in a directory inside your [% terms.Bugzilla %]
installation, so you can use it even if you don't have administrator-level
access to your machine, and without modifying your main Perl install.</p>
<p><kbd>checksetup.pl</kbd> will print out instructions for using
<kbd>install-module.pl</kbd>, or you can read its
<a href="[% docs_urlbase FILTER html %]api/install-module.html">documentation</a>.</p>
<h3><a name="v32_feat_oracle"></a>Experimental Oracle Support</h3>
<p>[% terms.Bugzilla %] 3.2 contains experimental support for using
Oracle as its database. Some features of [% terms.Bugzilla %] are known
to be broken on Oracle, but hopefully will be working by our next major
release.</p>
<p>The [% terms.Bugzilla %] Project, as an open-source project, of course
does not recommend the use of proprietary database solutions. However,
if your organization requires that you use Oracle, this will allow
you to use [% terms.Bugzilla %]!</p>
<p>The [% terms.Bugzilla %] Project thanks Oracle Corp. for their extensive
development contributions to [% terms.Bugzilla %] which allowed this to
happen!</p>
<h3><a name="v32_feat_utf8"></a>Improved UTF-8 Support</h3>
<p>[% terms.Bugzilla %] 3.2 now has advanced UTF-8 support in its code,
including correct handling for truncating and wrapping multi-byte
languages. Major issues with multi-byte or unusual languages
are now resolved, and [% terms.Bugzilla %] should now be usable
by users in every country with little (or at least much less)
customization.</p>
<h3><a name="v32_feat_grcons"></a>Group Icons</a></h3>
<p>Administrators can now specify that users who are in certain groups
should have an icon appear next to their name whenever they comment.
This is particularly useful for distinguishing developers from
[%+ terms.bug %] reporters.</p>
<h3><a name="v32_feat_other"></a>Other Enhancements and Changes</h3>
<p>These are either minor enhancements, or enhancements that have
very short descriptions. Some of these are very useful, though!</p>
<h4>Enhancements For Users</h4>
<ul>
<li><strong>[% terms.Bugs %]</strong>: You can now reassign
[%+ terms.abug %] at the same time as you are changing its status.</li>
<li><strong>[% terms.Bugs %]</strong>: When entering [% terms.abug %],
you will now see the description of a component when you select it.</li>
<li><strong>[% terms.Bugs %]</strong>: When adding or removing keywords
from [% terms.abug %], there is now a very nice JavaScript popup that
will help you, which lists available keywords.</li>
<li><strong>[% terms.Bugs %]</strong>: The [% terms.bug %] view now
contains some <a href="http://microformats.org/about/">Microformats</a>,
most notably for users' names and email addresses.</li>
<li><strong>[% terms.Bugs %]</strong>: You can now remove a QA Contact
from [% terms.abug %] simply by clearing the QA Contact field.</li>
<li><strong>[% terms.Bugs %]</strong>: There is now a user preference
that will allow you to exclude the quoted text when replying
to comments.</li>
<li><strong>[% terms.Bugs %]</strong>: You can now expand or collapse
individual comments in the [% terms.bug %] view.</li>
<li><strong>Attachments</strong>: There is now "mid-air collision"
protection when editing attachments.</li>
<li><strong>Attachments</strong>: Patches in the Diff Viewer now show
line numbers (<a href="https://bugzilla.mozilla.org/attachment.cgi?id=327546">Example</a>).</li>
<li><strong>Attachments</strong>: After creating or updating an attachment,
you will be immediately shown the [% terms.bug %] that the attachment
is on.</li>
<li><strong>Search</strong>: You can now reverse the sort of
[%+ terms.abug %] list by clicking on a column header again.</li>
<li><strong>Search</strong>: Atom feeds of [% terms.bug %] lists now
contain more fields.</li>
<li><strong>Search</strong>: QuickSearch now supports searching flags
and groups. It also now includes the OS field in the list of fields
it searches by default.</li>
<li><strong>Search</strong>: "Help" text can now appear on query.cgi
for Internet Explorer and other non-Firefox browsers. (It always
could appear for Firefox.)</li>
<li>[% terms.Bugzilla %] now ships with an icon that will show
up next to the URL in most browsers. If you want to replace it,
it's in <kbd>images/favicon.ico</kbd>.</li>
<li>You can now set the Deadline when using "Change Several
[%+ terms.Bugs %] At Once"</li>
<li><strong>Saved Searches</strong> now save their column list, so if
you customize the list of columns and save your search, it will
always contain those columns.</li>
<li><strong>Saved Searches</strong>: When you share a search, you can
now see how many users have subscribed to it, on
<kbd>userprefs.cgi</kbd>.</li>
<li><strong>Saved Searches</strong>: You can now see what group a
shared search was shared to, on the list of available shared searches
in <kbd>userprefs.cgi</kbd>.</li>
<li><strong>Flags</strong>: If your installation uses drop-down user
lists, the flag requestee box will now contain only users who are
actually allowed to take requests.</li>
<li><strong>Flags</strong>: If somebody makes a request to you, and you
change the requestee to somebody else, the requester is no longer set
to you. In other words, you can "redirect" requests and maintain the
original requester.</li>
<li>When using <kbd>email_in.pl</kbd>, you can now add users to the CC
list by just using <kbd>@cc</kbd> as the field name.</li>
<li>Many pages (particularly administrative pages) now contain links to
the relevant section of the [% terms.Bugzilla %] Guide, so you can read
the documentation for that page.</li>
<li>Dependency Graphs should render more quickly, as they now (by default)
only include the same [% terms.bugs %] that you'd see in the dependency
tree.</li>
</ul>
<h4>Enhancements For Administrators</h4>
<ul>
<li><strong>Admin UI</strong>: Instead of having the Administration
Control Panel links in the footer, there is now just one link called
"Administration" that takes you to a page that links to all the
administrative controls for [% terms.Bugzilla %].</li>
<li><strong>Admin UI</strong>: Administrative pages no longer display
confirmation pages, instead they redirect you to some useful page
and display a message about what changed.</li>
<li><strong>Admin UI</strong>: The interface for editing group
inheritance in <kbd>editgroups.cgi</kbd> is much clearer now.</li>
<li><strong>Admin UI</strong>: When editing a user, you can now see
all the components where that user is the Default Assignee or Default
QA Contact.</li>
<li><strong>Email</strong>: For installations that use SMTP to send
mail (as opposed to Sendmail), [%+ terms.Bugzilla %] now supports
SMTP Authentication, so that it can log in to your mail server
before sending messages.</li>
<li><strong>Email</strong>: Using the "Test" mail delivery method now
creates a valid mbox file to make testing easier.</li>
<li><strong>Authentication</strong>: [% terms.Bugzilla %] now correctly
handles LDAP records which contain multiple email addresses. (The first
email address in the list that is a valid [% terms.Bugzilla %] account
will be used, or if this is a new user, the first email address in
the list will be used.)</li>
<li><strong>Authentication</strong>: [% terms.Bugzilla %] can now take
a list of LDAP servers to try in order until it gets a successful
connection.</li>
<li><strong>Authentication</strong>: [% terms.Bugzilla %] now supports
RADIUS authentication.</li>
<li>[% terms.Bugzilla %] now uses transactions in the database instead of
table locks. This should generally improve [% terms.Bugzilla %]'s
performance with many concurrent users. It also means if there is
an unexpected error in the middle of a page, all database changes made
during that page will be rolled back.</li>
<li>New WebService functions:
<a href="[% docs_urlbase FILTER html %]api/Bugzilla/WebService/Bug.html">B<!-- -->ug.add_comment</a>
and <a href="[% docs_urlbase FILTER html %]api/Bugzilla/WebService/Bugzilla.html">Bugzilla.extensions</a>.</li>
<li>You can now delete custom fields, but only if they have never been
set on any [% terms.bug %].</li>
<li>There is now a <kbd>--reset-password</kbd> argument to
<kbd>checksetup.pl</kbd> that allows you to reset a user's password
from the command line.</li>
<li>There is now a script called <kbd>sanitycheck.pl</kbd> that you can
run from the command line. It works just like <kbd>sanitycheck.cgi</kbd>.
By default, it only outputs anything if there's an error, so it's
ideal for administrators who want to run it nightly in a cron job.</li>
<li>The <kbd>strict_isolation</kbd> parameter now prevents you from setting
users who cannot see [% terms.abug %] as a CC, Assignee, or QA
Contact. Previously it only prevented you from adding users who
could not <em>edit</em> the [% terms.bug %].</li>
<li>Extensions can now add their own headers to the HTML &lt;head&gt;
for things like custom CSS and so on.</li>
<li><kbd>sanitycheck.cgi</kbd> has been templatized, meaning that the
entire [% terms.Bugzilla %] UI is now contained in templates.</li>
<li>When setting the <kbd>sslbase</kbd> parameter, you can now specify
a port number in the URL.</li>
<li>When importing [% terms.bugs %] using <kbd>importxml.pl</kbd>,
attachments will have their actual creator set as their creator,
instead of the person who exported the [% terms.bug %] from the other
system.</li>
<li>The voting system is off by default in new installs. This is to
prepare for the fact that it will be moved into an extension at
some point in the future.</li>
</ul>
<h3>Enhancements for Localizers (or Localized Installations)</h3>
<ul>
<li>The documentation can now be localized--in other words, you can have
documentation installed for multiple languages at once and
[%+ terms.Bugzilla %] will link to the correct language in its internal
documentation links.</li>
<li>[% terms.Bugzilla %] no longer uses the <kbd>languages</kbd> parameter.
Instead it reads the <kbd>template/</kbd> directory to see which
languages are available.</li>
<li>Some of the messages printed by <kbd>checksetup.pl</kbd> can now
be localized. See <kbd>template/en/default/setup/strings.txt.pl</kbd>.
</ul>
<h2><a name="v32_issues"></a>Outstanding Issues</h2>
<ul>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=423439">
[%- terms.Bug %] 423439</a>: Tabs in comments will be converted
to four spaces, due to a b<!-- -->ug in Perl as of Perl 5.8.8.</li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=69621">
[%- terms.Bug %] 69621</a>: If you rename or remove a keyword that is
in use on [% terms.bugs %], you will need to rebuild the "keyword cache"
by running <a href="sanitycheck.cgi">sanitycheck.cgi</a> and choosing
the option to rebuild the cache when it asks. Otherwise keywords may
not show up properly in search results.</li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=89822">
[%- terms.Bug %] 89822</a>: When changing multiple [% terms.bugs %] at
the same time, there is no "mid-air collision" protection.</li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=276230">
[%- terms.Bug %] 276230</a>: The support for restricting access to
particular Categories of New Charts is not complete. You should treat
the 'chartgroup' Param as the only access mechanism available.<br>
However, charts migrated from Old Charts will be restricted to
the groups that are marked MANDATORY for the corresponding Product.
There is currently no way to change this restriction, and the
groupings will not be updated if the group configuration
for the Product changes.</li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=370370">
[%- terms.Bug %] 370370</a>: mod_perl support is currently not
working on Windows machines.</li>
</ul>
<h2><a name="v32_upgrading"></a>How to Upgrade From An Older Version</h2>
<h3><a name="v32_upgrading_notes"></a>Notes For Upgraders</h3>
<ul>
<li>If you upgrade by CVS, the <kbd>extensions</kbd> and
<kbd>skins/contrib</kbd> directories are now in CVS instead of
being created by <kbd>checksetup.pl</kbd> If you do a <kbd>cvs update</kbd>
from 3.0, you will be told that your directories are "in the way" and
you should delete (or move) them and then do <kbd>cvs update</kbd>
again. Also, the <kbd>docs</kbd> directory has been restructured
and after you <kbd>cvs update</kbd> you can delete the <kbd>docs/html</kbd>,
<kbd>docs/pdf</kbd>, <kbd>docs/txt</kbd>, and <kbd>docs/xml</li>
directories.</li>
<li>If you are using MySQL, you should know that [% terms.Bugzilla %]
now uses InnoDB for all tables. <kbd>checksetup.pl</kbd> will convert
your tables automatically, but if you have InnoDB disabled,
the upgrade will not be able to complete (and <kbd>checksetup.pl</kbd>
will tell you so).</li>
<li><strong>You should also read the
<a href="#v30_upgrading_notes">[% terms.Bugzila %] 3.0 Notes For Upgraders
section</a> of the
<a href="#v32_previous">previous release notes</a> if you are upgrading
from a version before 3.0.</strong></li>
</ul>
<h3>Steps For Upgrading</h3>
<ol>
<li>Read these entire Release Notes, particularly the &quot;Notes for
Upgraders&quot; section above.</li>
<li>View the <a href="sanitycheck.cgi">Sanity Check</a> page on your
installation before upgrading. Attempt to fix all warnings that
the page produces before you go any further, or you may experience
problems during your upgrade.</li>
<li>Make a backup of the [% terms.Bugzilla %] database before you upgrade,
perhaps by using <kbd>mysqldump</kbd>. <strong>THIS IS VERY
IMPORTANT</strong>. If anything goes wrong during the upgrade, your
installation can be corrupted beyond recovery. Having a backup keeps you
safe.
<p>Example: <kbd>mysqldump -u root -p bu[%# trick filter %]gs &gt;
bu[%# trick filter %]gs-db.sql</kbd></p></li>
<li>Replace the files in your installation with the new version of
[% terms.Bugzilla %], or you can try to use CVS to upgrade.
<p>You can also use a brand-new [% terms.Bugzilla %] directory, as long
as you copy over the old <kbd>data/</kbd> directory and the
<kbd>localconfig</kbd> file to the new installation.</p></li>
<li>Now follow the standard
<a href="[% docs_urlbase FILTER html %]installing-bugzilla.html">
[%- terms.Bugzilla %] installation process</a>.</li>
<li>Run <kbd>checksetup.pl</kbd> after you install the new version.</li>
<li>View the <a href="sanitycheck.cgi">Sanity Check</a> page again after
you run <kbd>checksetup.pl</kbd>.</li>
<li>It is recommended that, if possible, you fix any problems you find
immediately. Failure to do this may mean that [% terms.Bugzilla %] will
not work correctly. Be aware that if the sanity check page contains more
errors after an upgrade, it doesn't necessarily mean there are more
errors in your database than there were before, as additional tests
are added to the sanity check over time, and it is possible that those
errors weren't being checked for in the old version.</li>
</ol>
<h2><a name="v32_code_changes"></a>Code Changes Which May Affect
Customizations</h2>
<ul>
<li><a href="#v32_code_hooks">More Hooks!</a></li>
<li><a href="#v32_code_search">Search.pm Rearchitecture</a></li>
<li><a href="#v32_code_lib">lib Directory</a></li>
<li><a href="#v32_code_other">Other Changes</a></li>
</ul>
<h3><a name="v32_code_hooks"></a>More Hooks!</h3>
<p>There are more code hooks in 3.2 than there were in 3.0. See the
documentation of <a href="[% docs_urlbase FILTER html %]api/Bugzilla/Hook.html">Bugzilla::Hook</a>
for more details.</p>
<h3><a name="v32_code_search"></a>Search.pm Rearchitecture</h3>
<p><kbd>Bugzilla/Search.pm</kbd> has been heavily modified, to be much
easier to read and use. It contains mostly the same code as it did in
3.0, but it has been moved around and reorganized significantly.</p>
<h3><a name="v32_code_lib"></a>lib Directory</h3>
<p>As part of implementing <a href="#v32_feat_install">install-module.pl</a>,
[%+ terms.Bugzilla %] was given a local <kbd>lib</kbd> directory which
it searches for modules, in addition to the standard system path.</p>
<p>This means that all [% terms.Bugzilla %] scripts now start with
<code>use lib qw(. lib);</code> as one of the first lines.</p>
<h3><a name="v32_code_other"></a>Other Changes</h3>
<ul>
<li>You should now be using <code>get_status('NEW')</code> instead of
<code>status_descs.NEW</code> in templates.</li>
<li>The <code>[&#37;# version = 1.0 &#37;] comment at the top of every
template file has been removed.</li>
</ul>
<h2><a name="v32_previous"></a>Release Notes For Previous Versions</h2>
<h1>[% terms.Bugzilla %] 3.0.x Release Notes</h1>
<h2>Table of Contents</h2>
<ul class="bz_toc">
<li><a href="#v30_introduction">Introduction</a></li>
<li><a href="#v30_point">Updates In This 3.0.x Release</a></li>
<li><a href="#v30_req">Minimum Requirements</a></li>
......@@ -256,27 +736,156 @@
<li>Perl v<strong>5.8.1</strong> (Windows platforms)</li>
</ul>
[% PROCESS db_req db='mysql' %]
<h3><a name="v30_req_mysql"></a>For MySQL Users</h3>
[% PROCESS db_req db='pg' %]
<ul>
<li>MySQL v4.1.2</li>
<li><strong>perl module:</strong> DBD::mysql v2.9003</li>
</ul>
<h3><a name="v30_req_pg"></a>For PostgreSQL Users</h3>
<ul>
<li>PostgreSQL v8.00.0000</li>
<li><strong>perl module:</strong> DBD::Pg v1.45</li>
</ul>
<h3><a name="v30_req_modules"></a>Required Perl Modules</h3>
[% INCLUDE req_table reqs = REQUIRED_MODULES
new = ['Email-MIME-Modifier', 'Email-Send']
updated = ['DBI'] %]
<table class="req_table" border="0" cellspacing="0" cellpadding="0">
<tr>
<th>Module</th> <th>Version</th>
</tr>
<tr><td>CGI</td> <td>2.93</td>
</tr>
<tr>
<td>Date::Format</td> <td>2.21</td>
</tr>
<tr>
<td>DBI</td>
<td class="req_new">1.41</td>
</tr>
<tr>
<td>File::Spec</td> <td>0.84</td>
</tr>
<tr>
<td>Template</td> <td>2.12</td>
</tr>
<tr>
<td class="req_new">Email::Send</td>
<td class="req_new">2.00</td>
</tr>
<tr>
<td>Email::MIME</td>
<td>1.861</td>
</tr>
<tr>
<td class="req_new">Email::MIME::Modifier</td>
<td class="req_new">1.442</td>
</tr>
</table>
<h3><a name="v30_req_optional_mod"></a>Optional Perl Modules</h3>
<p>The following perl modules, if installed, enable various
features of [% terms.Bugzilla %]:</p>
[% INCLUDE req_table reqs = OPTIONAL_MODULES
new = ['libwww-perl', 'SOAP-Lite', 'mod_perl',
'Apache-DBI', 'Email-MIME-Attachment-Stripper',
'Email-Reply']
updated = ['CGI']
include_feature = 1 %]
<table class="req_table" border="0" cellspacing="0" cellpadding="0">
<tr>
<th>Module</th> <th>Version</th>
<th>Enables Feature</th>
</tr>
<tr>
<td class="req_new">LWP::UserAgent</td>
<td class="req_new">(Any)</td>
<td>Automatic Update Notifications</td>
</tr>
<tr>
<td>Template::Plugin::GD::Image</td>
<td>(Any)</td>
<td>Graphical Reports</td>
</tr>
<tr>
<td>GD::Graph</td>
<td>(Any)</td>
<td>Graphical Reports</td>
</tr>
<tr>
<td>GD::Text</td>
<td>(Any)</td>
<td>Graphical Reports</td>
</tr>
<tr>
<td>GD</td>
<td>1.20</td>
<td>Graphical Reports, New Charts, Old Charts</td>
</tr>
<tr>
<td class="req_new">Email::MIME::Attachment::Stripper</td>
<td class="req_new">(Any)</td>
<td>Inbound Email</td>
</tr>
<tr>
<td class="req_new">Email::Reply</td>
<td class="req_new">(Any)</td>
<td>Inbound Email</td>
</tr>
<tr>
<td>Net::LDAP</td>
<td>(Any)</td>
<td>LDAP Authentication</td>
</tr>
<tr>
<td>HTML::Parser</td>
<td>3.40</td>
<td>More HTML in Product/Group Descriptions</td>
</tr>
<tr>
<td>HTML::Scrubber</td>
<td>(Any)</td>
<td>More HTML in Product/Group Descriptions</td>
</tr>
<tr>
<td>XML::Twig</td>
<td>(Any)</td>
<td>Move [% terms.Bugs %] Between Installations</td>
</tr>
<tr>
<td>MIME::Parser</td>
<td>5.406</td>
<td>Move [% terms.Bugs %] Between Installations</td>
</tr>
<tr>
<td>Chart::Base</td>
<td>1.0</td>
<td>New Charts, Old Charts</td>
</tr>
<tr>
<td>Image::Magick</td>
<td>(Any)</td>
<td>Optionally Convert BMP Attachments to PNGs</td>
</tr>
<tr>
<td>PatchReader</td>
<td>0.9.4</td>
<td>Patch Viewer</td>
</tr>
<tr>
<td class="req_new">SOAP::Lite</td>
<td class="req_new">(Any)</td>
<td>XML-RPC Interface</td>
</tr>
<tr>
<td class="req_new">mod_perl2</td>
<td class="req_new">1.999022</td>
<td>mod_perl</td>
</tr>
<tr>
<td> CGI</td>
<td>3.11</td>
<td>mod_perl</td>
</tr>
</table>
<h2><a name="v30_feat"></a>New Features and Improvements</h2>
......@@ -687,7 +1296,7 @@
<h2><a name="v30_upgrading"></a>How to Upgrade From An Older Version</h2>
<h3>Notes For Upgraders</h3>
<h3><a name="v30_upgrading_notes"></a>Notes For Upgraders</h3>
<ul>
<li>If you upgrade by CVS, there are several .cvsignore files
......@@ -928,13 +1537,18 @@ sub y { $var++ }</pre>
[% BLOCK db_req %]
[% SET m = DB_MODULE.$db %]
<h3><a name="v30_req_[% db FILTER html %]"></a>For [% m.name FILTER html %]
<h3><a name="v32_req_[% db FILTER html %]"></a>For [% m.name FILTER html %]
Users</h3>
<ul>
<li>[% m.name FILTER html %] v[% m.db_version FILTER html %]</li>
<li>[% m.name FILTER html %]
[%+ '<span class="req_new">' IF db_new %]v[% m.db_version FILTER html %]
[% '</span>' IF db_new %]
</li>
<li><strong>perl module:</strong>
[%+ m.dbd.module FILTER html %] v[% m.dbd.version FILTER html %]</li>
[%+ m.dbd.module FILTER html %]
[% '<span class="req_new">' IF dbd_new %]v[% m.dbd.version FILTER html %]
[% '</span>' IF dbd_new %]</li>
</ul>
[% END %]
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment