Hello, I suggest you split the merge proposal in several merge proposals... I see that you have just merged all other branches into this one :) but this will be simpler to have several merge proposals and work each addon at a time, to be sure the work is correctly done. It is simpler to review 10 merge proposals of 100 lines than 1 of 1000.
If you have branches that are dependent of each other (such as depending on crm_base and crm_case), please propose to merge first the base dependencies, then the others. Example : - propose to merge crm_lead, with crm_base and crm_case and lead objects updated - keep your dependent branches updated with your CRM branch to reflect the latest changes - when the CRM branch is validated, propose to merge dependent branches Best regards, Thibault. -- https://code.launchpad.net/~openerp-dev/openobject-addons/trunk-social-jra/+merge/96163 Your team OpenERP R&D Team is subscribed to branch lp:~openerp-dev/openobject-addons/trunk-social-tde. _______________________________________________ Mailing list: https://launchpad.net/~openerp-dev-gtk Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-dev-gtk More help : https://help.launchpad.net/ListHelp
