Archives
Contributors
Re: Is a new hidden folder '.oca/' in OCA repositories acceptable?
I like the idea, so that means: - for module migration, we add a 'deprecated' flag for the earlier version/branch (not the target one as it's done now), but do we need to blacklist a migration from 15.0 to 14.0 or it's not necessary? - for blacklisted PRs, we still need to add a metadata on the target branch Le 12/10/2022 à 07:22, Mignon, Laurent a écrit : > What about a new 'deprecated' entry into the __manifest__.py file? > To specify/announce that an addon should not be migrated in version > 'n', we would add in version 'n-1' a 'deprecated' entry into the > manifest where the value explains why the addon is deprecated. > In this way, this kind of information could also be used by > other tools like the gen_addon_table to highlight such addons and > explain why in a structured way. In the same way, the gen_addo_readme > could also use this information to add a warning into the addon readme > ....
by Sébastien Alix - 10:06 - 12 Oct 2022
Reference
-
Is a new hidden folder '.oca/' in OCA repositories acceptable?
Hi everyone, While working on a new feature of 'oca-port' (https://github.com/OCA/oca-port/pull/7), I would like to store some data in the git repository so they are shared between all contributors using this tool. Here it is about blacklisting some migrations (with a comment), so another contributor who try to port a module/PR will get warned that it has been blacklisted (and why) for a given branch. This new '.oca' hidden folder could host files for any kind of OCA tools in the future, but before going further I would like to know if it's something you are comfortable with? -- Sébastien Alix Business Solutions Odoo Developer Camptocamp France SA https://www.camptocamp.com/
by Sébastien Alix - 01:50 - 10 Oct 2022