Odoo Repository Migration Data
This module collects and records modules migration data from Odoo repositories.
Thanks to oca-port and data collected by odoo_repository, this module will generate migration data on each module for declared migration paths (e.g. 16.0 -> 18.0).
Also, for specific cases you can declare what a module became in a given Odoo version, like OCA web_domain_field replaced by standard Odoo module web starting from 17.0 (with an optional explanation that could help users, like how to use this new module compared to the previous one).
Given a migration path, a module can get one of this migration status:
Status |
Description |
|---|---|
Fully Ported |
All commits from source version are present in target version |
To migrate |
The module doesn’t exist on target version |
Ported (missing commits?) |
Some commits from source version are not ported in target version (could be false-positive) |
To review |
A migration PR has been detected |
Replaced |
The module has been replaced by another one (not sharing the same git history) |
Moved to standard? |
The module name has been detected in Odoo standard repositories for target version. High chance this module is or should be replaced by another one instead (by creating a timeline), so it mainly helps to detect such cases. |
Moved to OCA |
the module name is available in an OCA repository (could be a false-positive because sharing the same name, in such case a timeline has to be created) |
Moved to generic repo |
a specific module (only available in a project) in source version now exists in a generic repository (could be a false-positive if both modules have only their name in common) |
It helps to build a consolidated knowledge database accross different Odoo versions for everyone: functionals and developers.
Table of contents
Usage
To enable this feature, the option Collect migration data should be enabled on repositories (opt-in).
To record what a module became starting from a given Odoo version, you should do it through the Odoo Repositories / Data / Modules / Timelines menu.
Once the scheduled action ran, the migration data are available on each module in Migration tab, or through the Odoo Repositories / Data / Modules / Migrations menu.
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
Contributors
Camptocamp
Sébastien Alix <seb@usr-src.org>
Maintainers
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
This module is part of the OCA/module-composition-analysis project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
1 maintainer
Release files for odoo-addon-odoo-repository-migration 18.0.1.1.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| odoo_addon_odoo_repository_migration-18.0.1.1.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Release files / odoo_addon_odoo_repository_migration-18.0.1.1.0.3-py3-none-any.whl
| Download URL | odoo_addon_odoo_repository_migration-18.0.1.1.0.3-py3-none-any.whl |
|---|---|
| Size | 57.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ea511f29b5eef2745332acf8bdc66f95032d5e7afaf26a35de91cf0472cc64f8
|
|
BLAKE2b-256 checksum How to use checksums |
e38bf1d4a628817c8b824e5186150fbb9507ecd31411e900a60f3780ccbdc5a6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
