1. Mailing Lists
  2. Contributors
  3. Re: Is a new hidden folder '.oca/' in OCA repositories acceptable?

Contributors mailing list archives

contributors@odoo-community.org

Browse archives

Re: Is a new hidden folder '.oca/' in OCA repositories acceptable?

Avatar

Re: Is a new hidden folder '.oca/' in OCA repositories acceptable?

by
Camptocamp France SAS, Sébastien Alix
- 12/10/2022 10:02:19 
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 

> ....

Reference