Skip to content

Migration to version 18.0 #4519

Open
Open

Description

@legalsylvain

Full list of modules available here : https://github.com/OCA/OpenUpgrade/blob/18.0/docsource/modules170-180.rst

Pending / done work

Merged modules

Activity

  1. added this to the 18.0 milestone on Jul 16, 2024
  2. pinned this issue on Oct 25, 2024
  3. hbrunn commented on Jan 6, 2025

    @hbrunn
    Member

    I've worked on openupgrade_framework and the base module today, will probably push something testable next week.

    I'm also looking into generating the analysis files automatically in a cronjob so that we always have the latest analysis on github without human intervention.

  4. legalsylvain commented on Jan 7, 2025

    @legalsylvain
    ContributorAuthor

    I've worked on openupgrade_framework and the base module today, will probably push something testable next week.

    Nice ! I added a Version column in the main followup document.

    I'm also looking into generating the analysis files automatically in a cronjob so that we always have the latest analysis on github without human intervention.

    interested. Created a dedicated issue to talk about that : #4707

  5. added
    no staleUse this label to prevent the automated stale action from closing this PR/Issue.
    on Feb 6, 2025
  6. chmuche commented on Feb 19, 2025

    @chmuche

    Hello,

    Thank you for your work.
    One of our customers in Community Edition wants to migrate to v18.
    We use only account + l10n_fr and uom.

    Do you have an estimate date of release v18 script for these 2 modules?

    I don't know the governance in this repository.

    Only account seems to have big changes (after looking is the analysis #4740)
    Thanks

  7. hbrunn commented on Feb 19, 2025

    @hbrunn
    Member

    you can start contributing by reviewing the existing open PRs for v18, which are all prerequisites for the account migration

  8. changed the title [-] Migration to version 18.0[/-] [+]Migration to version 18.0[/+] on Mar 6, 2025
  9. hbrunn commented on Sep 4, 2025

    @hbrunn
    Member

    @OCA/openupgrade-maintainers given this is pretty mature by now, should we shift the default branch to 18.0?

  10. pedrobaeza commented on Sep 4, 2025

    @pedrobaeza
    Member

    Yes!

  11. yoanyr commented on Oct 20, 2025

    @yoanyr
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

    enhancementno staleUse this label to prevent the automated stale action from closing this PR/Issue.

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions