From 6c709dd097e65025038a0dc9c17fad6a88e99b6b Mon Sep 17 00:00:00 2001 From: "gerv%gerv.net" <> Date: Sun, 25 Jan 2004 02:30:57 +0000 Subject: Massive rearrangement of the installation section. Hopefully it makes sense now. --- docs/html/upgrading.html | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) (limited to 'docs/html/upgrading.html') diff --git a/docs/html/upgrading.html b/docs/html/upgrading.html index e2956299d..bfbb59d47 100644 --- a/docs/html/upgrading.html +++ b/docs/html/upgrading.html @@ -7,7 +7,7 @@ NAME="GENERATOR" CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ ">The Bugzilla Guide - 2.17.5 +>The Bugzilla Guide - 2.17.7 Development ReleaseChapter 5. Administering BugzillaChapter 3. Administering Bugzilla5.9. Upgrading to New Releases3.9. Upgrading to New Releases

Using CVS (Example 5-1Example 3-1)

  • Downloading a new tarball (Example 5-2Example 3-2)

  • Applying the relevant patches (Example 5-3Example 3-3)

  • Example 5-1. Upgrading using CVSExample 3-1. Upgrading using CVS

    Every release of Bugzilla, whether it is a revision or a point @@ -352,7 +352,7 @@ NAME="upgrade-tarball" >

    Example 5-2. Upgrading using the tarballExample 3-2. Upgrading using the tarball

    If you are unable or unwilling to use CVS, another option that's @@ -508,7 +508,7 @@ NAME="upgrade-patches" >

    Example 5-3. Upgrading using patchesExample 3-3. Upgrading using patches

    The Bugzilla team will normally make a patch file available for @@ -588,7 +588,7 @@ CLASS="filename" > directory so it may make updates using CVS (Example 5-1Example 3-1) more difficult in the future.