@fabien: thanks for this comment, you're right, this is not a war ! we try to find solutions, to propose and test, and to say that for us, partner is different from contact (but can live in same table), and partner is the only one mandatory key you can have on a business object/document. We can be wrong and we can have divergence .. that's opensource :) I've questions, if we (or some other people) want to have clean partner_id and contact_id semantic différence, do you think we can live together with the official version ? Do you think we can have roadmap and documentation of futur new features ? Now, I think you should have say: Partners, community members, strong motivated guys, we decide to implement a new way for managing contact, partner etc .. Here is what we choose at Openerp: - 1 .... - 2..... - .... In X month you will have to check all your modules and modify them to be compatible with the futur version of OpenERP, and you can test it here to validate your modules, customers instance etc .... If you want have editor role, think we have to work together and have small newsletter (technical newsletter, not marketing) to now what will be the futur ... have discution (not war ;) ). For such a big change, I think we must prepare our customer with docs, training, migration cost if needed .. and not after three month of release ? last, if you decide not to include this branch to openERP (it's your right, no problem), I think we will have some modules that will be compatible and some not. Don't know what branch partners prefer to follow, but maybe a survey / vote can be done just to have an idea ? My 2 cents, Nicolas JEUDY Expert Technique et Fonctionnel Système d'Information TUXSERVICES 22 rue du seminaire - 25170 Pelousey e-mail :