-
-
Notifications
You must be signed in to change notification settings - Fork 31
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
[14.0] Add Missing Changes from v12 #51
base: 14.0
Are you sure you want to change the base?
Conversation
5a2a110
to
1dffc34
Compare
…ration from v12 to v14
1dffc34
to
0556209
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good job! LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks all good and reasonable to me.
@yweng8111 I think this is not correct as you should keep commits as is and not changing them. |
I encourage you to use this great tool: https://github.com/OCA/oca-port |
This PR has the |
@rousseldenis
|
And what is the issue ? The problem is about authorship and history. With this approach, both branches will be more asynchronous from each other. We should avoid such problems. Ideally, I would say you should first do a PR per module. This is the best approach to decouple the lever for review/approvals and fast merges. |
The problem is that we simply do not have time to do it the way you suggest. I'm afraid it won't be done at all then. |
During the migration of the modules (v12 -> v14) we have made some changes that are not contained in the actual code of 14.0