Dear Maintainer,

Moving between Odoo releases requires an upgrade process.  The OCA have such a
process (the native Odoo one is a pay for option and thus not relevant to
Debian).  This process is normally integrated with the OCA packaged Odoo
distributions.

Without the upgrade process a user would have to re-enter all the data from a
previous release in order to move to the new release, which is clearly a manual
and thus error prone process.

If the OCA upgrade process were integrated such upgrades could be done
automatically for the user, which would greatly improve the ease of use and
uptake of Odoo.

Thank you.

Hi,

Yes, that's the reason why we opted to use versioned binary packages so
that you don't upgrade to a new major version by mistake.

Can you give some pointers here?

When we looked at OCA's fork of Odoo, there were no changes to Odoo. And
that's the reason why we dropped "oca-core" from Debian.

I know they created supplementary "plugins" and anyone is certainly free
to package those supplementary plugins if they find them useful.

Cheers,

https://github.com/OCA/OpenUpgrade[1]

You are right that it now seems to be in the form of an installable addon, and that it comes
in two parts for the Odoo-14 branch.


*addon*
*version*
*summary*
https://github.com/OCA/OpenUpgrade/blob/14.0/openupgrade_framework[2]
14.0.1.0.0
Module to integrate in the server_wide_modules option to make upgrades between two
major revisions.
https://github.com/OCA/OpenUpgrade/blob/14.0/openupgrade_scripts[3]
14.0.1.0.0
Module that contains all the migrations analysis and scripts for migrate Odoo SA modules.

This looks much easier to install, and to include in the Odoo-14 package than previous
versions.

The documentation is very out of date, stopping at Odoo-11, but there does seem to be
(as above) an active Odoo-14 branch.

--------
[1] https://github.com/OCA/OpenUpgrade
[2] https://github.com/OCA/OpenUpgrade/blob/14.0/openupgrade_framework
[3] https://github.com/OCA/OpenUpgrade/blob/14.0/openupgrade_scripts