Skip to content

Prepare our tooling for odoo v20 #683

Open

Description

@etobella

One week until Odoo 20. I'm opening this so we can start preparing.

Tasls for previous versions for reference: #658 #628

Improvements we may want to do

...


Activity

  1. feketemihai commented on Sep 17, 2026

    @feketemihai
    Member

    I created acsone/click-odoo-contrib#189 for make sure [click-odoo-makepot] works with Odoo 20:

  2. feketemihai commented on Sep 17, 2026

    @feketemihai
    Member

    acsone/manifestoo-core#149 for add Odoo 20 support to manifestoo-core

  3. feketemihai commented on Sep 17, 2026

    @feketemihai
    Member

    tested also

    make pylint-odoo supports Odoo 20
    make sure odoo-pre-commit-hooks supports Odoo 20

    both working as expected also for 20.0

  4. feketemihai commented on Sep 17, 2026

    @feketemihai
    Member
  5. etobella commented on Sep 18, 2026

    @etobella
    MemberAuthor

    @sbidoul We need to add a new release of manifestoo_core. Can you handle it?

  6. hbrunn commented on Sep 18, 2026

    @hbrunn
    Member

    note that openupgrade doesn't need anything specific any more, this now behaves like a normal oca repo

  7. etobella commented on Sep 19, 2026

    @etobella
    MemberAuthor

    Thanks @hbrunn I removed it from the list.

    Also, there is parts that might not be necessary, like the create version in OCA instance, as it should be done automatically

  8. added a commit that references this issue on Sep 21, 2026
  9. rousseldenis commented on Sep 22, 2026

    @rousseldenis
    SponsorContributor

    @sbidoul We need to add a new release of manifestoo_core. Can you handle it?

    @etobella I see the latest version has 20.0 series

  10. rousseldenis commented on Sep 23, 2026

    @rousseldenis
    SponsorContributor

    pylint-odoo seems to wrok correctly with 20.0. Tested locally

  11. sbidoul commented on Sep 24, 2026

    @sbidoul
    Member

    Next step in OCA/oca-ci#132.

  12. etobella commented on Sep 24, 2026

    @etobella
    MemberAuthor

    I Also prepared the PR to add all 20.0 branches

  13. sbidoul commented on Sep 26, 2026

    @sbidoul
    Member

    runboat and click-odoo-makepot should be ready

  14. etobella commented on Sep 27, 2026

    @etobella
    MemberAuthor

    @sbidoul shall we merge the branches?

    about the issues, can you create it with the oca bot?

  15. rousseldenis commented on Sep 30, 2026

    @rousseldenis
    SponsorContributor

    @etobella Is it possible to run the oca-create-migration-issue script as a lot of migration PR's are already created? 😅

  16. 4 remaining items

  17. simahawk commented on Oct 5, 2026

    @simahawk
    Contributor

    It should be feasible for any core maintainer 😉
    I'm having a look at it.

  18. pedrobaeza commented on Oct 5, 2026

    @pedrobaeza
    Member

    Really? I don't have access to "Settings" option at OCA org level for that AFAIK.

  19. simahawk commented on Oct 5, 2026

    @simahawk
    Contributor

    It's running...

  20. pedrobaeza commented on Oct 5, 2026

    @pedrobaeza
    Member

    Well, it's running with your identity, which we didn't want to. Now you'll be pinged everywhere... That's why we were asking for a token with the OCA bot.

  21. simahawk commented on Oct 5, 2026

    @simahawk
    Contributor

    Dang! I forgot the little part about "don't forget to use a bot token not yours" 🤣
    I'll keep you posted! 😅

  22. simahawk commented on Oct 5, 2026

    @simahawk
    Contributor

    Bah, I cannot find that access, I deleted "my" issues. I'll see if we can do something w/ repo-maintainer: how do you see if we get this automatically when bootstrapping the new branch?

  23. bguillot commented on Oct 5, 2026

    @bguillot

    Hello @simahawk, I managed to log into the gitbot account

  24. etobella commented on Oct 5, 2026

    @etobella
    MemberAuthor

    @bguillot can you try to generate the issues 🙏 ?

  25. bguillot commented on Oct 5, 2026

    @bguillot

    yes I'm on it !

  26. bguillot commented on Oct 5, 2026

    @bguillot

    the script is running

  27. simahawk commented on Oct 5, 2026

    @simahawk
    Contributor

    For next year: OCA/repo-maintainer#31 (reviews welcomed)

  28. pedrobaeza commented on Oct 8, 2026

    @pedrobaeza
    Member

    According OCA/server-env#307 (comment), the Python version used in runbot is 3.14, so we should align runboat with that one for not having different results due to the version mismatch.

  29. sbidoul commented on Oct 15, 2026

    @sbidoul
    Member

    31. According OCA/server-env#307 (comment), the Python version used in runbot is 3.14, so we should align runboat with that one for not having different results due to the version mismatch.

    I think we should continue testing with the minimum supported Python version.

    Since we test with odoo and OCB, we could consider doing one with 3.12 and the other with 3.14.

    Regarding runboat, if tests pass on both versions, it should not make a difference whether it runs 3.12 and 3.14, right?

  30. pedrobaeza commented on Oct 15, 2026

    @pedrobaeza
    Member

    Ok to test one with 3.12 and the other with 3.14, but we can't allow not testing in the one where runbot does the core tests.

  31. sbidoul commented on Oct 16, 2026

    @sbidoul
    Member

    I'll be happy to review a PR to oca/oca-addons-repo-template adding a copier question to select the test image for the odoo and OCB tests (with backward compatible defaults). I don't think this "problem" is new, though. I believe for 19 Odoo's runbot was running python 3.12, while OCA tests run 3.10.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions