blob: 78b4fb1e088be6f2b18f096ddc46c5959d548e1c (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
|
.. _upgrading-with-git:
Upgrading with Git
##################
Upgrading to new Bugzilla releases is very simple, and you can upgrade
from any version to any later version in one go - there is no need for
intermediate steps. There is a script named :file:`checksetup.pl` included
with Bugzilla that will automatically do all of the database migration
for you.
.. include:: upgrading-with-1.inc.rst
You can see if you have local code customizations using:
:command:`git diff`
If that comes up empty, then run:
:command:`git log | head`
and see if the last commit looks like one made by the Bugzilla team, or
by you. If it looks like it was made by us, then you have made no local
code customizations.
.. _start-upgrade-git:
Starting the Upgrade
====================
When you are ready to go:
#. Shut down your Bugzilla installation by putting some explanatory text
in the :param:`shutdownhtml` parameter.
#. Make all necessary :ref:`backups <backups>`.
*THIS IS VERY IMPORTANT*. If anything goes wrong during the upgrade,
having a backup allows you to roll back to a known good state.
.. _upgrade-files-git:
Getting The New Bugzilla
========================
In the commands below, ``$BUGZILLA_HOME`` represents the directory
in which Bugzilla is installed. Assuming you followed the installation
instructions and your Bugzilla is a checkout of a stable branch,
you can get the latest point release of your current version by simply doing:
:command:`cd $BUGZILLA_HOME`
:command:`git pull`
If you want to upgrade to a newer release of Bugzilla, then you will
additionally need to do:
:command:`git checkout bugzilla-X.X-stable`
where "X.X" is the 2-digit version number of the stable version you want to
upgrade to (e.g. "4.4").
.. note:: Do not attempt to downgrade Bugzilla this way - it won't work.
If you have local code customizations, git will attempt to merge them. If
it fails, then you should implement the plan you came up with when you
detected these customizations in the step above, before you started the
upgrade.
.. include:: upgrading-with-2.inc.rst
|
