Merge lp://qastaging/~savoirfairelinux-openerp/partner-contact-management/partner-contact-management-base_contact_add_modules into lp://qastaging/~partner-contact-core-editors/partner-contact-management/7.0
Status: | Needs review |
---|---|
Proposed branch: | lp://qastaging/~savoirfairelinux-openerp/partner-contact-management/partner-contact-management-base_contact_add_modules |
Merge into: | lp://qastaging/~partner-contact-core-editors/partner-contact-management/7.0 |
Diff against target: |
2416 lines (+2295/-0) 23 files modified
base_contact_by_functions/__init__.py (+27/-0) base_contact_by_functions/__openerp__.py (+56/-0) base_contact_by_functions/functions.py (+41/-0) base_contact_by_functions/functions_view.xml (+38/-0) base_contact_by_functions/i18n/base_contact_by_functions.pot (+353/-0) base_contact_by_functions/i18n/fr.po (+353/-0) base_contact_by_functions/res_institutions.py (+49/-0) base_contact_by_functions/res_institutions_view.xml (+55/-0) base_contact_by_functions/res_partner.py (+102/-0) base_contact_by_functions/res_partner_view.xml (+526/-0) base_contact_by_functions/security/ir.model.access.csv (+5/-0) base_contact_by_functions/tests/__init__.py (+31/-0) base_contact_by_functions/tests/test_functions.py (+98/-0) base_contact_by_functions/tests/test_institutions.py (+99/-0) base_contact_by_functions/tests/test_partner_category.py (+105/-0) base_contact_by_functions_partner_firstname/__init__.py (+25/-0) base_contact_by_functions_partner_firstname/__openerp__.py (+53/-0) base_contact_by_functions_partner_firstname/i18n/base_contact_by_functions_partner_firstname.pot (+27/-0) base_contact_by_functions_partner_firstname/i18n/fr.po (+27/-0) base_contact_by_functions_partner_firstname/res_partner.py (+76/-0) base_contact_by_functions_partner_firstname/res_partner_view.xml (+71/-0) base_contact_by_functions_partner_firstname/tests/__init__.py (+27/-0) base_contact_by_functions_partner_firstname/tests/test_partner.py (+51/-0) |
To merge this branch: | bzr merge lp://qastaging/~savoirfairelinux-openerp/partner-contact-management/partner-contact-management-base_contact_add_modules |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Lorenzo Battistini (community) | Needs Resubmitting | ||
Stefan Rijnhart (Opener) | Needs Information | ||
Sandy Carter (http://www.savoirfairelinux.com) | Abstain | ||
Review via email: mp+217775@code.qastaging.launchpad.net |
This proposal supersedes a proposal from 2014-01-30.
Description of the change
- [ADD] added base_contact_
- [ADD] Added base_contact_
The base_contact_
Unmerged revisions
- 46. By Sandy Carter (http://www.savoirfairelinux.com)
-
Fix KeyError which sometimes arises when installing modules.
Assert that contact_id exists in vals
- 45. By Sandy Carter (http://www.savoirfairelinux.com)
-
Fix error when creating partner with contact info
- 44. By Sandy Carter (http://www.savoirfairelinux.com)
-
adapt module for community firstname module
- 43. By El Hadji Dem (http://www.savoirfairelinux.com)
-
[IMP] is_company field is True by default and replace Organism by Parent Organism in form view
- 42. By El Hadji Dem (http://www.savoirfairelinux.com)
-
[ADD] added base_contact_
by_functions_ partner_ firstname module: It allows to add firstname before name.Name is considered like the lastname and we have firstname and lastname on partner view and contact view. - 41. By El Hadji Dem (http://www.savoirfairelinux.com)
-
[ADD] added base_contact_
by_functions module: It allow to manage contacts by function
I have a hard time trying to find out what this module actually does. The manifest description is very terse. The name of the module reminds me of base_contact, which allowed multiple connections between the same person and a company. Is this module similar? The description should at least explain what 'institutions' are (a concept that this module introduces).
Terminology is off at times, it seems. l.130: 'acronym': is this abbreviation, or maybe stick to the standard 'code' field name and label?
Organism: I'm guessing you mean organization. But in any case, changing the 'company' terminology should be split off as a separate module.
The translations seem to contain obsolete terms, e.g. l.241 and other occurrences of 'passport'.