Contributors mailing list archives
RE: Split OCA website repository into website and website_saleby
website_sale and ecommerce, same purpose only one project :+1
We must take care when merging modules. If a modules add or modify functionality in website_sale it must be in ecommerce and not in website.
About moving modules, Alexandre, maybe now we can do it (there are 4 modules to move), but in one month will be totally impossible.
We have already in production that modules but I think we can manage this in this moment.
Antiun Ingeniería S.L.
Camino del Pocito de San Roque, 30
28231 Las Rozas de Madrid
+34 91 710 35 29
+34 675 84 83 64
Enviado desde Antiun Telecomunicaciones | Sent from Telecom Antiun
De: Alexandre Fayolle [mailto:firstname.lastname@example.org]
Enviado el: viernes, 14 de agosto de 2015 15:53
Para: OCA Contributors
Asunto: Re: Split OCA website repository into website and website_sale
On 14/08/2015 12:52, Leonardo "LeartS" Donelli wrote:
> Hi all!
> The OCA/website repository already contains 16 modules of which 4 are
> actually ecommerce (website_sale) modules.
> There are 22 PR for new modules, of which 6 are modules for the ecommerce.
> Assuming all get merged, this would result in a repo with 38 modules.
> By splitting the repo into OCA/website and OCA/website_sale, they
> would have respectively 28 and 10 modules, which would make it simpler
> to manage and to find the modules you're looking for.
I'm :-1: on this proposal.
We have servers in productions, using these projects, and moving modules
around is a real pain when you upgrade the versions on these servers.
What should be a simple operation becomes a nightmare when you have to
hunt down the new repositories in which the modules have moved.
Chef de Projet
Tel : +33 4 58 48 20 30
Camptocamp France SAS
Savoie Technolac, BP 352
73377 Le Bourget du Lac Cedex
Post to: mailto:email@example.com