[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-devel] CVS guidelines

From: Karsten Hilbert
Subject: Re: [Gnumed-devel] CVS guidelines
Date: Mon, 17 Nov 2003 21:48:02 +0100
User-agent: Mutt/


> 1.) start your work in test-area
> 2.) from now on all patches should be peer reviewed before comitting to CVS
> 3.) unreviewed patches will not make it into CVS (main trunk)
> 4.) comment your code ( and I mean comment everything even if it might seem 
> stupid to you !!!! )
> 5.) uncommented code (new files etc. ) will not make it into CVS
main trunk

> 6.) submit early and often / announce changes to the list
> 7.) be aware that huge patches will most likely be ignored by peer reviewers 
> unless they agree with it
> 8.) do not mix tabs and spaces when indenting ( tabs are preferred )
> 9.) never commit files you did not change 
> 10.) add commit comments to each file you commit !!!
meaningful comments, that is

> 11.) take  a close look at what code is already there, use existing code 
> whenever possible, enhance existing code whenever necessary
> 12.) wanna code your own client ? That's perfectly fine . Please stick to 
> test-area for that

> 13.) whatever is missing
> I want to hear your comments. If you intend you help ! GNUmed in the future 
> raise your voice. By now you may think who they hell does he think he is !

13) code that is checked into the main trunk must be tested
and must run reasonably well (one doesn't find all bugs, of
course) unless it is new and initial work in progress and
clearly announced as such

GPG key ID E4071346 @
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

reply via email to

[Prev in Thread] Current Thread [Next in Thread]