3
.. i18n: single: Update; Upgrade; OpenERP (Linux)
7
single: Update; Upgrade; OpenERP (Linux)
9
.. i18n: .. _updating-linux-link:
11
.. i18n: ===============================================================================
12
.. i18n: Updating your OpenERP Installation
13
.. i18n: ===============================================================================
16
.. _updating-linux-link:
18
===============================================================================
19
Updating your OpenERP Installation
20
===============================================================================
22
.. i18n: Going to a Newer Minor/Patch Release
23
.. i18n: ++++++++++++++++++++++++++++++++++++
26
Going to a Newer Minor/Patch Release
27
++++++++++++++++++++++++++++++++++++
29
.. i18n: OpenERP's release policy states that minor/patch releases of the stable
30
.. i18n: versions are usually published every month. These are recommended for
31
.. i18n: production deployment, as they include the latest security updates and bugfixes,
32
.. i18n: and do not require any migration process.
35
OpenERP's release policy states that minor/patch releases of the stable
36
versions are usually published every month. These are recommended for
37
production deployment, as they include the latest security updates and bugfixes,
38
and do not require any migration process.
40
.. i18n: Of course you should always test these updates on a staging environment
41
.. i18n: (copy of your production environment) before applying them on the real
42
.. i18n: production systems.
45
Of course you should always test these updates on a staging environment
46
(copy of your production environment) before applying them on the real
49
.. i18n: Minor/patch releases of OpenERP are identified by an increasing 3rd release
50
.. i18n: number, for example, v6.0.15 would be the 15th patch release of OpenERP v6.0.
53
Minor/patch releases of OpenERP are identified by an increasing 3rd release
54
number, for example, v6.0.15 would be the 15th patch release of OpenERP v6.0.
56
.. i18n: For more details regarding the release cycle, have a look at the section
57
.. i18n: :ref:`release_cycle`.
60
For more details regarding the release cycle, have a look at the section
63
.. i18n: .. note:: Minor Versions
65
.. i18n: You can skip minor versions, for example, you do not need to install all the intermediary versions between 6.0.6 and 6.0.15 if you need to upgrade an outdated installation, as long as you stay in the same version line (6.0 in this example).
68
.. note:: Minor Versions
70
You can skip minor versions, for example, you do not need to install all the intermediary versions between 6.0.6 and 6.0.15 if you need to upgrade an outdated installation, as long as you stay in the same version line (6.0 in this example).
72
.. i18n: Updating an existing OpenERP installation to a newer patch release boils down
73
.. i18n: to 2 operations:
76
Updating an existing OpenERP installation to a newer patch release boils down
79
.. i18n: * Install the new code over the existing one
80
.. i18n: * Synchronize each existing database with the new code
83
* Install the new code over the existing one
84
* Synchronize each existing database with the new code
86
.. i18n: In order to accomplish this, the following step-by-step procedure should give you
87
.. i18n: the best results:
90
In order to accomplish this, the following step-by-step procedure should give you
93
.. i18n: #. Make a fresh backup of all existing databases, as well as a backup of the files
94
.. i18n: of your OpenERP installation (server and addons), just in case.
95
.. i18n: #. Locate the executable file to start the Server, it should be named
96
.. i18n: ``openerp-server.py``. You may want to have a look at the running processes
97
.. i18n: to find out the command-line parameters that are passed to the server (needed below).
98
.. i18n: #. Stop the OpenERP server.
99
.. i18n: #. Update the source files to the latest release, or simply install the new releases
100
.. i18n: over the previous ones.
101
.. i18n: #. Start the server manually (directly call the executable you located above), with
102
.. i18n: the following additional parameters, to trigger an update of all module data and
103
.. i18n: views in the database, based on the new source files (include your usual startup
104
.. i18n: parameters, if any, and replace ``DB_NAME`` with the name of the OpenERP database you wish
105
.. i18n: to update)::
107
.. i18n: openerp-server.py -d DB_NAME -u all
109
.. i18n: #. Let the server complete its startup (watch the log for the final message that says
110
.. i18n: ``OpenERP server is running, waiting for connections`` or wait until you can connect
111
.. i18n: to that database with a GTK client), then stop the server with :kbd:`Ctrl+C` and repeat the
112
.. i18n: previous step for each database on this OpenERP installation (any database not updated
113
.. i18n: will use the latest business logic but might have errors or missing improvements in
114
.. i18n: the views until you update it using this procedure).
115
.. i18n: #. Stop the server again with :kbd:`Ctrl+C` and restart it normally (no extra parameters anymore).
116
.. i18n: #. You can now proceed with the update of the GTK clients,
117
.. i18n: by simply reinstalling the latest version over the previous one.
120
#. Make a fresh backup of all existing databases, as well as a backup of the files
121
of your OpenERP installation (server and addons), just in case.
122
#. Locate the executable file to start the Server, it should be named
123
``openerp-server.py``. You may want to have a look at the running processes
124
to find out the command-line parameters that are passed to the server (needed below).
125
#. Stop the OpenERP server.
126
#. Update the source files to the latest release, or simply install the new releases
127
over the previous ones.
128
#. Start the server manually (directly call the executable you located above), with
129
the following additional parameters, to trigger an update of all module data and
130
views in the database, based on the new source files (include your usual startup
131
parameters, if any, and replace ``DB_NAME`` with the name of the OpenERP database you wish
134
openerp-server.py -d DB_NAME -u all
136
#. Let the server complete its startup (watch the log for the final message that says
137
``OpenERP server is running, waiting for connections`` or wait until you can connect
138
to that database with a GTK client), then stop the server with :kbd:`Ctrl+C` and repeat the
139
previous step for each database on this OpenERP installation (any database not updated
140
will use the latest business logic but might have errors or missing improvements in
141
the views until you update it using this procedure).
142
#. Stop the server again with :kbd:`Ctrl+C` and restart it normally (no extra parameters anymore).
143
#. You can now proceed with the update of the GTK clients,
144
by simply reinstalling the latest version over the previous one.
146
.. i18n: .. note:: Server
148
.. i18n: As an alternative to restarting the server in update mode for each database, as described above, you may try to start the server normally, and then connect to each database as the *Administrator* user, open the list of modules and manually trigger an update of the *base* module. Because all modules depend on *base* they will be updated too. However this requires the *Administrator* password of each database and may not work for some updates, specifically when the update prevents you from logging into the system.
153
As an alternative to restarting the server in update mode for each database, as described above, you may try to start the server normally, and then connect to each database as the *Administrator* user, open the list of modules and manually trigger an update of the *base* module. Because all modules depend on *base* they will be updated too. However this requires the *Administrator* password of each database and may not work for some updates, specifically when the update prevents you from logging into the system.
155
.. i18n: .. tip:: Developer Book
157
.. i18n: For more technical details on the actual operations accomplished by the server during such an update, you may refer to the corresponding section in the Developer Book: :ref:`technical_update_procedure`.
160
.. tip:: Developer Book
162
For more technical details on the actual operations accomplished by the server during such an update, you may refer to the corresponding section in the Developer Book: :ref:`technical_update_procedure`.
164
.. i18n: Going to a Newer Major Release
165
.. i18n: ++++++++++++++++++++++++++++++
168
Going to a Newer Major Release
169
++++++++++++++++++++++++++++++
171
.. i18n: The frequency of major stable releases has fluctuated in the past, but the current policy is to release a new stable version every 6 months on average, with one out of three stable versions being a Long Term Support (LTS) version. An LTS version is a normal stable version, but one that is supported for an extended time under the OpenERP Publisher’s Warranty (OPW). Stable versions are labelled as a decimal number with 2 components (e.g. 6.1), where the leftmost part indicates the corresponding Long Term Support (LTS) version, and the second digit indicates successive stable releases between two LTS versions.
174
The frequency of major stable releases has fluctuated in the past, but the current policy is to release a new stable version every 6 months on average, with one out of three stable versions being a Long Term Support (LTS) version. An LTS version is a normal stable version, but one that is supported for an extended time under the OpenERP Publisher’s Warranty (OPW). Stable versions are labelled as a decimal number with 2 components (e.g. 6.1), where the leftmost part indicates the corresponding Long Term Support (LTS) version, and the second digit indicates successive stable releases between two LTS versions.
176
.. i18n: Transitioning to the next major release implies a lot more changes than jumping to another minor release.
177
.. i18n: As the underlying OpenERP data structures usually evolve quite a bit from one major release to the next, a full migration of the existing data is needed.
178
.. i18n: Each major release will be published with specific recommendations and procedures for upgrading an existing OpenERP system to the next major version.
181
Transitioning to the next major release implies a lot more changes than jumping to another minor release.
182
As the underlying OpenERP data structures usually evolve quite a bit from one major release to the next, a full migration of the existing data is needed.
183
Each major release will be published with specific recommendations and procedures for upgrading an existing OpenERP system to the next major version.