Proposal: KDE CVS Commit Policy

[Waldo Bastian]

On Sunday 30 March 2003 14:24, Cornelius Schumacher wrote:
> KDE CVS Commit Policy
> ----------------------------
>
>  1. Think before committing.
>  2. Never commit code that doesn't compile.
>  3. Test your changes before committing.
>  4. Always add log messages that somebody who only sees the log can
> understand.
>  5. Respect special commit policies set by the release plans.
>  6. Make sure that the maintainer of the code you are changing knows
> about your plans before committing.
>  7. If you have any doubts ask the maintainer of the code before
> committing.
>  8. If you commit bugfixes think about porting the fixes to other
> branches.
>  9. If you fix bugs reported on Bugzilla add the bug number to the log
> message and close the bug.
> 10. Don't forget that your commit will be publically available in the
> CVS repository forever.
>
>
> I would propose to discuss it and then put the result on a policies page
> on developer.kde.org.
>
> Comments?

Looks good. Wrt 8: use the same comment for both the original fix and the 
backport, that way it is easy to see which fixes have been backported 
already.

Cheers,
Waldo
-- 
bastian@kde.org -=|[ SuSE, The Linux Desktop Experts ]|=- bastian@suse.com