httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From c...@hyperreal.org
Subject cvs commit: apache-1.3 STATUS
Date Tue, 07 Apr 1998 13:18:02 GMT
coar        98/04/07 06:18:02

  Modified:    .        STATUS
  Log:
  	Votes and vetos.
  
  Revision  Changes    Path
  1.273     +20 -2     apache-1.3/STATUS
  
  Index: STATUS
  ===================================================================
  RCS file: /export/home/cvs/apache-1.3/STATUS,v
  retrieving revision 1.272
  retrieving revision 1.273
  diff -u -r1.272 -r1.273
  --- STATUS	1998/04/07 12:36:26	1.272
  +++ STATUS	1998/04/07 13:18:01	1.273
  @@ -15,9 +15,10 @@
         or not, and if not, what changes are needed to make it right.
   
         Approve guidelines as written:
  -         +1: Roy, Dean, Paul, Jim, Martin, Ralf, Randy, Brian
  +         +1: Roy, Dean, Paul, Jim, Martin, Ralf, Randy, Brian, Ken
            +0:
            -1:
  +      (Ken: 'lazy consensus' needs to be defined.)
   
   Plan:
   
  @@ -293,7 +294,8 @@
         1.3b6 and thus for the 1.3.x release branch via the
         apache-1.3/src/test/rename/rename.cf file as the configuration for the
         renaming. The used prefix or prefixes are configureable in the file.
  -       +1: Ralf, Jim, Roy
  +       +1: Ralf, Jim, Roy, Ken [only because collisions won't be addressed any
  +	   other way, apparently - otherwise agrees with Marc]
           0: Marc [thinks this is the wrong time for such a big change]
   
       * What prefixes to use for the renaming:
  @@ -308,6 +310,7 @@
           - Private functions which we can't make static (because of
             cross-object usage) but should be (e.g., new_connection)
               ap_xxx:    +1: Roy, Dean, Randy, Martin, Brian
  +		       -1: Ken
               apx_xxx:   +1: Ralf
               appri_xxx: +1: Paul, Ken
   
  @@ -319,6 +322,17 @@
               apm_xxx:   +1: Ralf
   
           Notes: 
  +	    - Ken: I'm vetoing the 'same prefix for everything' idea
  +	      because it means that everything is part of the API, and
  +	      every single change - even to things which aren't supposed
  +	      to be used by modules - will require a bump to MMN.  Either
  +	      we do it right, and distinguish by name between what's for
  +	      public consumption and what's not, or we don't do a global
  +	      rename at this point.  I feel this distinction is necessary
  +	      because of our 'glass house' (full source availability)
  +	      environment.  Saying 'look at the [nonexistent] documentation'
  +	      is a cop-out if we're going to do it right.
  +
               - Ralf: My opinion for my decisions are the following ones: 
                 1. The short ap_ prefix is a good idea because its
                    a handy prefix while still Apache specific, so I
  @@ -414,6 +428,10 @@
   	mod_auth_db at this time, and I'm pretty sure it was to
   	deal with this issue.  But I think I still ran into
   	troubles if I automatically looked for gdbm.
  +
  +    * The binary should have the same name on Win32 and UNIX.
  +	+1: Ken
  +	-1:  
   
       * What do we call the binary: apache or httpd? Under UNIX
         it's httpd, under Win32 it's apache. Maybe rename it
  
  
  

Mime
View raw message