Contributors mailing list archives


Re: Mass commit to prepare branching 9.0

Tecnativa. S. L., Pedro M. Baeza
- 09/10/2015 07:24:17
Stéphane, go ahead then without normalizing the __unported__ modules, but please take in care Raphaël's comment. Another option is to follow my approach of removing entirely this directory on 9.0.


2015-10-09 9:07 GMT+02:00 Raphaël Valyi <>:
Hello Stéphane,

 wonder, if you do:
"2 move the content of __unported__ to the root of the repository with "git mv __unported__/* .", also on the 8.0 branch"

-> how will that no break the existing 8.0 PR's ?
Did you think about it? I fear it may even break the ability to rebase and merges these PR's
Or is it okay?

Thanks for your work as usual BTW

On Fri, Oct 9, 2015 at 3:53 AM, <> wrote:
On Thu, Oct 8, 2015 at 10:38 AM, <> wrote:
Hi, Stephane, maybe we should normalize also version number of __unported__ dir to 7.0.x.y(.z). All modules in __unported__ for 8.0 branch are assured to be 7.0 because a delete was done on 8.0 branch for modules not migrated from 6.1.

Are you 100% sure there is not any old 6.1 modules in 8.0/__unported__? Moreover I find it a bit weird to have unported modules with a greater version number than the last ported version. And I'm lacking time... ;)

So if you don't mind I'll proceed.

By the way, I'm finding here and there some remnant code in unported for modules that are ported (example: hr_expense_sequence in OCA/hr). In such cases I remove the code in 8.0/__unported__ directly without PR.


Post to:


Post to: