Migration to version 9.0

[pedrobaeza]

Todo

https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-9.0

Dependencies

• product_m2mcategories Migration to version 9.0 product-attribute#100
• connector_ecommerce Migration to version 9.0 connector-ecommerce#26

Modules to migrate

• server_env_magentoerpconnect - Assigned to @SodexisTeam - [MIG][9.0] server env magentoerpconnect #201
• magentoerpconnect by @SodexisTeam in [WIP/MIG][9.0] Migrate magentoerpconnect #210
• magentoerpconnect_pricing
• magentoerpconnect_options_active
• customize_example
• magentoerpconnect_catalog
• magentoerpconnect_order_comment
• magentoerpconnect_export_partner

[jaredkipe]

Warning, incoming rant:
Am I the only one who feels like this rabbit hole is too deep?

To be able to install magentoerpconnect, you need to have connector and connector-ecommerce.
The 'connector-ecommerce' package has dependencies into oca/e-commerce. (e.g. sale_payment_method_automatic_workflow) and oca/sale-workflow (e.g. sale_exceptions)

Both e-commerce and sale-workflow have a ton of modules...!

magentoerpconnect requires 'product_m2mcategories' as well. That is found in oca/product-attribute which also has a ton of modules...!

Now that things are not installable out of the box you have to at least sed all of them to be installable just to try to get it to install. All of them together are ~100 modules, thats 40% of the whole odoo addons directory!

And just when you think you've solved everything.... BAM View error in product_m2mcategories... and back down the rabbit hole you go...

Ironically, I believe at least one potential solution to this would be to make magentoerpconnect more 'modularized' itself. This might be more in line with the modular Odoo vision (e.g. if you just want to sync partners because you are doing a CRM or PM only install), and it would be easier to manage dependencies on a per-module basis (e.g. partners is immune to the 80+ module dependancies for oca/e-commerce, oca/sale-workflow and oca/product-attribute)

[pedrobaeza]

You're starting the house by the roof: you have to migrate the first isolated dependency before (for example, product_m2m_categories), and when done, continue upwards until you have all the dependencies resolved. It's what a migration of such complex piece of software requires. No more, no less.

[jaredkipe]

No, I understand that. I guess my problem is more with the 'all or nothing' kind of setup on the core magentoerpconnect module. Installing it requires a lot of modules, and including core modules that maybe are not desired at the level of integration you are trying to do.

[guewen]

@jaredkipe I don't know any project where you need to synchronize only the partners or only the products with Magento. Generally, business-speaking, it is all-or-nothing. Also, separating a connector in many parts is painful, it really doesn't worth the pain in this case in my opinion.

[jaredkipe]

I understand your position, and the position of the current state of development, so I don't mean any disrespect.

Odoo advertises the ability to gradually convert a company's external services over to Odoo. E.g. by replacing Salesforce/SugarCRM =>CRM&SalesManagement, or Basecamp/JIRA => ProjectManagement. In both of those examples, a partners+products export/sync are desired.

To me, it seems overwhelmingly difficult to assist in moving a module like this one through a version bump when the dependencies spiral to 100 modules that all are 'help wanted'.

I mean, I can fix broken views, but does that mean its 9.0 ready? Especially with things called 'sales-workflow' when the core 'sales-workflow' changed so much?

[rvalyi]

@jaredkipe you have an other option if you cannot eat v9 now: you can go v8 which works well and in 2 or 3 years you migrate to a newer version (but that won't be easy either). You'll always have a newer more shinny version but eventually not all complex modules will be ported at the time you need them. The pace of evolution of Odoo will probably slow down, but untill now it had to evolve so it's the way it is...

[jaredkipe]

@rvalyi Thats not entirely true, I can just comment out depends and data files in __openerp__.py and comment out imports in__init__.py
I could also fork and rewrite it, which was going to be my initial plan but decided that it wasn't in the 'OCA Spirit'.

[rvalyi]

@jaredkipe well yes eventually you could make a subset of it indeed. Eventually that can help the port initiative and your work or part of it could be merged.

[pedrobaeza]

@rvalyi, if he actually makes a fork, he will for sure be alone in his solitaire code. A better strategy is to collaborate to migrate some part of the puzzle (some of the dependencies), announce that to avoid the duplication of efforts, and let others make another piece of this puzzle.