Hi, this have been discussed before, as I see, there is no actual release policy.
But still, you do not always have to jump to a new version as soon as it comes out. Of course there should be some strictly bugfix releases, without adding new functionality or removing some, so there would not be any need for hard testing. I believe there is no need to move the production system to a new version more than twice a year. Otherwise there is too much work hours generated on testing, and system becomes too expensive. There are also the place to talk about certification. If a module has been certified, there should not be problem to migrate it even to between major releases 5->6 (?)... In order to achieve migration guarantee, Tiny has to preserve the interfaces at least for certified modules. Here comes interesting dilemma - or Tiny will lock in the whole project (by certifying modules and preserving obsolete interfaces), or the whole certification is just a trick, and no migration possibility is ever guaranteed. Kaspars ------------------------ http://kndati.lv -------------------- m2f -------------------- -- http://www.openobject.com/forum/viewtopic.php?p=42252#42252 -------------------- m2f -------------------- _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman2/listinfo/tinyerp-users
