Comment 159 for bug 1160365

@fabien

We all agree we need 2 levels, but disagree on field names:
* The community wants contact and partner
* OpenERP SA wants partner and commercial_entity

If we were having this discussion a year ago I would say : "Let's go with your data model with the same field names : contact vs partner" and OpenERP SA would have implemented it during 2012.

Unfortunately, we never had this discussion last year, you chose to use one field partner_id and forgot about the second level. You realized the problem 3 months after the release and now you want to add the second level with commercial_entity_id.

You are just trying to push your solution into our throat, because you already did the migration of your modules to the new field names. You leave us with no other way than migrating our modules AND updating them to your field names. You made a mistake and the community has to assume it. This is not fair and unprofessional.

Where does this lead us ?
1) OpenERP SA merges Olivier's branch and the community adapts his modules to use partner vs commercial entity.
2) OpenERP SA assumes his responsibility, reverts its modules to use contact vs partner, releases a 7.1 and handles the migration from 7.0 to 7.1.

Fabien, can you provide a third option where each party will at least get out of this situation with something ? Otherwise the frustration will go on forever.

Can you also make sure the Community is involved earlier in the process to avoid this situation in the future ? I hope we will use this situation as a way to grow and move forward.

Thank you very much for your answer (comment #146).