1. Mailing Lists
  2. Contributors
  3. Re: Server-tools split environment related modules

Contributors mailing list archives

contributors@odoo-community.org

Browse archives

Re: Server-tools split environment related modules

Re: Server-tools split environment related modules

Avatar

Re: Server-tools split environment related modules

by
Tecnativa. S. L., Pedro M. Baeza
- 29/11/2017 14:14:45
Sorry, I didn't cross-compare the links, as mine was the GitHub issue.

Well, I'm not sure if this is too much split and we are going to have a lot of repositories without too much modules. We have never used that modules as we have a Docker infrastructure that doesn't need them, and I have never like the structure with the need of that extra module (server_environment_files), but if you still continue maintaining them, then decide the best strategy.

Regards.

2017-11-29 14:02 GMT+01:00 Yannick Vaucher <yannick.vaucher@camptocamp.com>:
Pedro, I was refering to that split in my message, please see that I linked the same spreadsheet.

Yannick Vaucher
Business Solutions Software Developer

Camptocamp SA
PSE A, CH-1015 Lausanne

On 29 November 2017 at 13:47, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:
Hi, Yannick, there's already a split in progress. See https://github.com/OCA/server-tools/issues/1008. Look if it's enough.

Regards.

2017-11-29 13:32 GMT+01:00 Yannick Vaucher <yannick.vaucher@camptocamp.com>:
Hello,

I'm just looking for other opinions about having specific environment ('dev', 'test', 'qa', 'prod', ...)
modules in it's own project repository.

Here are the modules:

mail_environment
server_env_base_external_referentials
server_environment
server_environment_files_sample
server_environment_ir_config_parameter

What about creating a OCA/server-env project ?

(I propose the short env as it is clear what it means and we already have server-ux which didn't bother anyone)

Here are some PR which were already made for those modules but not merged yet:


It would be the right time to forward them to a new project repository.

Why should we do it ?
- We wanted to split the repo which dragged to many addons as being too generic.
- Environment related addons might grow
- it's a topic on itself

Why we shouldn't?
- we don't want too many repositories
- server-environment is a well know module and has always been in server-tools

(not sure there is a dedicated mailing list for server-* topic)

Yannick Vaucher
Business Solutions Software Developer

Camptocamp SA
PSE A, CH-1015 Lausanne

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


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


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


Reference