Contributors mailing list archives
contributors@odoo-community.org
Browse archives
Removal of migration scripts on each new version
by
Opener B.V., Stefan Rijnhart
Hi,
the migration guide mandates the following
> Remove any possible migration script from previous version (in a nutshell, remove
(https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-18.0#tasks-to-do-in-the-migration)
However, it is not uncommon to skip versions when migrating an Odoo instance. You would go from 15.0 or 16.0 to 18.0 rather than migrating every year. When using the Odoo enterprise migration, the migration scripts between the source and the target version are supposed to be present in the target version. So the migration guideline breaks this type of migration.
I had a disagreement with Pedro Baeza about this on one PR, but I keep coming across instances of this such as https://github.com/OCA/account-invoicing/pull/1874 today so I would like to discuss this in a wider audience.
My preference would be for the guideline to change to say that it is allowed to keep some of the scripts if they are safe for inclusion in the later version (such as the script from https://github.com/OCA/account-invoicing/pull/1874, which checks if a field already exists before trying to add it).
Can I have a temperature check from the community to see how you all feel about this?
Best regards,
Stefan
the migration guide mandates the following
> Remove any possible migration script from previous version (in a nutshell, remove
migrations
folder inside the module
if exists).(https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-18.0#tasks-to-do-in-the-migration)
However, it is not uncommon to skip versions when migrating an Odoo instance. You would go from 15.0 or 16.0 to 18.0 rather than migrating every year. When using the Odoo enterprise migration, the migration scripts between the source and the target version are supposed to be present in the target version. So the migration guideline breaks this type of migration.
I had a disagreement with Pedro Baeza about this on one PR, but I keep coming across instances of this such as https://github.com/OCA/account-invoicing/pull/1874 today so I would like to discuss this in a wider audience.
My preference would be for the guideline to change to say that it is allowed to keep some of the scripts if they are safe for inclusion in the later version (such as the script from https://github.com/OCA/account-invoicing/pull/1874, which checks if a field already exists before trying to add it).
Can I have a temperature check from the community to see how you all feel about this?
Best regards,
Stefan
-- Opener B.V. - Business solutions driven by open source collaboration Stefan Rijnhart - Consultant/developer mail: stefan@opener.amsterdam tel: +31 (0) 6 1447 8606 web: https://opener.amsterdam
Follow-Ups
-
Re: Removal of migration scripts on each new version
byComunitea, Javier Colmenero Fernández -
Re: Removal of migration scripts on each new version
by "Richard deMeester" <richard.demeester@willdooit.com> - 07/05/2025 15:49:29 - 12 -
Re: Removal of migration scripts on each new version
byOpener B.V., Stefan Rijnhart -
Re: Removal of migration scripts on each new version
byDIXMIT Consulting SLU, Enric Tobella Alomar -
Re: Removal of migration scripts on each new version
byCamptocamp France SAS, Sébastien Alix -
Re: Removal of migration scripts on each new version
byAcsone SA/NV, Stéphane Bidoul -
Re: Removal of migration scripts on each new version
bySygel Technology S.L., Valentín Vinagre -
Re: Removal of migration scripts on each new version
byAkretion France., Raphaël Reverdy -
Re: Removal of migration scripts on each new version
byTherp, Tom Blauwendraat -
Re: Removal of migration scripts on each new version
byMoaHub, Graeme Gellatly