Openupgrade Framework

Installation

This module does not need to be installed on a database. It simply needs to be available via your addons-path.

Configuration

• call your odoo instance with the option --load=base,web,openupgrade_framework

or

• add the key to your configuration file:

[options]
server_wide_modules = web,openupgrade_framework

When you load the module in either way of these ways, and you have the openupgrade_scripts module in your addons path available, the –upgrade-path option of Odoo will be set automatically to the location of the OpenUpgrade migration scripts.

Development

The odoo_patch folder contains python files in a tree that mimicks the folder tree of the Odoo project. It contains a number of monkey patches to improve the migration of an Odoo database between two major versions.

So far, we are able to make everything work without overwriting large blocks of code, but if larger patches need to be added, please use the method described below:

To see the patches added, you can use meld tools:

meld PATH_TO_ODOO_FOLDER/odoo/ PATH_TO_OPENUPGRADE_FRAMEWORK_MODULE/odoo_patch

To make more easy the diff analysis :

• Make sure the python files has the same path as the original one.
• Keep the same indentation as the original file. (using if True: if required)
• Add the following two lines at the beginning of your file, to avoid flake8 / pylint errors

# flake8: noqa
# pylint: skip-file

• When you want to change the code. add the following tags:

For an addition:

# <OpenUpgrade:ADD>
some code...
# </OpenUpgrade>

For a change:

# <OpenUpgrade:CHANGE>
some code...
# </OpenUpgrade>

For a removal:

# <OpenUpgrade:REMOVE>
# Comment the code, instead of removing it.
# </OpenUpgrade>

Bug Tracker

Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.

Do not contact contributors directly about support or help with technical issues.

Credits