Fabien, I find this policy not very useful for OpenERP and also users.
I suggest to google for "Trunk stable" 9.3 Million hits and "Trunk unstable" 800000 hits. Clearly the software development model to hold trunk always stable is the favorite one, why - alpha, beta and releases are just snapshots of trunk, a continuous software development cycle is possible - continuous testing can be done by outsiders by pulling simply trunk, this gives an additional feedback loop before a release happens - documentation can be continuously updated and doesnt need to be created in a hurry when suddenly the release happens. etc. To achieve a stable release your model forces you to make a snapshot of trunk and then make another intermediate development cycle until stable. Clearly that puts you under lots of time pressure to go from trunk to stable. IMO trunk should be controlled by only very few people whose main task is to observe that any merge is stable. Ground-breaking development can be branched off until it is stable. Just my very humble opinion on the matter. Geejay -------------------- m2f -------------------- -- http://www.openerp.com/forum/viewtopic.php?p=25278#25278 -------------------- m2f -------------------- _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman/listinfo/tinyerp-users
