20
20
maintenance and support are critical for your long term success.
22
22
.. i18n: * Support aims to ensure that end users get the maximum productivity from their use of Open ERP by
23
.. i18n: responding to their questions on the use of the system. Support can be technical or functional.
25
* Maintenance aims to ensure that the system itself continues to function as required. It includes
26
system upgrades, which give you access to the latest functionality available.
23
.. i18n: responding to their questions on the use of the system. Support can be technical or functional.
28
25
.. i18n: * Maintenance aims to ensure that the system itself continues to function as required. It includes
29
.. i18n: system upgrades, which give you access to the latest functionality available.
26
.. i18n: system upgrades, which give you access to the latest functionality available.
28
* Support aims to ensure that end users get the maximum productivity from their use of Open ERP by
29
responding to their questions on the use of the system. Support can be technical or functional.
31
31
* Maintenance aims to ensure that the system itself continues to function as required. It includes
32
32
system upgrades, which give you access to the latest functionality available.
78
78
There are four sources of code change for Open ERP:
80
80
.. i18n: * patches supplied by Tiny to correct faults: after validation these patches shouldn't cause any
81
.. i18n: secondary effects,
81
.. i18n: secondary effects,
83
.. i18n: * minor updates, which gather the fault corrections together in one package, and are generally
84
.. i18n: announced with a modification of the version number, such as from 5.0.0 to 5.0.1,
86
.. i18n: * upgrades, which bundle both the fault corrections and the improvements to the functionality in a
87
.. i18n: major release such as from 5.0.3 to 5.2.0.
89
.. i18n: * new functions generally released in the form of new modules.
91
* patches supplied by Tiny to correct faults: after validation these patches shouldn't cause any
83
94
* minor updates, which gather the fault corrections together in one package, and are generally
84
95
announced with a modification of the version number, such as from 5.0.0 to 5.0.1,
86
.. i18n: * minor updates, which gather the fault corrections together in one package, and are generally
87
.. i18n: announced with a modification of the version number, such as from 5.0.0 to 5.0.1,
89
97
* upgrades, which bundle both the fault corrections and the improvements to the functionality in a
90
98
major release such as from 5.0.3 to 5.2.0.
92
.. i18n: * upgrades, which bundle both the fault corrections and the improvements to the functionality in a
93
.. i18n: major release such as from 5.0.3 to 5.2.0.
95
* new functions generally released in the form of new modules.
97
.. i18n: * new functions generally released in the form of new modules.
99
100
* new functions generally released in the form of new modules.
101
102
.. i18n: You should establish a procedure with your supplier to define how to respond to changes in the
187
188
The procedure for migrating runs like this:
189
.. i18n: #. Make a backup of the database from the old version of Open ERP
190
.. i18n: #. Make a backup of the database from the old version of Open ERP
192
.. i18n: #. Stop the server running the old version
194
.. i18n: #. Start the script called \ ``pre.py``\ for the versions you're moving between.
196
.. i18n: #. Start the new version of the server using the option –\ ``update=all``\
198
.. i18n: #. Stop the server running the new version.
200
.. i18n: #. Start the script called post.py for the versions you're moving between.
202
.. i18n: #. Start the new version of the server and test it.
204
#. Make a backup of the database from the old version of Open ERP
191
206
#. Stop the server running the old version
193
.. i18n: #. Stop the server running the old version
195
208
#. Start the script called \ ``pre.py``\ for the versions you're moving between.
197
.. i18n: #. Start the script called \ ``pre.py``\ for the versions you're moving between.
199
210
#. Start the new version of the server using the option –\ ``update=all``\
201
.. i18n: #. Start the new version of the server using the option –\ ``update=all``\
203
212
#. Stop the server running the new version.
205
.. i18n: #. Stop the server running the new version.
207
214
#. Start the script called post.py for the versions you're moving between.
209
.. i18n: #. Start the script called post.py for the versions you're moving between.
211
#. Start the new version of the server and test it.
213
.. i18n: #. Start the new version of the server and test it.
215
216
#. Start the new version of the server and test it.
217
218
.. i18n: A migration is never an easy process. It may be that your system doesn't function as it did before