105877 - Backup & check for modifications before upgrade.

Status: RESOLVED FIXED

(Bugzilla :: Documentation, defect, P3)

Description

[Matthew Tuck [:CodeMachine]]

The upgrading section should mention backing up before each upgrade as good
practice as always.

It should probably also mention overwriting the code is only appropriate if you
haven't made mods to the code (as many ppl do).  Admins who've inherited a
system might not be aware of this.

Comment 1

[Jacob Steenhagen]

Perhaps we could also mention that if your upgrading from version 2.12 or later
you can use CVS which will tell you about conflicts, etc. as mentioned on the
download page.  Of course, we should still mention that backing up before you
start is a good thing :)

http://www.mozilla.org/projects/bugzilla/download.html

Comment 2

[Dave Miller [:justdave]]

We are currently trying to wrap up Bugzilla 2.16.  We are now close enough to
release time that anything that wasn't already ranked at P1 isn't going to make
the cut.  Thus this is being retargetted at 2.18.  If you strongly disagree with
this retargetting, please comment, however, be aware that we only have about 2
weeks left to review and test anything at this point, and we intend to devote
this time to the remaining bugs that were designated as release blockers.

Comment 3

[Dave Miller [:justdave]]

The docs should always be up-to-date when we release.  Forgot to exclude
Documentation when I mass-retargetted.

Comment 4

[Dave Miller [:justdave]]

Barnboy changed his email address and opened a new account instead of having the
address changed on his existing one.  Reassigning all docs bugs to his new account.

Comment 5

[Gervase Markham [:gerv]]

Fixed in section 3.5.2.

Checking in docs/sgml/installation.sgml;
/cvsroot/mozilla/webtools/bugzilla/docs/sgml/installation.sgml,v  <-- 
installation.sgml
new revision: 1.17; previous revision: 1.16
done

Gerv