As OpenERP is a critical application for business, it should be controlled/managed when upgrading the system. Right now when I find a bug in the system and it is solved in trunk and ported to a official release, I need to update the whole system!
Ergo I have to test all business flows affected by the upgrade, but what is solved beside my needed fix? There is no documentation about he fixes, pre- and post conditions are missing and even bazaar reports only "fixed" or "modifs", not very useful. It would be good to have a system in place that records made solutions, where you can pick a needed solution for your problem and the system will mandatory pick all depended solutions (read affected objects) for installing in the right order. Resulting in a smaller changed system and thus smaller work in upgrading and better to plan and testing the system. Resume: businesses need a better way to control import of fixes/solutions in there running system without need to upgrade to the latest version. I know this would be a big step forward and is not created in a few weeks, but at least we can think about this already. Where we can start with today is to comment meaningful messages in bazaar! and extract those messages in a release document. ------------------------ Jan www.veritos.nl -------------------- m2f -------------------- -- http://www.openobject.com/forum/viewtopic.php?p=34063#34063 -------------------- m2f -------------------- _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman/listinfo/tinyerp-users
