Update our tooling to support Odoo 18.0

[sbidoul]

Improvements we may want to do

• Add mechanism to fail on WARNING messages in Odoo test log oca-ci#10
• pre-commit/mirrors-prettier has been archived oca-addons-repo-template#264, find an alternative
• Improve xml prettyfier oca-addons-repo-template#224
• review pylint-odoo and odoo-pre-commit-hooks configs oca-addons-repo-template#270

---

See #582 for links to similar PRs for 17.0.

• determine Python version to use in CI and whool (via manifestoo-core)
• determine Postgres version to use in CI
• prepare migration wiki page, using as reference https://github.com/odoo/documentation/blob/master/content/developer/reference/backend/orm/changelog.rst - @pedrobaeza
• create OCB 18.0 branch - @pedrobaeza
• set OCB 18.0 branch as default - @simahawk Add branch 18.0 [WAIT FOR MERGE] repo-maintainer-conf#36
• Change OCB README to OCB one (after Odoo finishes doing changes there) - @pedrobaeza
• update OCB sync script - @pedrobaeza
• deploy updated OCB sync script - @sbidoul
• make sure click-odoo-makepot works with Odoo 18
• add Odoo 18 support to manifestoo-core (used by oca-ci via manifestoo, and whool) - @sbidoul Add Odoo 18 support acsone/manifestoo-core#81
• update manifestoo-core core addons list
• request new PyPI classifier - @sbidoul Add Odoo 18 trove classifier pypa/trove-classifiers#187
• oca-ci
• update addons repo template
• update oca-github-bot if needed
• restart oca-github-bot to pick-up latest build tools
• update runboat config - @sbidoul
• generate 18.0 branches - @simahawk Add branch 18.0 [WAIT FOR MERGE] repo-maintainer-conf#36
• create migration issues (oca-create-migration-issue, don't forget to use a bot token not yours)
• update weblate deployment Dockerfile to use latest maintainer-tools
• deploy weblate
• in OCA Odoo Instance, add the new series in GitHub > GitHub Comunity > Organizations > OCA.
• create 18.0 OpenUpgrade branch - @pedrobaeza
• create branches on apps.odoo.com

[simahawk]

generate 18.0 branches (oca-create-branch), using the bot account

I'd rather add another tool on https://github.com/OCA/repo-maintainer as we need to add a branch to all repos of https://github.com/OCA/repo-maintainer-conf.

I could have a look at that. Then we can trash oca-create-branch IMO, unless you see any reason to keep it.

[pedrobaeza]

I have assigned to me the OCB first part and the OpenUpgrade one.

[simahawk]

set OCB 18.0 branch as default

same for this -> we must use the repo-maintainer. I'll include an option in the new tool mentioned above.

@pedrobaeza I take over this one if ok for you

[legalsylvain]

Hi @sbidoul. Thanks for enumerating all the tasks to do.
The majority of tasks cannot be performed, as version 18.0 has not been released but as soon as 18.0 is released, we can go forward.
The last year, the release was done october 26, 2023 : (odoo/odoo@dd05f0a) 13 days before the Odoo days. (8 - 10 November 2023)

[sbidoul]

@simahawk feel free to give it a try. For oca-create-branch I used this PR last time: #541 which tries to preserve some copier answer from previous branch (not all, as we use different more modern defaults each year).

[pedrobaeza]

@simahawk OK

@legalsylvain I predict this year the date will be more constrained, as they still have some big things to merge (for example, company dependent fields to JSON - let's hope it enters this version -), but maybe they still create the branch on advance even if not completed as a favor to the community.

[sbidoul]

@legalsylvain it's true some tasks can't be done yet. PRs can be prepared, though.

But more importantly there are the improvements mentioned at the beginning that can be worked on if we want to address them.

[simahawk]

@simahawk feel free to give it a try. For oca-create-branch I used this PR last time: #541 which tries to preserve some copier answer from previous branch (not all, as we use different more modern defaults each year).

hmm the repo-maintainer will bootstrap the branch w/o that tool. We have to find a different way likely. I'll have a look, thanks for the pointer.

[simahawk]

@simahawk feel free to give it a try. For oca-create-branch I used this PR last time: #541 which tries to preserve some copier answer from previous branch (not all, as we use different more modern defaults each year).

hmm the repo-maintainer will bootstrap the branch w/o that tool. We have to find a different way likely. I'll have a look, thanks for the pointer.

I had a look at your work but I think we don't need it anymore. Please see #541 (comment)
If that's correct, here we have the new tool to manage branches and here the result for v18

[pedrobaeza]

I have added a point for the migration guide.

[sbidoul]

I have added a point for the migration guide.

@pedrobaeza was that not the third item already?

[pedrobaeza]

Ouch, I didn't see it...

[PabloEForgeFlow]

Hello, I was wondering if I could contribute somehow, perhaps one of the improvements mentioned above. I looked through OCA/oca-ci#10 and I think I could do that, if nobody's working on it currently.

[sbidoul]

Hello, I was wondering if I could contribute somehow, perhaps one of the improvements mentioned above. I looked through OCA/oca-ci#10 and I think I could do that, if nobody's working on it currently.

@PabloEForgeFlow cool, that is most welcome. Just checking if @rousseldenis was not planning to do the same.

[rousseldenis]

Hello, I was wondering if I could contribute somehow, perhaps one of the improvements mentioned above. I looked through OCA/oca-ci#10 and I think I could do that, if nobody's working on it currently.

@PabloEForgeFlow cool, that is most welcome. Just checking if @rousseldenis was not planning to do the same.

@PabloEForgeFlow You can do it as the solution proposed is simpler than mine.

Ping me if you want review.

[PabloEForgeFlow]

Great I'll be working on it then, thanks @sbidoul @rousseldenis.

[PabloEForgeFlow]

Hey @sbidoul @rousseldenis , I've implemented a first version of OCA/oca-ci#10 in OCA/oca-ci#77, let me know what you think.