fielding    99/01/07 14:39:18

  Modified:    .        STATUS
  Log:
  T minus 48hours
  
  Revision  Changes    Path
  1.593     +34 -13    apache-1.3/STATUS
  
  Index: STATUS
  ===================================================================
  RCS file: /home/cvs/apache-1.3/STATUS,v
  retrieving revision 1.592
  retrieving revision 1.593
  diff -u -r1.592 -r1.593
  --- STATUS    1999/01/05 08:17:24     1.592
  +++ STATUS    1999/01/07 22:39:17     1.593
  @@ -1,11 +1,11 @@
     1.3 STATUS:
  -  Last modified at [$Date: 1999/01/05 08:17:24 $]
  +  Last modified at [$Date: 1999/01/07 22:39:17 $]
   
   Release:
   
       1.3.4-dev: current.
  -            Possible release on ???
  -            Lars volunteers as RM for dates after January 21.
  +           Tarball planned for Saturday afternoon PST, Roy is RM
  +           Release planned for Monday, January 11.
   
       1.3.3: Tagged and rolled on Oct. 7.  Released on 9th, announced on 10th.
       1.3.2: Tagged and rolled on Sep. 21. Announced and released on 23rd.
  @@ -16,14 +16,9 @@
   
   RELEASE SHOWSTOPPERS:
   
  -    * long pathnames with many components and no AllowOverride None
  -        Status: Marc is looking at it
  -
   RELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP:
   
  -    * Document compilation on Win95 and NT
  -
  -    * RemoveHandler directive needs docs
  +    * Update the Win32 install script
   
       * Randy's proposed changes for binbuild:
       
  @@ -43,8 +38,17 @@
         4. Create toplevel 'setup' script for install to mirror win32 name
            [It is currently creating "install-bindist.sh"]
   
  +    * long pathnames with many components and no AllowOverride None
  +        Workaround is to define <Directory /> with AllowOverride None,
  +        which is something all sites should do in any case.
  +        Status: Marc was looking at it.
  +
   Documentation that needs writing:
   
  +    * Document compilation on Win95 and NT
  +
  +    * RemoveHandler directive needs docs
  +
       * Need a document explaining mod_rewrite/"UseCanonicalName off" based
         virtualhosting.  (If it exists already I can't find it easily.)
         => It still doesn't exists but I've already assembled the relevant
  @@ -53,6 +57,10 @@
   
   Available Patches:
   
  +    * Martin's [PATCH] Make "-S" exit(0) after dumping the VHost settings
  +        Message-ID: <[EMAIL PROTECTED]>
  +        Status: Martin +1, Roy +1
  +
       * Jim Patterson's patch to make mod_info work on Win32
           Message-ID: PR#1442
           Status: Lars +1 (on concept)
  @@ -91,6 +99,10 @@
           Message-ID: <[EMAIL PROTECTED]>
           Status: 
   
  +    * Ronald Tschalär's major update of mod_digest
  +        Message-ID: <[EMAIL PROTECTED]>
  +        Status: Big change -- needs review.
  +
   In progress:
   
       * Marc's [PATCH] PR#3323: recursive includes
  @@ -98,10 +110,6 @@
        Status: Marc +1, Jim +1 (concept)
        * Needs more in-depth review *
   
  -    * Ronald Tschalär's major update of mod_digest
  -        Message-ID: <[EMAIL PROTECTED]>
  -        Status: 
  -
       * Mark Bixby's freshening up the MPE/iX port (mostly APACI)
        Message-ID: <[EMAIL PROTECTED]>
           Status: Mark says: "...currently waiting for HP to fix two OS bugs.
  @@ -111,6 +119,11 @@
                fopen()" bug has been identified, but analysis on how
                to fix it continues."
   
  +    * Doug MacEachern's libapr - Generic Apache Request Library (Alpha)
  +      This package contains modules for manipulating client request data
  +      via the Apache API with Perl and C.
  +        Status: http://www.pobox.com/~dougm/libapr-0.20_01.tar.gz
  +
   Needs patch:
   
       * get_path_info bug; ap_get_remote_host should be ap_vformatter instead.
  @@ -143,6 +156,14 @@
         What is needed is a separate interface for "don't need a dup"
         situations, like just about everywhere we use it in bvputs and
         bputs calls.
  +
  +    * Should we disallow requests with bogus characters in the method?
  +      See <[EMAIL PROTECTED]>
  +
  +    * A mechanism is needed for applying access control to methods
  +      that are not known by the server core, either using a Limit __unknown__
  +      as in <<[EMAIL PROTECTED]>,
  +      or via a LimitExcept directive.
   
   Open issues:
   
  
  
  

Reply via email to