Community mailing list archives
Re: OCA project: __unported__ folder considered painfulby
No pain maybe, just headache :) for me beside pythonic where regulary & daily coding in c/c++/java for firmwares, kernel & drivers. But it is a must because a lot of end users go back to previous version for many reasons.
But, odoo is an ERP. I dont think so. Is it posible some one back to old version of odoo?
wasn't there a proposal by someone to have two branches for each version?
All 'unported' modules go to the 'x.0 dev' branch and move to 'x.0 master' once they are ready to use.
On 3/11/2015 3:42 PM, Holger Brunn wrote:<blockquote cite="mid:54FFF0A3.email@example.com" type="cite">
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 > 1. am I the only one to feel the pain of __unported__? not at all. I'm very unhappy with that too > 2. do you think it is worthwhile to have 7.0 -> 8.0 merges for OCA > projects? sounds good in theory, but as soon as you did the v8 api port you're bound to get so many conflicts that I assume it's less hassle to do the improvement in both versions. When I review PRs, I try to have people do the same for version(s) >n too if appropriate. Maybe http://odoo-community.org/page/how-to should state this as a requirement for PRs? > 3. do you have ideas how to tackle the two objectives above with a social contract as proposed in (2) - -- Therp - Maatwerk in open ontwikkeling Holger Brunn - Ontwerp en implementatie mail: firstname.lastname@example.org web: http://therp.nl phone: +31 (0)20 3093096 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iF4EAREIAAYFAlT/8KAACgkQAcl2D+yjrhg8SgD/TapYAQFEJWVcMTpB1txOkuLl l4aCWq/tbd8n6EmhsK8BAKttbkLc7oR2Bl9Hrns3B5jIfbtjpCWrrZF0pE7j1ppJ =4UPj -----END PGP SIGNATURE-----
Gunnar Wagner | Iris Germanica Ltd. | JinQian Gong Lu 385, 8-201 | FengXian Qu, 201404 Shanghai | P.R. CHINA
+86 159 0094 1702 | +49 (0)176 7808 9090 | skype: professorgunrad | www.fashionsupermarket.net
Camptocamp France SAS, Alexandre Fayolle - Camptocamp