[13.0][MIG] delivery_dropoff_site

[acsonefho]

Migration of the module delivery_dropoff_site (based on open PR #244 about 12.0).

• Use OCA guideline to migrate the module;
• Migrate to 13.0;
• Use api.model_create_multi when possible;
• Use new super() syntax;
• No error/warning during install;
• pre-commit.

[rousseldenis]

@acsonefho Can you fix runbot warning? It's about model _description missing field

[rousseldenis]

@acsonefho Please check https://runbot2.odoo-community.org/runbot/static/build/3436478-281-091d3e/logs/job_20_test_all.txt

Warning at the end about two fields having the same label.

2020-08-24 08:50:53,499 158 WARNING openerp_test odoo.addons.base.models.ir_model: Two fields (property_delivery_carrier_id, carrier_id) of dropoff.site() have the same label: Delivery Method.

[ThomasBinsfeld]

@rousseldenis Warning should be fixed

[rousseldenis]

@acsonefho Could you rebase ?

[rousseldenis]

@acsonefho

[github-actions]

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

[flotho]

ping @vincent-mundo @gaelTorrecillas @MalikaBelmokhtar please could you review this to prepare v14 migration

[flotho]

ping @BechirAouji
A Review is also expected from you .

[flotho]

hi @acsonefho @pedrobaeza @sbidoul , how is it possible to force a runBOAT execution for this one?

Regards

[flotho]

Hi @acsonefho any chance to update your unit tests?
Do you have time for this?

[acsonefho]

Hi @acsonefho any chance to update your unit tests? Do you have time for this?

Hi @flotho I don't have time today and I'm off during a couple of week so don't hesitate to do it.

[sbidoul]

@flotho normally triggering a build is done by pushing a commit.

In exceptional situation, it is doable also via https://runboat.odoo-community.org/docs, but you need a login - which I'd be happy to share with regular contributors, I just don't have a convenient way to do it. So I just triggered the build for this PR.

[github-actions]

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.