Analysis - rename repositories and module

[robinkeunen]

We first mapped the module dependencies.
- cf #247
- cf coopiteasy/vertical-cooperative#170

This will be used to prioritise the module migration. We will start by the root modules.

We took these three cases to explore the migration scripts and estimate the time needed for migration.

• [12.0] rename easy my coop to cooperator coopiteasy/vertical-cooperative#202
  • easy_my_coop => cooperator
  • + repercussions cooperator_portal
  • rename xml_id prefixes (easy_my_coop.subscription_request_form)
  • + repercussions to easy_my_coop_api
• [WIP] Split beesdoo_product #264
  • beesdoo_product = beesdoo_product + sale_suggested_price
• [WIP] merging emc_loan and emc_loan_website coopiteasy/vertical-cooperative#201
  • easy_my_coop_loan + easy_my_coop_loan_website = loan

---

Following our investigations, here is the selected solution :

We will use update_module_names function from openupgradelib.

In openupgrade this function is used when updating the base module : here. The base module is always the first to be updated as all module depends of it. So this rename function is run before any action take place. This can't be applied in our context.

Therefore, we will create a script rename_deprecated_modules.py for the entire repository that will be run in an odoo shell before every updade. That script calls the rename function of openupgradelib.

With the modules and depending datas renamed, the update of the module will

1. run the pre-update and post-update hooks
2. update all the data from the new module and its dependencies.