httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Jagielski <...@jaguNET.com>
Subject Re: cvs commit: apache-devsite commitpolicies.html
Date Fri, 09 Jan 1998 23:57:15 GMT
brian@hyperreal.org wrote:
> 
>   <P>
>   
>   <UL>
>   <LI> The CVS tree should be expected to compile at all times
>   <LI> Experimental new features must be discussed before implemented
>   <LI> The committer is responsible for the quality of the third-party code
>      they bring into the code.
>   <LI> Related changes should be posted at once, or very closely together;
>      no half-baked projects in the code.
>   
>   <LI> Any changes:</BR>
>     <UL>
>     <LI>which affect symantics of arguments to directives 
>     <LI>which would have to be implemented differently on other architectures
>     <LI>which significantly add to the runtime size of the program
>     </UL>
>   need to be discussed on new-httpd before it gets committed, even experimentally.
>   
>   <LI> A patch must be reversed if the equivalent of a "veto" comes from
>   another developer with commit access.
>   

I think it would be helpful if, when a person decides to work
on some stuff, to post/commit/whatever a short little note saying
"I'm planning on doing this...". reasons have been posted before
but if needed, I can relist them.

+1

-- 
====================================================================
      Jim Jagielski            |       jaguNET Access Services
     jim@jaguNET.com           |       http://www.jaguNET.com/
            "Look at me! I'm wearing a cardboard belt!"

Mime
View raw message