Community mailing list archives
Re: OCA project: __unported__ folder considered painfulby
Agree with Guewen, but newcomers & git lovers seem are the most ...
On 03/11/2015 08:27 AM, Alexandre Fayolle wrote: [...] > My take on this is that in a better world, "unported" modules would > not be in the 8.0 branch *at all*. They would live in their peaceful and > quiet lives in the 7.0 branch until someone decides it is time to move > them. I'm not quite sure how this can play nicely with the fact that I > would really like to have periodical merges of the 7.0 branches in the > 8.0 branches of the OCA projects to ensure that 8.0 versions get the > fixes from 7.0. AFAIK it is hard to move one module at a time from one branch to another preserving the git history. It is possible though by playing with git filter-branch. But I feel it would make uneasy the migration of modules to newcomers or the ones not being comfortable with git. > 1. am I the only one to feel the pain of __unported__? Same pain > 2. do you think it is worthwhile to have 7.0 -> 8.0 merges for OCA projects? > 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)? > My take is that the efforts that would require the move of individual modules between branches are not worth compared to the benefits to hide the unported modules. Unported modules have the 'installable' flag set to 'False' so it is possible to know which are ported or not (look up with a command line is possible too). BTW apps.odoo.com won't show unported modules. -- 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