Proposal: KDE CVS Commit Policy
Neil Stevens
kde-policies@mail.kde.org
Sun, 30 Mar 2003 07:47:37 -0800
=2D----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=
=20
with them before making large changes. Source control systems are not a=20
substitute for developer communication.
=2D --=20
Neil Stevens - neil@qualityassistant.com
"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
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+hxGZf7mnligQOmERAgFFAJ4syY21Cp9Hrylc+R06m0q1gLQZdQCgjNnh
rtbbg76FBo7bnZR4aDB1nYo=3D
=3D6SKP
=2D----END PGP SIGNATURE-----