Bug 379777: Finalize Release Notes for Bugzilla 3.0 (Also sync'ed branch relnotes with tip relnotes, since they differed slightly, with tip being newer.)

Patch By Max Kanat-Alexander <mkanat@bugzilla.org> r=LpSolit

1 files changed, 30 insertions, 11 deletions

diff --git a/template/en/default/pages/release-notes.html.tmpl b/template/en/default/pages/release-notes.html.tmpl
index a4e10d7b2..8e0f716fd 100644
--- a/template/en/default/pages/release-notes.html.tmpl
+++ b/template/en/default/pages/release-notes.html.tmpl
@@ -24,8 +24,6 @@
   style_urls = ['skins/standard/release-notes.css'] 
 %]
 
-<p><big>These release notes are currently a <strong>DRAFT</strong>.</big></p>
-
 <h2>Table of Contents</h2>
 
 <ul class="bz_toc">
@@ -312,6 +310,10 @@
 <p>You can control these notifications by changing the 
   <kbd>upgrade_notification</kbd> parameter.</p>
 
+<p>If your Bugzilla installation is on a machine that needs to go through
+  a proxy to access the web, you may also have to set the <kbd>proxy_url</kbd>
+  parameter.</p>
+
 <h3><a name="v30_feat_welc"></a>Welcome Page for New Installs</h3>
 
 <p>When you log in for the first time on a brand-new [% terms.Bugzilla %]
@@ -455,13 +457,26 @@
   <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.
-
-    <p>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.</p></li>
+    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 may currently not
+    be working on Windows machines. Also, even when it does work,
+    editparams.cgi seems to crash on certain versions of mod_perl.</li>
+  <li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=361149">
+    [%- terms.Bug %] 361149</a>: If you are using Perl 5.8.0, you may
+    get a lot of warnings in your Apache error_log about "deprecated
+    pseudo-hashes." These are harmless--they are a bug in Perl 5.8.0.
+    Perl 5.8.1 and later do not have this problem.</li>
+  <li>Bugzilla 3.0rc1 allowed custom field column names in the database
+    to be mixed-case. Bugzilla 3.0 only allows lowercase column names.
+    It will fix any column names that you have made mixed-case, but
+    if you have custom fields that previously were mixed-case in any
+    Saved Search, you will have to re-create that Saved Search yourself.</li>
 </ul>
 
 <h2><a name="v30_upgrading"></a>How to Upgrade From An Older Version</h2>
@@ -484,6 +499,10 @@
     at that time, that you have to follow before you can complete
     the upgrade. Don't do the conversion yourself manually--follow
     the instructions of checksetup.pl.</li>
+  <li>If you ever ran 2.23.3, 2.23.4, or 3.0rc1, you will have to run
+    <kbd>./collectstats.pl --regenerate</kbd> at the command line, because
+    the data for your Old Charts is corrupted. This can take several days,
+    so you may only want to run it if you use Old Charts.</li>
   <li>You should also read the Outstanding Issues sections of
     <a href="#v30_previous">older release notes</a> if you are upgrading
     from a version lower than 2.22.</li>
@@ -506,8 +525,8 @@
    installation can be corrupted beyond recovery. Having a backup keeps you
    safe.
 
-    <p>Example: <kbd>mysqldump -u root -p [% terms.bugs %] &gt; 
-      [% terms.bugs %]-db.sql</kbd></p></li>
+    <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.