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 versionbyComunitea, Javier Colmenero Fernández- 07/05/2025 16:41:14 - 0
- 
                Re: Removal of migration scripts on each new versionby "Richard deMeester" <richard.demeester@willdooit.com> - 07/05/2025 15:49:29 - 12
- 
                Re: Removal of migration scripts on each new versionbyOpener B.V., Stefan Rijnhart- 07/05/2025 15:41:34 - 0
- 
                Re: Removal of migration scripts on each new versionbyDIXMIT Consulting SLU, Enric Tobella Alomar- 07/05/2025 12:46:40 - 0
- 
                Re: Removal of migration scripts on each new versionbyCamptocamp France SAS, Sébastien Alix- 07/05/2025 12:22:27 - 0
- 
                Re: Removal of migration scripts on each new versionbyAcsone SA/NV, Stéphane Bidoul- 07/05/2025 12:06:52 - 0
- 
                Re: Removal of migration scripts on each new versionbySygel Technology S.L., Valentín Vinagre- 07/05/2025 11:58:25 - 0
- 
                Re: Removal of migration scripts on each new versionbyAkretion France., Raphaël Reverdy- 07/05/2025 11:41:01 - 0
- 
                Re: Removal of migration scripts on each new versionbyTherp, Tom Blauwendraat- 07/05/2025 08:54:02 - 0
- 
                Re: Removal of migration scripts on each new versionbyMoaHub, Graeme Gellatly- 07/05/2025 00:29:27 - 0