Skip to Content
  2. Mailing Lists
  3. Contributors
  4. Re: Migration 12.0 -> 14.0

Archives

Contributors

Re: Migration 12.0 -> 14.0

Re: Migration 12.0 -> 14.0

With https://github.com/OCA/oca-github-bot/pull/97, we try to achieve such thing.

Regards.
by Pedro M. Baeza - 10:51 - 2 Sep 2021

Reference

  • Migration 12.0 -> 14.0
    Hello everyone,

    Is it allowed to create a PR for a module migration that bypasses 13.0 ?
    Yann PAPOUIN
    Ingénieur R&D | DEC

    A ZAC du Monné 3 r Champ du Verger 72700 ALLONNES
    T 02 43 21 65 50 ext 51  ­ F 02 43 39 30 78  ­ E ypa@decgroupe.com ­ W www.decgroupe.com ­
    by Yann Papouin - 10:26 - 31 Aug 2021

    5 replies 5 replies

    • Re: Migration 12.0 -> 14.0
      With https://github.com/OCA/oca-github-bot/pull/97, we try to achieve such thing.

      Regards.
      by Pedro M. Baeza - 10:51 - 2 Sep 2021
    • Re: Migration 12.0 -> 14.0
      Oh, I don't pretend to make a such request 😅
      I thought that Github was able to give enough fine control to create a "Moderator" group across all OCA's modules projects to include users that would be able to edit issues or tag PRs with labels.

      I don't have any knowledge on Github bots, but would it be possible to have specific commands that would add/update the task list for Issues named like "Migration to version xxx" ?

      Analyse the current task list and update the check status based on the linked PR
      /ocabot migration-issue

      Add a module to the task list:
      /ocabot migration-issue module_name

      Add/edit a module to/from the task list and link it with a PR:
      /ocabot migration-issue module_name #123

      Add/edit a module to/from the task list and add/edit a comment:
      /ocabot migration-issue module_name "Merged with another_module"
      /ocabot migration-issue module_name "Move to OCA/another_repo"

      --
      Yann PAPOUIN, Ingénieur R&D | DEC


      Le mar. 31 août 2021 à 15:37, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> a écrit :
      Well, for having such permission you need to be PSC of the area of the repository. You can propose yourself in this list if you think you have enough contributions for such place. More information at https://odoo-community.org/page/oca-project-steering-committee-guide

      Regards.

      _______________________________________________
      Mailing-List: https://odoo-community.org/groups/contributors-15
      Post to: mailto:contributors@odoo-community.org
      Unsubscribe: https://odoo-community.org/groups?unsubscribe

      by Yann Papouin - 02:40 - 1 Sep 2021
    • Re: Migration 12.0 -> 14.0
      Well, for having such permission you need to be PSC of the area of the repository. You can propose yourself in this list if you think you have enough contributions for such place. More information at https://odoo-community.org/page/oca-project-steering-committee-guide

      Regards.
      by Pedro M. Baeza - 03:35 - 31 Aug 2021
    • Re: Migration 12.0 -> 14.0
      Thank you, that's good news.

      I've started an audit on our database to know current OCA module migration status before starting on it.
      This is really complicated (long task in fact) as for each module, you need to know the github repo and find the "Migration to version 1x.0" issue, and this one is not always updated with the latest comments.
      To help the community, is there a way to give me write access to the main topic to edit/update the task list ?

      --
      Yann PAPOUIN, Ingénieur R&D | DEC


      Le mar. 31 août 2021 à 10:31, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> a écrit :
      Yes, that's possible while respecting commit history. If the 13.0 version ever needed, it can be backported from 14.0, or migrated from 12.0 again.

      Regards.

      _______________________________________________
      Mailing-List: https://odoo-community.org/groups/contributors-15
      Post to: mailto:contributors@odoo-community.org
      Unsubscribe: https://odoo-community.org/groups?unsubscribe

      by Yann Papouin - 02:21 - 31 Aug 2021
    • Re: Migration 12.0 -> 14.0
      Yes, that's possible while respecting commit history. If the 13.0 version ever needed, it can be backported from 14.0, or migrated from 12.0 again.

      Regards.
      by Pedro M. Baeza - 10:30 - 31 Aug 2021