coar        98/04/23 03:42:06

  Modified:    .        STATUS
  Log:
        Add some issues and votes.  Too overcast to see the conjunction
        this morning.  Drat.
  
  Revision  Changes    Path
  1.328     +21 -20    apache-1.3/STATUS
  
  Index: STATUS
  ===================================================================
  RCS file: /export/home/cvs/apache-1.3/STATUS,v
  retrieving revision 1.327
  retrieving revision 1.328
  diff -u -r1.327 -r1.328
  --- STATUS    1998/04/22 15:06:39     1.327
  +++ STATUS    1998/04/23 10:42:05     1.328
  @@ -94,6 +94,8 @@
   
   FINAL RELEASE SHOWSTOPPERS:
   
  +    * MIME type case sensitivity disparity between 1.2.6 and 1.3b6 (PR #2112)
  +
       * proxy security fixes from 1.2.5 need to be brought forward
   
       * Someone other than Dean has to do a security/correctness review on
  @@ -150,6 +152,7 @@
        (feb98 archives)
        Jim: I thought that we decided "default", although Ken
             thought it ugly
  +     Ken: I just don't like using "Add" when reverting something; no -1
   
       * proxy_*_canon routines use r->proxyreq incorrectly.  See
        <[EMAIL PROTECTED]>
  @@ -173,15 +176,6 @@
       * Paul would like to see a 'gdbm' option because he uses
         it a lot.
   
  -    * 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.
  -     apache-httpd: Ken +1
  -     leave it apache: +1 Brian, Ralf, Martin, Jim
  -
       * Maybe a http_paths.h file? See
        <[EMAIL PROTECTED]>
        +1: Brian, Paul, Ralf, Martin
  @@ -211,7 +205,7 @@
   
       * Ken's PR#1053: an error when accessing a negotiated document
         explicitly names the variant selected.  Should it do so, or should
  -      the base input name be referenced?
  +      the original URI be referenced?
   
       * Proposed API Changes:
   
  @@ -233,28 +227,35 @@
                    Martin +1, Ralf +1, Ken +1
   
       * Don't wait for WIN32:  It's been quite some time and WIN32 doesn't seem
  -     to be progressing, and Unix seems quite stable.  It would be in Apache's
  -     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.
  +      to be progressing, and Unix seems quite stable.  It would be in 
Apache's
  +      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.
   
               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
                      machine. Could be OS problems..
   
  -    * Should we re-enable nagle now that we're non-buffering CGIs?  See 
various
  -     messages from Marc in March 98.
  +    * Should we re-enable nagle now that we're non-buffering CGIs?  See
  +      various messages from Marc in March 98.
     
       * Listing the operating system's generic name (e.g. Irix, Win32) in
  -        SERVER_VERSION:
  +      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().
  -     
  +        that takes a 'const char *' and tacks it onto the end
  +        of the string returned by ap_get_server_version().  Would allow
  +        modules to add their info at run-time, more closely tracking
  +        reality for dynamically-loaded modules.
  +
  +      o Do we want to scrap -DSERVER_SUBVERSION if modules can add
  +        their contribution strings at run-time?
  +          +1: 
  +          -1: Ken
  +
         o Debate:
            Unix:Win32:OS/2 in '()' comment
  -          +1: Jim, Martin, Alexei
  +          +1: Jim, Martin, Alexei, Ken
            Irix:AIX:FreeBSD in '()' comment
   
   Win32 specific issues:
  
  
  

Reply via email to