release-notes.html.tmpl

buzilla软件

    #line 605 "template\en\default\pages\release-notes.html.tmpl"
    $output .=  $stash->get(['terms', 0, 'bug', 0]);
    $output .=  " list,\n    it will be sorted alphabetically, so you can sanely sort a list on\n    that field.</li>\n  <li>In most places, the Version field is now sorted using a version-sort\n    (so 1.10 is greater than 1.2) instead of an alphabetical sort.</li>\n  <li>Options for flags will only appear if you can set them. So, for\n    example, if you can't grant <kbd>+</kbd> on a flag, that option\n    won't appear for you.</li>\n  <li>You can limit the product-related output of <kbd>config.cgi</kbd>\n    by specifying a <kbd>product=</kbd> URL argument, containing the name\n    of a product. You can specify the argument more than once for multiple\n    products.</li>\n  <li>You can now search the boolean charts on whether or not a comment\n    is private.</li>\n</ul>\n\n<h4>Enhancements For Administrators</h4>\n\n<ul>\n  <li>Administrators can now delete attachments, making them disappear\n    entirely from ";
    #line 625 "template\en\default\pages\release-notes.html.tmpl"
    $output .=  $stash->get(['terms', 0, 'Bugzilla', 0]);
    $output .=  ".</li>\n  <li><kbd>sanitycheck.cgi</kbd> can now only be accessed by users\n    in the <kbd>editcomponents</kbd> group.</li>\n  <li>The &quot;Field Values&quot; control panel can now only be accessed\n    by users in the <kbd>admin</kbd> group. (Previously it was accessible\n    to anybody in the <kbd>editcomponents</kbd> group.)</li>\n  <li>There is a new parameter <kbd>announcehtml</kbd>, that will allow\n    you to enter some HTML that will be displayed at the top of every\n    page, as an announcement.</li>\n  <li>The <kbd>loginnetmask</kbd> parameter now defaults to 0 for new\n    installations, meaning that as long as somebody has the right\n    login cookie, they can log in from any IP address. This makes\n    life a lot easier for dial-up users or other users whose IP\n    changes a lot. This could be done because the login cookie is now\n    very random, and thus secure.</li>\n  <li>Classifications now have sortkeys, so they can be sorted in an\n    order that isn't alphabetical.</li>\n  <li>Authentication now supports LDAP over SSL (LDAPS) or TLS (using\n    the STARTLS command) in addition to plain LDAP.</li>\n  <li>LDAP users can have their LDAP username be their email address,\n    instead of having the LDAP <kbd>mail</kbd> attribute be their\n    email address. You may wish to set the <kbd>emailsuffix</kbd>\n    parameter if you do this.</li>\n  <li>Administrators can now see what has changed in a user account,\n    when using the &quot;Users&quot; control panel.</li>\n  <li><code>REMIND</code> and <code>LATER</code> are no longer part\n    of the default list of resolutions. Upgrading installations will\n    not be affected--they will still have these resolutions.</li>\n  <li><kbd>editbugs</kbd> is now the default for the <kbd>timetrackinggroup</kbd>\n    parameter, meaning that time-tracking will be on by default in a new\n    installation.</li>\n</ul>\n\n<h2><a name=\"v30_issues\"></a>Outstanding Issues</h2>\n\n<ul>\n  <li><a href=\"https://bugzilla.mozilla.org/show_bug.cgi?id=69621\">";
    #line 662 "template\en\default\pages\release-notes.html.tmpl"
    $output .=  $stash->get(['terms', 0, 'Bug', 0]);
    $output .=  " 69621</a>: If you rename or remove a keyword that is\n    in use on ";
    #line 663 "template\en\default\pages\release-notes.html.tmpl"
    $output .=  $stash->get(['terms', 0, 'bugs', 0]);
    $output .=  ", you will need to rebuild the \"keyword cache\"\n    by running <a href=\"sanitycheck.cgi\">sanitycheck.cgi</a> and choosing \n    the option to rebuild the cache when it asks. Otherwise keywords may \n    not show up properly in search results.</li>\n  <li><a href=\"https://bugzilla.mozilla.org/show_bug.cgi?id=99215\">";
    #line 668 "template\en\default\pages\release-notes.html.tmpl"
    $output .=  $stash->get(['terms', 0, 'Bug', 0]);
    $output .=  " 99215</a>: Flags are not protected by \"mid-air \n    collision\" detection. Nor are any attachment changes.</li>\n  <li><a href=\"https://bugzilla.mozilla.org/show_bug.cgi?id=89822\">";
    #line 671 "template\en\default\pages\release-notes.html.tmpl"
    $output .=  $stash->get(['terms', 0, 'Bug', 0]);
    $output .=  " 89822</a>: When changing multiple ";
    #line 671 "template\en\default\pages\release-notes.html.tmpl"
    $output .=  $stash->get(['terms', 0, 'bugs', 0]);
    $output .=  " at \n    the same time, there is no \"mid-air collision\" protection.</li>\n  <li><a href=\"https://bugzilla.mozilla.org/show_bug.cgi?id=276230\">";
    #line 674 "template\en\default\pages\release-notes.html.tmpl"
    $output .=  $stash->get(['terms', 0, 'Bug', 0]);
    $output .=  " 276230</a>: The support for restricting access to \n    particular Categories of New Charts is not complete. You should treat \n    the 'chartgroup' Param as the only access mechanism available.<br>\n    However, charts migrated from Old Charts will be restricted to \n    the groups that are marked MANDATORY for the corresponding Product.\n    There is currently no way to change this restriction, and the \n    groupings will not be updated if the group configuration\n    for the Product changes.</li>\n  <li><a href=\"https://bugzilla.mozilla.org/show_bug.cgi?id=370370\">";
    #line 683 "template\en\default\pages\release-notes.html.tmpl"
    $output .=  $stash->get(['terms', 0, 'Bug', 0]);
    $output .=  " 370370</a>: mod_perl support is currently not\n    working on Windows machines.</li>\n  <li><a href=\"https://bugzilla.mozilla.org/show_bug.cgi?id=361149\">";
    #line 686 "template\en\default\pages\release-notes.html.tmpl"
    $output .=  $stash->get(['terms', 0, 'Bug', 0]);
    $output .=  " 361149</a>: If you are using Perl 5.8.0, you may\n    get a lot of warnings in your Apache error_log about \"deprecated\n    pseudo-hashes.\" These are harmless--they are a b";
    $output .=  "ug in \n    Perl 5.8.0. Perl 5.8.1 and later do not have this problem.</li>\n  <li>";
    #line 690 "template\en\default\pages\release-notes.html.tmpl"
    $output .=  $stash->get(['terms', 0, 'Bugzilla', 0]);
    $output .=  " 3.0rc1 allowed custom field column names in \n    the database to be mixed-case. ";
    #line 691 "template\en\default\pages\release-notes.html.tmpl"
    $output .=  $stash->get(['terms', 0, 'Bugzilla', 0]);
    $output .=  " 3.0 only allows\n    lowercase column names. It will fix any column names that you have\n    made mixed-case, but if you have custom fields that previously were\n    mixed-case in any Saved Search, you will have to re-create that Saved\n    Search yourself.</li>\n</ul>\n\n<h2><a name=\"v30_security\"></a>Security Updates in This Release</h2>\n\n<h3>3.0.6</h3>\n\n<p>";
    #line 702 "template\en\default\pages\release-notes.html.tmpl"
    $output .=  $stash->get(['terms', 0, 'Bugzilla', 0]);
    $output .=  " contains a minor security fix. For details, see the\n  <a href=\"http://www.bugzilla.org/security/2.20.6/\">Security Advisory</a>.</p>\n\n<h3>3.0.5</h3>\n\n<p>";
    #line 707 "template\en\default\pages\release-notes.html.tmpl"
    $output .=  $stash->get(['terms', 0, 'Bugzilla', 0]);
    $output .=  " contains one security fix for \n  <a href=\"";
    #line 708 "template\en\default\pages\release-notes.html.tmpl"
    
    # FILTER
    $output .=  do {
        my $output = '';
        my $_tt_filter = $context->filter('html')
                  || $context->throw($context->error);
    
    $output .=  $stash->get(['Param', [ 'docs_urlbase' ]]);
        
        &$_tt_filter($output);
    };
    
    $output .=  "api/importxml.html\">importxml.pl</a>.\n  For details, see the \n  <a href=\"http://www.bugzilla.org/security/2.22.4/\">Security Advisory</a>.</p>\n\n<h3>3.0.4</h3>\n\n<p>";
    #line 714 "template\en\default\pages\release-notes.html.tmpl"
    $output .=  $stash->get(['terms', 0, 'Bugzilla', 0]);
    $output .=  " 3.0.4 contains three security fixes.\n  For details, see the\n  <a href=\"http://www.bugzilla.org/security/2.20.5/\">Security Advisory</a>.</p>\n</p>\n\n<h3>3.0.3</h3>\n\n<p>No security fixes in this release.</p>\n\n<h3>3.0.2</h3>\n\n<p>";
    #line 725 "template\en\default\pages\release-notes.html.tmpl"
    $output .=  $stash->get(['terms', 0, 'Bugzilla', 0]);
    $output .=  " 3.0.1 had an important security fix that is\n  critical for public installations with \"requirelogin\" turned on.\n  For details, see the\n  <a href=\"http://www.bugzilla.org/security/3.0.1/\">Security Advisory</a></p>\n\n<h3>3.0.1</h3>\n\n<p>";
    #line 732 "template\en\default\pages\release-notes.html.tmpl"
    $output .=  $stash->get(['terms', 0, 'Bugzilla', 0]);
    $output .=  " 3.0 had three security issues that have been\n  fixed in this release: one minor information leak, one hole only\n  exploitable by an admin or using <code>email_in.pl</code>, and one in an\n  uncommonly-used template. For details, see the \n  <a href=\"http://www.bugzilla.org/security/2.20.4/\">Security Advisory</a>.</p>\n\n<h2><a name=\"v30_upgrading\"></a>How to Upgrade From An Older Version</h2>\n\n<h3>Notes For Upgraders</h3>\n\n<ul>\n  <li>If you upgrade by CVS, there are several .cvsignore files\n    that are now in CVS instead of being locally created by \n    <kbd>checksetup.pl</kbd>. This means that you will have to\n    delete those files when CVS tells you there's a conflict, and\n    then run <kbd>cvs update</kbd> again.</li>\n  <li>In this version of ";
    #line 748 "template\en\default\pages\release-notes.html.tmpl"
    $output .=  $stash->get(['terms', 0, 'Bugzilla', 0]);
    $output .=  ", the Summary field\n    is now limited to 255 characters. When you upgrade, any Summary\n    longer than that will be truncated, and the old summary will be\n    preserved in a comment.</li>\n  <li>If you have the <kbd>utf8</kbd> parameter turned on, at some\n    point you will have to convert your database. <kbd>checksetup.pl</kbd>\n    will tell you when this is, and it will give you certain instructions\n    at that time, that you have to follow before you can complete\n    the upgrade. Don't do the conversion yourself manually--follow\n    the instructions of checksetup.pl.</li>\n  <li>If you ever ran 2.23.3, 2.23.4, or 3.0rc1, you will have to run\n    <kbd>./collectstats.pl --regenerate</kbd> at the command line, because\n    the data for your Old Charts is corrupted. This can take several days,\n    so you may only want to run it if you use Old Charts.</li>\n  <li>You should also read the Outstanding Issues sections of\n    <a href=\"#v30_previous\">older release notes</a> if you are upgrading\n    from a version lower than 2.22.</li>\n</ul>\n\n<h3>Steps For Upgrading</h3>\n\n<p>Once you have read the notes above, see the\n  <a href=\"";
    #line 770 "template\en\default\pages\release-notes.html.tmpl"
    
    # FILTER
    $output .=  do {
        my $output = '';
        my $_tt_filter = $context->filter('html')
                  || $context->throw($context->error);
    
    $output .=  $stash->get(['Param', [ 'docs_urlbase' ]]);
        
        &$_tt_filter($output);
    };
    
    $output .=  "upgrade.html\">Upgrading \n  documentation</a> for instructions on how to upgrade.</p>\n\n<h2><a name=\"v30_code_changes\"></a>Code Changes Which May Affect \n  Customizations</h2>\n\n<ul>\n  <li><a href=\"#v30_code_loc\"><strong>Packagers:</strong> Location\n    Variables Have Moved</a></li>\n  <li><a href=\"#v30_code_hooks\">Hooks!</a></li>\n  <li><a href=\"#v30_code_api\">API Documentation</a></li>\n  <li><a href=\"#v30_code_globals\">Elimination of globals.pl</a></li>\n  <li><a href=\"#v30_code_scope\">Cleaned Up Variable Scoping Issues</a></li>\n  <li><a href=\"#v30_code_sql\">No More SendSQL</a></li>\n  <li><a href=\"#v30_code_auth\">Auth Re-write</a></li>\n  <li><a href=\"#v30_code_obj\">Bugzilla::Object</a></li>\n  <li><a href=\"#v30_code_req\">Bugzilla-&gt;request_cache</a></li>\n  <li><a href=\"#v30_code_other\">Other Changes</a></li>\n</ul>\n\n<h3><a name=\"v30_code_loc\"></a><strong>Packagers:</strong> Location\n    Variables Have Moved</h3>\n\n<p>In previous versions of ";
    #line 793 "template\en\default\pages\release-notes.html.tmpl"
    $output .=  $stash->get(['terms', 0, 'Bugzilla', 0]);
    $output .=  ", <kbd>Bugzilla::Config</kbd>\n  held all the paths for different things, such as the path to localconfig\n  and the path to the <kbd>data/</kbd> directory.</p>\n\n<p>Now, all of this data is stored in a subroutine,\n  <kbd>Bugzilla::Constants::bz_locations</kbd>.</p>\n\n<p>Also, note that for mod_perl, <kbd>bz_locations</kbd> must return\n  <em>absolute</em> (not relative) paths. There is already code in that\n  subroutine to help you with this.</p>\n\n<h3><a name=\"v30_code_hooks\"></a>Hooks!</h3>\n\n<p>";
    #line 806 "template\en\default\pages\release-notes.html.tmpl"
    $output .=  $stash->get(['terms', 0, 'Bugzilla', 0]);
    $output .=  " now supports a code hook mechanism. See the \n  documentation for \n  <a href=\"";
    #line 808 "template\en\default\pages\release-notes.html.tmpl"
    
    # FILTER
    $output .=  do {
        my $output = '';
        my $_tt_filter = $context->filter('html')
                  || $context->throw($context->error);
    
    $output .=  $stash->get(['Param', [ 'docs_urlbase' ]]);
        
        &$_tt_filter($output);
    };
    
    $output .=  "api/Bugzilla/Hook.html\">Bugzilla::Hook</a>\n  for more details.</p>\n\n<p>This gives ";
    #line 811 "template\en\default\pages\release-notes.html.tmpl"
    $output .=  $stash->get(['terms', 0, 'Bugzilla', 0]);
    $output .=  " very advanced plugin support. You can\n  hook templates, hook code, add new parameters, and use the XML-RPC\n  interface. So we'd like to see some ";
    #line 813 "template\en\default\pages\release-notes.html.tmpl"
    $output .=  $stash->get(['terms', 0, 'Bugzilla', 0]);
    $output .=  " plugins\n  written! Let us know on the <a href=\"http://bugzilla.org/cgi-bin/mj_wwwusr?func=lists-long-full&amp;extra=developers\">developers&#64;bugzilla.org</a>\n  mailing list if you write a plugin.</p>\n\n<p>If you need more hooks, please \n  <a href=\"http://www.bugzilla.org/developers/reporting_bugs.html\">File a\n  bug</a>!</p>\n\n<h3><a name=\"v30_code_api\"></a>API Documentation</h3>\n\n<p>";
    #line 823 "template\en\default\pages\release-notes.html.tmpl"
    $output .=  $stash->get(['terms', 0, 'Bugzilla', 0]);
    $output .=  " now ships with all of its perldoc built\n  as HTML. Go ahead and read the\n  <a href=\"";
    #line 825 "template\en\default\pages\release-notes.html.tmpl"
    
    # FILTER
    $output .=  do {
        my $output = '';
        my $_tt_filter = $context->filter('html')
                  || $context->throw($context->error);
    
    $output .=  $stash->get(['Param', [ 'docs_urlbase' ]]);
        
        &$_tt_filter($output);
    };
    
    $output .=  "api/\">API Documentation</a>\n  for all of the ";
    #line 826 "template\en\default\pages\release-notes.html.tmpl"
    $output .=  $stash->get(['terms', 0, 'Bugzilla', 0]);
    $output .=  " modules now! Even scripts like\n  <kbd>checksetup.pl</kbd> have HTML documentation.</p>\n\n<h3><a name=\"v30_code_globals\"></a>Elimination of globals.pl</h3>\n\n<p>The old file <kbd>globals.p