While I agree that we do not expect trunk version to be as stable as released versions, but I think a good practice in software engineering is to ensure that the trunk should be free of regression issues as much as possible. I suggest that we have this following in place:
1. A clear/visible tags in trunk for non-regression issues (of the modules responsible by OpenERP SA, of course): this is intended for people to use the latest in trunk without too much troubles (they focus on their local development/new features rather than working on the problems resulting from the publisher/editor). This should be visible in the launchpad so people knows which one to update to. 2. Any regression issues reported by the test server should be treated with high priority: who breaks it, fix it. This can be and should be enforce among OpenERP SA development teams. 3. A more thorough automatic tests that cover everything from clean setup/start of the server. The reasons I ask for this was that many times, I found problems after restarting the servers, and not during the upgrading modules, which is very annoying. -- You received this bug notification because you are a member of C2C OERPScenario, which is subscribed to the OpenERP Project Group. https://bugs.launchpad.net/bugs/715667 Title: [6.0 trunk] setup stops with missing file(s) Status in OpenERP Server: In Progress Bug description: hi there, The new changes from last night broke the setup process. running python setup.py install on the folder, setup fails to find file 'release.py' as there is a important move from 'bin' to 'openerp' folders. correcting this leads to other errors. thank you! _______________________________________________ Mailing list: https://launchpad.net/~c2c-oerpscenario Post to : [email protected] Unsubscribe : https://launchpad.net/~c2c-oerpscenario More help : https://help.launchpad.net/ListHelp
