> Sure it's good practise to check before you commit a stable release. > But it's up to the developer doing it.
I don't know in how many open source projects you're involved, but all projects I know have a quite rigid policy concerning commits into the stable tree. People with a write access bear a certain responsibility. Commiting without testing is an absolute NO-NO - anywhere and everytime. Otherwise you're risking the projekt and the community, as the incidence with Doug clearly showed. Errors happen, ok - but saying that anyone is invited to commit his buggiest code is a bit far-fetched. If you think you don't have the time to test your code, just do not commit it. Submit it to the patch manager and let others do the rest. That is the minimal compromise which allows a group of people to work on the same source base. Best regards, Stephan _______________________________________________ Dynapi-Dev mailing list [EMAIL PROTECTED] http://www.mail-archive.com/dynapi-dev@lists.sourceforge.net/
