From b6d72360ea168aaa9bcb51ae12569897db3ab34a Mon Sep 17 00:00:00 2001 From: "mkanat%bugzilla.org" <> Date: Thu, 7 Aug 2008 13:57:31 +0000 Subject: Bug 449504: Release Notes no longer need upgrading instructions Patch By Max Kanat-Alexander r=LpSolit --- template/en/default/pages/release-notes.html.tmpl | 90 ++--------------------- 1 file changed, 6 insertions(+), 84 deletions(-) (limited to 'template/en/default') diff --git a/template/en/default/pages/release-notes.html.tmpl b/template/en/default/pages/release-notes.html.tmpl index 7858d1d15..5e62281c0 100644 --- a/template/en/default/pages/release-notes.html.tmpl +++ b/template/en/default/pages/release-notes.html.tmpl @@ -416,48 +416,9 @@

Steps For Upgrading

-
    -
  1. Read these entire Release Notes, particularly the "Notes for - Upgraders" section above.
    2. - -
  2. View the Sanity Check 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.
    3. - -
  3. Make a backup of the [% terms.Bugzilla %] database before you upgrade, - perhaps by using mysqldump. THIS IS VERY - IMPORTANT. If anything goes wrong during the upgrade, your - installation can be corrupted beyond recovery. Having a backup keeps you - safe. - -

    Example: mysqldump -u root -p bu[%# trick filter %]gs > - bu[%# trick filter %]gs-db.sql

    4. - -
  4. Replace the files in your installation with the new version of - [% terms.Bugzilla %], or you can try to use CVS to upgrade. - -

    You can also use a brand-new [% terms.Bugzilla %] directory, as long - as you copy over the old data/ directory and the - localconfig file to the new installation.

    5. - -
  5. Now follow the standard - - [%- terms.Bugzilla %] installation process.
    6. - -
  6. Run checksetup.pl after you install the new version.
    7. - -
  7. View the Sanity Check page again after - you run checksetup.pl.
    8. - -
  8. 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.
    9. -
+

Once you have read the notes above, see the + Upgrading + documentation for instructions on how to upgrade.

Code Changes Which May Affect Customizations

@@ -1325,48 +1286,9 @@

Steps For Upgrading

-
    -
  1. Read these entire Release Notes, particularly the "Notes for - Upgraders" section above.
    2. - -
  2. View the Sanity Check 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.
    3. - -
  3. Make a backup of the [% terms.Bugzilla %] database before you upgrade, - perhaps by using mysqldump. THIS IS VERY - IMPORTANT. If anything goes wrong during the upgrade, your - installation can be corrupted beyond recovery. Having a backup keeps you - safe. - -

    Example: mysqldump -u root -p bu[%# trick filter %]gs > - bu[%# trick filter %]gs-db.sql

    4. - -
  4. Replace the files in your installation with the new version of - [% terms.Bugzilla %], or you can try to use CVS to upgrade. - -

    You can also use a brand-new [% terms.Bugzilla %] directory, as long - as you copy over the old data/ directory and the - localconfig file to the new installation.

    5. - -
  5. Now follow the standard - - [%- terms.Bugzilla %] installation process.
    6. - -
  6. Run checksetup.pl after you install the new version.
    7. - -
  7. View the Sanity Check page again after - you run checksetup.pl.
    8. - -
  8. 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.
    9. -
+

Once you have read the notes above, see the + Upgrading + documentation for instructions on how to upgrade.

Code Changes Which May Affect Customizations

-- cgit v1.2.3-24-g4f1b