Community mailing list archives
Re: OCA project: __unported__ folder considered painfulby
- Intranusa - ( Temporary )
Nice say pedro :) But, will be wasting everybody's time now for the better & easier in the next version, perhaps a better option.
On Mar 11, 2015 9:57 PM, "Pedro Manuel Baeza Romero" <firstname.lastname@example.org> wrote:
Well, say then that I don't like that option ;)Regards.2015-03-11 15:48 GMT+01:00 Guewen Baconnier <email@example.com>:On 03/11/2015 03:27 PM, Pedro Manuel Baeza Romero wrote: > * > > Said that, and as Nhomar told, to be made on future 9.0 branches, not on > current ones, I think we can improve this situation. Letting the modules > in root directory is not an option, because it has the mentioned > disadvantages, so I'd bet for starting in a clean branch, and using git > history when migrating one module. But this must be fully documented for > not discouraging contributions. You can't claim that it is not an option. Personally I think it is not the ideal option, but the least worst (with the current setup n-modules/repo). It is only a matter of a bad distinction between ported/unported when all the other options have technical drawbacks that will waste everybody's time. > * /git mv/ to move it from __unported__. This has issues as Alexandre stated > * Copy previous version over the current one. This only needs to take > care about renamed files or reorganize folders. Luckily, this won't > be needed soon with the folder structure standarization that > reviewers/contributors are doing. So you lose the history > * /git commit/ for marking changes already done on previous version. > * Migrate! -- Guewen Baconnier Business Solutions Software Developer Camptocamp SA PSE A, CH-1015 Lausanne Phone: +41 21 619 10 39 Office: +41 21 619 10 10 http://www.camptocamp.com/
Camptocamp France SAS, Alexandre Fayolle - Camptocamp