1. Mailing Lists
  2. Contributors
  3. Re: Move purchase_request* and purchase_work_acceptance*

Contributors mailing list archives

contributors@odoo-community.org

Browse archives

Re: Move purchase_request* and purchase_work_acceptance*

Re: Move purchase_request* and purchase_work_acceptance*

Avatar

Re: Move purchase_request* and purchase_work_acceptance*

by
ForgeFlow, S.L., Lois Rilo Antelo
- 21/12/2021 11:43:27
Hi,

I don't have a strong opinion on this one, if you want to split purchase-workflow, I'm fine with that.

For me the real problem, and to bring another consideration to the table, are the repos with "rebel" addons that forces you to have multiple pipelines with some addons excluded and other with them included, it happens often that a contributor ends having to fix other modules tests when you opening a new PR of a new module. This happens in purchase-workflow but also in sale-workflow.

Regards,

El mar, 21 dic 2021 a las 11:27, Pedro M. Baeza (Tecnativa) (<pedro.baeza@tecnativa.com>) escribió:
Now that having a lot of runboat instances is not too much of a problem, I think it's better to split the maximum repos for smaller sets of modules, so I will go to all of them that we are talking about. Reducing the number of them will:

- Avoid potential conflicts between them.
- Reduce tests size.

On the contrary, it makes the ecosystem a bit more complicated, and gets people used to look to other places. When we unfolded OCA/hr into several repos, including OCA/hr-holidays and OCA/hr-expense, some people still created PRs to migrate one module that is already migrated, but on the other repo. But the problem here is that people don't look, and it happens constantly, not only with this, so no big deal.

Regards.

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



--
Lois Rilo Antelo
Odoo consultant at ForgeFlow S.L.

Reference