Because an error prevent creation of res.partner records in the tests due the
'mail' addon adding a required 'notification_email_send' field. This addon does
not depend on 'mail' so the test violates the not-null constraint.
The tests are passing in the normal builds anyway.
The company was mandatory and prevented to use the module for models without
company_id. Also, there is currently no use case for a different configuration
for different companies. It simplifies the setup too.
If a use case exists for a different setup per company, it can be reintroduced
later with a optional company_id.
From rusty_record_reaper_runner to record_archiver.
Not that I dislike the old funny name, but I guess it will be easier to get
what it does with the new (maybe too serious) name.
Follow OCA/maintainer-quality-tools#187 and use addons/apt/package directive to
install our build dependencies. This allows using container based Travis builds
(which should be faster).
With module admin_technical_features installed, base_import unittests fail with
in the following test:
test_shallow (openerp.addons.base_import.tests.test_cases.test_o2m)
Having technical features enabled add the following to the dict in
fields:
{'fields': [{'fields': [],
'id': 'parent_id',
'name': 'id',
'required': False,
'string': 'External ID'},
{'fields': [],
'id': 'parent_id',
'name': '.id',
'required': False,
'string': 'Database ID'}],
'id': 'parent_id',
'name': 'parent_id',
'required': False,
'string': 'unknown'}
In order to get visibility on https://www.odoo.com/apps the OCA board has
decided to add the OCA as author of all the addons maintained as part of the
association.