Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[MIG][12.0] partner_delivery_schedule: Migration to v12.0 #236

Merged
merged 6 commits into from
Nov 30, 2019

Conversation

sergio-teruel
Copy link
Contributor

@sergio-teruel sergio-teruel commented Nov 28, 2019

cc @Tecnativa TT20121
@ernestotejeda @rafaelbn review please!!

@sergio-teruel sergio-teruel force-pushed the 12.0-mig-partner_delivery_schedule branch from f2eef14 to 1359315 Compare November 28, 2019 20:06
@sergio-teruel sergio-teruel changed the title [WIP][MIG][12.0] partner_delivery_schedule: Migration to v12.0 [MIG][12.0] partner_delivery_schedule: Migration to v12.0 Nov 28, 2019
@sergio-teruel sergio-teruel mentioned this pull request Nov 28, 2019
13 tasks
@pedrobaeza pedrobaeza added this to the 12.0 milestone Nov 28, 2019
@sergio-teruel sergio-teruel force-pushed the 12.0-mig-partner_delivery_schedule branch from 1359315 to d248906 Compare November 29, 2019 11:20
@sergio-teruel
Copy link
Contributor Author

@pedrobaeza Changes done!!

Copy link
Member

@ernestotejeda ernestotejeda left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code review

Copy link
Member

@ernestotejeda ernestotejeda left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe you can implement this later by having in re.partner a Many2one with resource.calendar instead of a Many2many with delivery.schedule and so we will have one less model to worry about and maybe the allow_delivery_date method could be shorter.
If it is not done in the migration of this module it could be done as an improvement later. What do you think ?

@pedrobaeza
Copy link
Member

/ocabot merge

@OCA-git-bot
Copy link
Contributor

On my way to merge this fine PR!
Prepared branch 12.0-ocabot-merge-pr-236-by-pedrobaeza-bump-no, awaiting test results.

OCA-git-bot added a commit that referenced this pull request Nov 30, 2019
Signed-off-by pedrobaeza
@OCA-git-bot OCA-git-bot merged commit d248906 into OCA:12.0 Nov 30, 2019
@OCA-git-bot
Copy link
Contributor

Congratulations, your PR was merged at 2e960f4. Thanks a lot for contributing to OCA. ❤️

This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants