Contributors mailing list archives


Re: Migration to version 9

Tecnativa. S. L., Pedro M. Baeza
- 31/08/2015 10:13:22
And another one is that you cannot merge branch 8.0 against 9.0 for unported modules. If we solve the problem with Odoo loading some parts of uninstalled modules, I would prefer option 2 over 3. Option 1 is still my favourite, but has some drawbacks that we have solved also.

One possible workaround for option 2: what about renaming to This way, modules will not be loaded because Python doesn't have the module loading file, but we have to see if it gives any error or not.


2015-08-31 12:08 GMT+02:00 Guewen Baconnier <>:
On Mon, Aug 31, 2015 at 11:53 AM, Daniel Reis <> wrote:
>> 1)   Migration to version 9 (git-filter option)
>> 2)   Migration to version 9 (installable False option)
>> 3)   Migration to version 9 (rm checkout option)
> #2 still has the same big problem the __unported__ solution had:
> it's easy to forget to forward port change in the previous version.
> I did a PoC for #3 and couldn't find any disadvantages:

I mentioned a major one: the diff shows you the entire addon as a new
addition instead of showing you the +- lines of the migrated code.

> - ported modules are immediately visible
> - you are "forced" to start a port PR using the current version in 8.0
> - history is kept just like with the installable='false'
> Find the PoC here:
> (sorry for using the OCA repo)
> Check the history for the module ported to v9:
> --Daniel

Post to: