httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j..@hyperreal.org
Subject cvs commit: apache-1.3 STATUS
Date Mon, 20 Apr 1998 20:18:06 GMT
jim         98/04/20 13:18:03

  Modified:    .        STATUS
  Log:
  Update STATUS
  
  Revision  Changes    Path
  1.309     +18 -13    apache-1.3/STATUS
  
  Index: STATUS
  ===================================================================
  RCS file: /export/home/cvs/apache-1.3/STATUS,v
  retrieving revision 1.308
  retrieving revision 1.309
  diff -u -r1.308 -r1.309
  --- STATUS	1998/04/20 08:28:48	1.308
  +++ STATUS	1998/04/20 20:18:02	1.309
  @@ -2,10 +2,12 @@
   
   Release:
   
  -    1.3b7: freeze; Hopefully to simply be renamed 1.3.0
  +    1.3.0: Shoot for May 16, 1998 Release!
   
  -    1.3b6: Tagged APACHE_1_3b6. Possible release 4/20
  +    1.3b7: In development
   
  +    1.3b6: Tagged APACHE_1_3b6. Announced and Released 4/20/98
  +
       2.0  : In pre-alpha development, see apache-2.0 repository
   
   Guidelines:
  @@ -162,16 +164,16 @@
       * What do we call the binary: apache or httpd? Under UNIX
         it's httpd, under Win32 it's apache.
   	apache-httpd: Ken +1
  -	leave it apache: +1 Brian, Ralf, Martin
  +	leave it apache: +1 Brian, Ralf, Martin, Jim
   
       * Maybe a http_paths.h file? See
   	<Pine.BSF.3.95q.971209222046.25627D-100000@valis.worldgate.com>
   	+1: Brian, Paul, Ralf, Martin
  +	+0: Jim (not for 1.3.0)
   
       * Release builds: Should we provide Configuration or not?
         Should we 'make all suexec' in src/support?
  -	Ken +1 (possible suexec path issue, though)
  -        Brian +1
  +	+1: Brian, Jim, Ken +1 (possible suexec path issue, though)
   
       * root's environment is inherited by the Apache server. Jim & Ken
         think we should recommend using 'env' to build the
  @@ -219,12 +221,6 @@
   	best interest to continue to support Unix to its utmost, and not delay
   	a release of 1.3.0 waiting for WIN32 issues to be resolved.
   
  -	Proposal: the next release should be named 1.3b6, and labelled "release
  -	    candidate on unix, beta on NT".  The release after that will be
  -	    called 1.3.0 "stable on unix, beta on NT".
  -	    +1: Jim, Ralf, Randy, Brian, Martin
  -	    +0: 
  -
               Notes:
               Randy: I would also argue that 1.3b6 is _not_ stable. I've been 
                      having real fits keeping it alive on a dual processor
  @@ -233,8 +229,17 @@
       * Should we re-enable nagle now that we're non-buffering CGIs?  See various
   	messages from Marc in March 98.
     
  -    * Should we list the operating system's generic name (e.g. Irix, Win32) in
  -        SERVER_VERSION?
  +    * Listing the operating system's generic name (e.g. Irix, Win32) in
  +        SERVER_VERSION:
  +	 o Looks like we want to do this...
  +	   Implementation: New API function, ap_add_version_component()
  +	    that takes a 'const char *' and tacks it onto the end
  +	    of the string returned by ap_get_server_version().
  +	
  +	 o Debate:
  +	    Unix:Win32:OS/2 in '()' comment
  +	     +1: Jim, Martin, Alexei
  +	    Irix:AIX:FreeBSD in '()' comment
   
   Win32 specific issues:
   
  
  
  

Mime
View raw message