Sign in
Try it free
  1. Mailing Lists
  2. Community
  3. Re: OCA project: __unported__ folder considered painful

Community mailing list archives

community@mail.odoo.com

Browse archives

Re: OCA project: __unported__ folder considered painful

Re: OCA project: __unported__ folder considered painful

Re: OCA project: __unported__ folder considered painful

by
Acsone, Stéphane Bidoul
- 03/11/2015 05:25:30
On Wed, Mar 11, 2015 at 8:27 AM, Alexandre Fayolle <alexandre.fayolle@camptocamp.com> wrote:
1. am I the only one to feel the pain of __unported__?
Not a huge pain, but a pain nevertheless. 
2. do you think it is worthwhile to have 7.0 -> 8.0 merges for OCA projects?
Definitely yes. It is made difficult by the new API migration, but doing it frequently and resolving conflicts let us mark cleanly what has been forward ported. I'm in favor of progressively making this forward porting systematic at least for 7.0 -> 8.0 (not 6.1).
3. do you have ideas how to tackle the two objectives above (preferably
without going through a huge reorganisation of our repositories, cf.
note below)?
I'm personally fine with the installable flag being set to False (plus a comment explaining why it is False). Such modules are not visible on apps.odoo.com and are not ...installable. When browsing source code, it's easy to open the __openerp__.py to check it's status.

-sbi

Reference