Thank you for these responses. It was obvious to me that something was very much needed to straighten out the source code trees.
And some suggestions: Please ALWAYS tag a release in the trunk. Every release should have an entry in trunk. When creating release versions please be cognizant of the fact that some packagers have version restrictions (like RPM). RPM can only work properly if the versioning is in absolute lexical order from the very early development up through final release. So for example, in RPM the release consists of two components, the version string and a release string, and this is why you always see strings like 'version=5.0.4' and 'release=1' in the default rpm setup files. It means that the first final release must look like 5.0.4-1 and NOT 5.0.4-0. All 5.0.4.0[xxxx] releases are considered pre-releases according to RPM rules. Examples would be: 5.0.4-0_12345678 (development) 5.0.4-0_a14 (alpha) 5.0.4-0_b3 (beta) 5.0.4-0_rc1 (release candidate) 5.0.4-1 (final release) 5.0.4-2(bugfix after final) And all this works for other packagers besides RPM as well. So if this convention is followed then everyone can be happy and RPM packages don't have to go and reinvent the wheel with different release designations which can get very confusing for users. And last, is there any ETA for when the manual merging will be completed? Regards, Gerry -------------------- m2f -------------------- -- http://www.openobject.com/forum/viewtopic.php?p=43728#43728 -------------------- m2f -------------------- _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman2/listinfo/tinyerp-users
