Re: Proposal: KDE CVS Commit Policy
Neil Stevens <[email protected]> Sun, 30 Mar 2003 07:47:37 -0800
| Newsgroups | gmane.comp.kde.policies |
|---|---|
| Message-ID | <[email protected]> |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday March 30, 2003 07:43, Stephan Binner wrote: > On Sunday 30 March 2003 14:24, Cornelius Schumacher wrote: > > 2. Never commit code that doesn't compile. > > With --disable-final? With --enable-final? > > > 6. Make sure that the maintainer of the code you are changing knows > > about your plans before committing. > > Do you want to describe the current situation (above has nothing to do > with reality) or do you want to change and slow down the development? > Most of my commits would be illegal by this definition. What about dead > maintainers? How about this: 6. Respect the policies of application and library maintainers, and consult with them before making large changes. Source control systems are not a substitute for developer communication. - -- Neil Stevens - [email protected] "The shepherd drives the wolf from the sheep's throat, for which the sheep thanks the shepherd as a liberator, while the wolf denounces him for the same act as the destroyer of liberty." -- Abraham Lincoln -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+hxGZf7mnligQOmERAgFFAJ4syY21Cp9Hrylc+R06m0q1gLQZdQCgjNnh rtbbg76FBo7bnZR4aDB1nYo= =6SKP -----END PGP SIGNATURE-----