Pedro M. Baeza

This module is clearly mature, but not set explicitly for to nobody putting that. Anyway, the rule is to not add any extra dependency on an already migrated module until...

@hbrunn it's an issue if in your deployments, you have restricted the available modules, and anyway, when the business model is based on the installed modules (like mine), you don't...

We contribute because we do business, so yes, business is important here, and there are no technical barriers to split this feature into the new module, so there are no...

I'm not ranting. I'm opposing to this change as is, and reasoning why, as you can change easily the approach creating an extra module on top.

Yes, and how this compares to the current case? Starting with, the PR you are referring to, in the state where I blocked it, contained potential harmful DB schema changes...

Please read https://github.com/OCA/odoo-community.org/issues/193#issuecomment-2448846096, which expresses clearly right now how I feel.

FWIW, I still don't want such feature in the base module. It's to give more fuel to my users to screw up database. That's why I also insist on not...

/ocabot migration website_sale_product_assortment

Hi, Frédéric! I'm afraid the tool is not thought for that mass-update. It's easy to pipe through a shell script for doing in mass though, but not having decision power...

There's not too much problem in creating new accounts, but new taxes should be more controlled, specially in Spain, as the localization modules don't use taxes grids (it's a conscious...