Contributors mailing list archives
Re: Split OCA website repository into website and website_saleby
TAKOBI s.r.l., Lorenzo Battistini.
On 14 August 2015 at 14:22, Leonardo Pistone <email@example.com> wrote:
On Fri, Aug 14, 2015 at 2:08 PM, Miku Laitinen <firstname.lastname@example.org> wrote: > One argument for keeping modules in their own repos is that they can be used > as git submodules. If all the modules are in the same repository, you have > to 1. download all of them as a submodule, even if you need just one module, > and 2. modify the odoo configuration file to include the directory as an > addons path. +1 there are more important points: that would allow us to tag the repo with the module version, avoid custom merge-ins of open PRs with the buildout merge-in feature, easy transfer of ownership without git-fu and maybe reconsider making pip packages from every module. We'll see what happens when we'll start working on v9. Also, please note that to split repos in two or other rearrangements, we need to rewrite the git history of all repos involved, which I'd like to avoid. Also, we'll brake all existing projects (i.e. buildouts that pull modules from repos at specific hashes).
I think the history of stable branches should never be rewritten.
In case we decided to move website_sale_* module to ecommerce repo, they should just be moved.