Community mailing list archives
Re: OCA project: __unported__ folder considered painfulby
Anubía, soluciones en la nube, S.L., Alejandro Santana
Simplifying eben more Quentin's idea, there could be just one single text file called 'unported.txt', with a link to the previous version repo and a list of unported modules names.
My 2 cents.
2015-03-11 8:52 GMT+01:00 Quentin THEURET <email@example.com>:
On 11/03/2015 08:27, Alexandre Fayolle wrote: > 1. am I the only one to feel the pain of __unported__? Sorry, I didn't play a lot with merges of ported/unported modules, so I cannot tell you if it's very annoying. When the decision of put the unported modules in a __unported__ folder, I think community hoped all these modules will be ported into 8.0. But, it is not the case… I fear that if we remove these modules from the __unported__ folder and only let them on the 7.0 branch, we will lost the information that the module exists but it is unported to our version. > 2. do you think it is worthwhile to have 7.0 -> 8.0 merges for OCA projects? If the rewriting of the module is complete, I think it's not very worthwhile to have this kind of merges because the diff are too complex. > 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)? Maybe we can only put a file (__openerp__.py ?) for each unported module in the __unported__ folder which gie a link to the good branch where the module is availalbe. With this idea, we can remove the unported module source code, but we keep the information that other modules are available in an old branch. Regards, -- Quentin THEURET TeMPO Consulting 20, Avenue de la paix 67000 Strasbourg France http://www.tempo-consulting.fr Tel : 33 (0)3 88 56 82 18 Fax : 33 (0)9 70 63 35 46
Camptocamp France SAS, Alexandre Fayolle - Camptocamp