I think here is 2 debates : - How to improve the quality of new release, and how involve community in the design of new feature
- Is it better to have short or long release time > So where is the changelog between verions? There has been blog for API > changes created, unfortunately it is empty... I agree that Tiny need to improve their quality process. Everybody does, Fabien is the first one who want his ERP more stable I think :) ! That the purpose of this post, How could we do better than now ? We can do something better using : - RC and beta release for stable branch : a real release policy ! (apparently, this is coming soon, dixit Fabien) - Short release to let the stable branch stable, don't include new features or improvements in it. Release them in the next version. This is the point I'm "fighting" for ;) Short release = less work to test it = more people involve = better migration script and procedure. => All this will result in : - Stable will have less regression - Migration will be easier > Can you tell me where is the well designed migration script? In fact, even the official migration scripts are not enought to migrate a 4.2 version to 5.0 ! The GAP between those revisions is too large to allow that... so... make release smaller, then you'll benefit a well designed migration script :) ------------------------ Joël Grand-Guillaume <b>Camptocamp SA</b> PSE-A EPFL CH-1015 Lausanne -------------------- m2f -------------------- -- http://www.openobject.com/forum/viewtopic.php?p=42460#42460 -------------------- m2f --------------------
_______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman2/listinfo/tinyerp-users
