4501.3.1
by Ian Clatworthy
first draft of a 2.0 Upgrade Guide |
1 |
Overview |
2 |
######## |
|
3 |
||
4501.3.3
by Ian Clatworthy
various tweaks & standalone branch upgrade process |
4 |
High level upgrade process |
4501.3.1
by Ian Clatworthy
first draft of a 2.0 Upgrade Guide |
5 |
-------------------------- |
6 |
||
7 |
In broad terms, there are 3 steps involved in upgrading to Bazaar 2.x: |
|
8 |
||
9 |
1. Upgrade the core software |
|
10 |
||
11 |
2. Upgrade required plugins |
|
12 |
||
13 |
3. Migrate data to the new default format. |
|
14 |
||
15 |
Bazaar 2.x supports branches in earlier formats so the third step is |
|
16 |
strictly not required. However, the new default format in Bazaar 2.x |
|
17 |
is more space efficient, faster on large projects and provides a range |
|
18 |
of new features, so it is recommended that most projects migrate to it |
|
19 |
at a convenient time. |
|
20 |
||
21 |
For most users, upgrading to 2.x and migrating to the new format is |
|
22 |
straight forward. For projects with a large community of developers |
|
23 |
though, things become more complex. In these cases, careful planning |
|
24 |
and good communications become essential. This document provides |
|
25 |
general advice which aims to assist in this regard. If in doubt, |
|
26 |
please contact us on our mailing list or IRC channel with any |
|
27 |
questions or concerns you have. |
|
28 |
||
29 |
||
30 |
Upgrading the core software |
|
31 |
--------------------------- |
|
32 |
||
33 |
The steps required to upgrade the core software vary from operating |
|
34 |
system to operating system. There is nothing special about upgrading |
|
35 |
from Bazaar 1.x to Bazaar 2.0 compared to upgrading from Bazaar 1.x |
|
36 |
to Bazaar 1.y. In either case, a brief outline of the steps is given |
|
37 |
below. |
|
38 |
||
39 |
To upgrade Bazaar on Linux: |
|
40 |
||
41 |
1. Ensure your package manager is configured with the required |
|
42 |
software sources, e.g. the official release PPA for Ubuntu: |
|
43 |
https://launchpad.net/~bzr/+archive |
|
44 |
||
45 |
2. Use your package manager to upgrade to the latest version. |
|
46 |
||
47 |
To upgrade Bazaar on Windows: |
|
48 |
||
49 |
1. Uninstall the existing version using Add/Remove Programs. |
|
50 |
||
51 |
2. Install the new version using the relevant installer. |
|
52 |
||
53 |
To upgrade Bazaar on OS X (via the installer): |
|
54 |
||
4501.3.6
by Ian Clatworthy
Apply review feedback |
55 |
1. Install the new version using the relevant installer. |
4501.3.1
by Ian Clatworthy
first draft of a 2.0 Upgrade Guide |
56 |
|
57 |
To upgrade Bazaar on OS X (via MacPorts): |
|
58 |
||
59 |
1. Refresh the package metadata using **sudo port selfupdate** |
|
60 |
||
61 |
2. Upgrade to the latest version using **sudo port upgrade bzr** |
|
62 |
||
4501.3.3
by Ian Clatworthy
various tweaks & standalone branch upgrade process |
63 |
For further information on installing and upgrading, see |
4501.3.1
by Ian Clatworthy
first draft of a 2.0 Upgrade Guide |
64 |
http://bazaar-vcs.org/Download. |
65 |
||
66 |
||
67 |
Upgrading required plugins |
|
68 |
-------------------------- |
|
69 |
||
70 |
Many plugins are not dependent on a particular Bazaar version so |
|
71 |
upgrading them is optional. Other plugins, notably bzrtools and |
|
72 |
bzr-svn, are more tightly associated with Bazaar's APIs so these |
|
73 |
typically need to be upgraded in lockstep with the core software. |
|
74 |
||
75 |
For Windows and OS X users, bzrtools and bzr-svn are typically |
|
76 |
included in the installer so no special steps are required to upgrade |
|
77 |
these. For Linux and UNIX users, bztrools, bzr-svn and many other |
|
78 |
popular plugins can be installed and upgraded using your |
|
4501.3.3
by Ian Clatworthy
various tweaks & standalone branch upgrade process |
79 |
platform's package manager, e.g. Synaptic on Ubuntu. |
4501.3.1
by Ian Clatworthy
first draft of a 2.0 Upgrade Guide |
80 |
|
81 |
||
82 |
Migrating data to the new default format |
|
83 |
---------------------------------------- |
|
84 |
||
85 |
As mentioned earlier, the complexity of migrating to a new format |
|
86 |
depends on several factors, particularly project community size. |
|
87 |
It also depends on how data is currently stored, e.g. in a |
|
88 |
standalone branch, multiple branches in a shared repository, |
|
89 |
stacked branches on Launchpad, etc. These various scenarios are |
|
90 |
covered in the next chapter. |