-
-
Notifications
You must be signed in to change notification settings - Fork 785
[MIG] Bootstrapping 16.0 + analysis #3583
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
Conversation
1e2e8c5 to
971a8bb
Compare
|
@pedrobaeza thanks for challenging the branch setup. Nothing that could not be fixed with a And look at that clean history: https://github.com/OCA/Openupgrade/commits/16.0 |
|
|
13efb88 to
1e3255b
Compare
1e3255b to
1999340
Compare
| } | ||
|
|
||
| # only used here for upgrade_analysis | ||
| renamed_models = { |
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.
The analysis has to be re-run if renamed models are found. Do you know if there's any right now?
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.
No, not aware of any.
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.
The re-run will have to be done few months later, anyway.
| .. |badge3| image:: https://img.shields.io/badge/github-OCA%2FOpenUpgrade-lightgray.png?logo=github | ||
| :target: https://github.com/OCA/OpenUpgrade/tree/16.0/openupgrade_scripts | ||
| :alt: OCA/OpenUpgrade | ||
| .. |badge3| image:: https://img.shields.io/badge/github-OCA%2Fopenupgrade-lightgray.png?logo=github |
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.
Why changing uppercase?
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.
Oh I did not pay any attention to the casing when I ran oca-gen-addon-readme. I didn't know it mattered, and I'm still slightly annoyed the project name has to be passed on the command line 😛
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.
It's for reducing the diff essentially, and yes, you need to introduce it, as it can't be deduced from the folder itself.
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.
Couldn't we introduce a .oca-project-name file in the root of the addons directory?
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.
That's a good idea, but it should be proposed at maintainer-tools, and maybe harmonize it with ocaport hidden directory (not sure if it's .oca), and also bootstrap it through the copier template.
Feyensv
left a comment
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.
Only curiously looking at the analysis of the modules in my team's scope :3
Giving some information on the way to help the upgrades ;).
(really nice work to detect all those changes automatically, it's a great tool 👍)
| obsolete model payment.acquirer | ||
| obsolete model payment.acquirer.onboarding.wizard [transient] | ||
| model payment.refund.wizard (moved to account_payment) [transient] | ||
| new model payment.provider | ||
| new model payment.provider.onboarding.wizard [transient] |
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.
FYI those two changes are model rename (acquirer -> provider)
will probably simplify the upgrade analysis ;)
(Applies to view & other records xml ids as well, in payment(_*) modules, we replaced all occurrences of acquirer)
| obsolete model sale.payment.acquirer.onboarding.wizard [transient] | ||
| new model sale.payment.provider.onboarding.wizard [transient] |
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.
model renaming
|
Thank you for taking a look, Victor! @StefanRijnhart it seems we have our first renamed models to include and re-run analysis. |
|
Hi, Is there anything blocking that PR? I have updated https://oca-cm-15.komit.link to take into account v16.0 and currently it does not reflect the real situation without this PR being merged. |
|
Please merge this and someone can follow up with a new analysis. My computer is still smoking from all the analysis runs I did for this PR. |
|
OK, merging blindly |
|
The model renamings mentioned by Victor are still pending. |
Continued from #3582, after rebuilding the 16.0 branch without docs, openupgrade_framework and the scripts from openupgrade_scripts.
Added some documentation to https://github.com/OCA/OpenUpgrade/wiki/Set-up-the-branch-for-a-new-Odoo-release.
Also slightly updated: