> At least, I prefered when release come out more ofently.. this means less > change in the stable branch... which means also less time spent on fixing > regression... We (partners) don't earn money on regression fix, but we do on > migrating the customers system !
At the same time it means that 2 major versions per year have more steep change curve than 1 version per year. So if a company misses one or two upgrades, it may be unable to migrate let's say 5. to 7.version. Each migration has some overhead in time, that means more migrations per period of time, will possibly develop more working hours per customer, but still someone has to pay for that. As usual it is customer. I doubt if it is so good. This will not bring any quality benefit at all. OpenERP's API is not so well designed as it could be, this is probably because the lack of resources (changed terminology and so on between the versions). It is better to think over any change in API twice and only then include it in a production server. We are working with pretty serious data to sacrifice quality over the improvement of speed. I suggest informing on API changes before they are being built, and discuss it not only with direct developers, but also with the users. This is user oriented soft, isn't it? This is no military secret project, where disclosing information on future plans would bring some negative effects. Kaspars --------------------- http://kndati.lv -------------------- m2f -------------------- -- http://www.openobject.com/forum/viewtopic.php?p=42443#42443 -------------------- m2f -------------------- _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman2/listinfo/tinyerp-users
