You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For humans: I need an easy way to find existance of known module for each versions.
For machines:
Keep track of what module are available now.
Be able to generate part of openupgrade/apriori.py automatically
One of my long term goal, is to be able to know for a given project in one version, what modules need to be ported.
Non goals:
show dependency paths
manage module versions
Describe the solution you'd like
I would like oca-github-bot to automatically publish to a dedicated repo, when a module merged.
The information stored will be: {odoo version}, { module name }, {org = OCA}, { repo }
In case of module move to another repo, merged to another module, split between modules, the infromation will be {odoo version}, { module name }, {org = OCA}, { repo }, { org = OCA }, { repo in previous version }, { module name in previous version }.
This require #317 and it will make a stone with two shots kill two birds with one stone.
Describe alternatives you've considered
Pypi: look if a module is in pypi works only if org = oca.
OCA app store: do not work for different org.
Additional context
Add any other context about the feature request here.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem?
For humans: I need an easy way to find existance of known module for each versions.
For machines:
One of my long term goal, is to be able to know for a given project in one version, what modules need to be ported.
Non goals:
Describe the solution you'd like
I would like oca-github-bot to automatically publish to a dedicated repo, when a module merged.
The information stored will be: {odoo version}, { module name }, {org = OCA}, { repo }
In case of module move to another repo, merged to another module, split between modules, the infromation will be {odoo version}, { module name }, {org = OCA}, { repo }, { org = OCA }, { repo in previous version }, { module name in previous version }.
This require #317 and it will
make a stone with two shotskill two birds with one stone.Describe alternatives you've considered
Pypi: look if a module is in pypi works only if org = oca.
OCA app store: do not work for different org.
Additional context
Add any other context about the feature request here.
The text was updated successfully, but these errors were encountered: