From ac7429cde36a3e12e97588542c76e33965465e4e Mon Sep 17 00:00:00 2001 From: Havoc Pennington Date: Tue, 11 May 2004 22:33:57 +0000 Subject: create a process for committing patches that doesn't bottleneck on Havoc --- HACKING | 35 +++++++++++++++++++++++++++++++++++ 1 file changed, 35 insertions(+) (limited to 'HACKING') diff --git a/HACKING b/HACKING index 1faad127..46d62024 100644 --- a/HACKING +++ b/HACKING @@ -143,3 +143,38 @@ created invalid messages. gives a complete report on test suite coverage. You can also run "test/decode-gcov foo.c" on any source file to get annotated source, after running make check with a gcov-enabled tree. + +Patches +=== + +Please file them at http://bugzilla.freedesktop.org under component +dbus, and also post to the mailing list for discussion. The commit +rules are: + + - for fixes that don't affect API or protocol, they can be committed + if any one qualified reviewer other than patch author + reviews and approves + + - for fixes that do affect API or protocol, two people + in the reviewer group have to review and approve the commit, and + posting to the list is definitely mandatory + + - if there's a live unresolved controversy about a change, + don't commit it while the argument is still raging. + + - regardless of reviews, to commit a patch: + - make check must pass + - the test suite must be extended to cover the new code + as much as reasonably feasible + - the patch has to follow the portability, security, and + style guidelines + - the patch should as much as reasonable do one thing, + not many unrelated changes + No reviewer should approve a patch without these attributes, and + failure on these points is grounds for reverting the patch. + +The reviewer group that can approve patches: Havoc Pennington, Michael +Meeks, Alex Larsson, Zack Rusin, Joe Shaw, Mikael Hallendal, Richard +Hult, Owen Fraser-Green, Olivier Andrieu. + + -- cgit v1.2.3