Update our tooling to support Odoo 15

[sbidoul]

What needs to be done to create the 15.0 branches

• create OCB 15.0 branch
• update OCB sync script
  • Support odoo 15 #510
• deploy updated OCB sync script
• update click-odoo and click-odoo-contrib (needed to generate .pot files with click-odoo-makepot)
  • CI updated, no change strictly necessary for click-odoo (except to silence a warning)
  • Environment.manage() is a noop in Odoo 15 and emits a Warning acsone/click-odoo#43
  • Support Odoo 15 and update tests to cope with a constantly breaking world... acsone/click-odoo#44
  • Update core addons lists, and add Odoo 15 support acsone/click-odoo-contrib#104
• setuptools-odoo 3.0 - to publish wheels
• manifestoo (used by oca-ci)
• oca-ci - to test with GitHub actions
  • Odoo 15 support and install fixes for Odoo 12 and 13 oca-ci#12
• Update MQT
  • [FIX] fix compatibility with 15.0 PyPI addon naming scheme maintainer-quality-tools#698
  • Use new PyPI package naming scheme for Odoo>=15 maintainer-quality-tools#699
• update addons repo template
  • [IMP] support Odoo 15.0 oca-addons-repo-template#70
  • Test with GitHub actions oca-addons-repo-template#61
• update oca-github-bot
  • Support Odoo 15 oca-github-bot#156
• deploy oca-github-bot
• anything to do on OCA runbot ?
• generate 15.0 branches (oca-create-branch [ADD] oca-create-branch: create branch from a copier template #472 )
• create migration issues (oca-create-migration-issue)
• update weblate deployment Dockerfile to use latest maintainer-tools

[legalsylvain]

• Add 15.0 to the odoo-module-migrator allowed branches. (https://github.com/OCA/odoo-module-migrator)

[sbidoul]

@pedrobaeza @hbrunn @StefanRijnhart to unlock various things depending on it, I pushed odoo/odoo:15.0 to oca/ocb:15.0. Let me know if this is not the right thing to do. Also if one of you feels like updating the ocb sync script in this repo and on the oca server, this is most welcome :)

[pedrobaeza]

Yeah, it's OK to do such initial push, or even do manual pulls since now until we have the sync script. I don't know where such script is hosted and how it works, so I'm afraid I can't help there.

[pedrobaeza]

Any news regarding 15.0 branches creation? People is expectant and asking in several places.

[sbidoul]

It's getting in good shape. We need to merge the two open PR in oca/oca-addons-repo-template and then I'll create the branches later this week, or this week-end.

[pedrobaeza]

Should I review or do anything?

[sbidoul]

I'd like to do a test on one repo before creating all branches. So reviewing and merging and testing oca/oca-addons-repo-template can help.

[feketemihai]

@sbidoul This week there was a branch 15.0 created in l10n-romania, https://github.com/OCA/l10n-romania/tree/15.0, is this intended, should we remove it?

[sbidoul]

@feketemihai this branch seems to be bound to the 14.0 project template, so yes it's better to remove it. I'll create them all in the coming days.

[sbidoul]

Yeah, it's OK to do such initial push, or even do manual pulls since now until we have the sync script. I don't know where such script is hosted and how it works, so I'm afraid I can't help there.

I'm going to deploy the OCB sync script. @pedrobaeza can you confirm that we start fresh with each new branch ? I.e. we don't carry over backports from previous branches ?

[pedrobaeza]

Yes, we always start fresh, and if a backport/patch is still needed in new version, a new PR should be done.

[pedrobaeza]

Out of curiosity, this is the differences between OCB 14.0 and Odoo:

https://github.com/odoo/odoo/compare/14.0..OCA:14.0

(I have pushed today's changes manually for reducing the diff. This snapshot diff will be only valid after each sync)

[sbidoul]

I've tested the new linters on server-tools. The changes should be ok. Most of them are from black removing leading and trailing spaces from docstrings, which means black is stabilizing (good!). And a few minor changes from pyupgrades.

flake8 catches some new things but should be ok for most, we'll see how it goes.

I also ran it on OCA/web. There prettier is doing some more significant changes on js code. Not sure how much of that js code will have to be rewritten for owl though, so it might be less of an issue.

[pedrobaeza]

Thanks for the insights

[sbidoul]

I initialized server-tools 15.0 using #472.

[pedrobaeza]

And what about the rest of the process done by https://github.com/OCA/maintainer-tools/blob/master/tools/migrate_branch_empty.py?

• Migration issue creation
• Milestone creation
• Default branch (if working again)

[sbidoul]

For the migration issue and milestone there is now oca-create-migration-issue. I think we can now decommission migrate-branch and migrate-branch-empty.

For the default branch I'd need to test again. Is it not ok to let each PSC representative change it?

[pedrobaeza]

For the default branch I'd need to test again. Is it not ok to let each PSC representative change it?

In my experience, if I don't tell you about doing it or I do it myself (for the branches I have permissions), repositories languish unchanged.

[sbidoul]

I updated the weblate deployment to pick up 15.0 branches