@albertca,
> Given that the problem is the lack of resources I don't think shorter periods > between releases will solve that. If there are not enough resources right now, > there won't be enough resources to test new releases every half a year. Even > more if I want to upgrade all/most customers. etc.. Because you see resource as internal to Tiny only. While actually, there are lots of partners/advanced users in the world that would jump in the new releases if those weren't that experimental. Currently, when a major release is out, you typically didn't put any resources in building it because you were working for customer not using it while it has been done is the dark of an unstable trunk branch by Tiny very limited resource during the whole past year, with nobody testing it. Then the new version pops up. When you start using in it, after a few month of kamikaze stabilization by others, then the version is already feature frozen to third parties under the pretext that it's supposed to be stable. But just because there are too many bugs and things to re-think, in the urgence of customers/partners bugs, Tiny himself finally makes dangerous changes to that "stable branch" leading to all the stability issue we are talking about. I simply try to propose something that allows moving away for that vicious circle that could trap OpenERP for yet a few years. You could also read a DHH (Rails creator) interview recently stating that in order to avoid bugs, they want to move away for long release cycles so that people test more often and more people get involved in development branch as they have incentive in doing it, which is currently not the case with OpenERP unfortunately.[/quote] ------------------------ Raphaël Valyi CEO and OpenERP consultant at http://www.akretion.com -------------------- m2f -------------------- -- http://www.openobject.com/forum/viewtopic.php?p=42407#42407 -------------------- m2f --------------------
_______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman2/listinfo/tinyerp-users
