Adds the second virtual host to the example, so that we don't end up

[apache] / STATUS

diff --git a/STATUS b/STATUS
index 1a865156f390e28be80a8eb6675ce1bffbd2f44e..3551f5bd67cc7ea7e66c75a9d221c949c8c1b9fc 100644 (file)
--- a/STATUS
+++ b/STATUS
@@ -26,7 +26,9 @@ Release history:
     [NOTE that x.{odd}.z versions are strictly Alpha/Beta releases,
           while x.{even}.z versions are Stable/GA releases.]
 
-    2.3.9   : In Development. Jim proposes T&R ~ November 14
+    2.3.11  : In development.
+    2.3.10  : Tagged on December 13, 2010. Released Dec 21, 2010.
+    2.3.9   : Tagged on November 23, 2010, not released.
     2.3.8   : Tagged on August 24, 2010.
     2.3.7   : Tagged on August 19, 2010, not released.
     2.3.6   : Released on June 21, 2010.
@@ -84,6 +86,13 @@ RELEASE SHOWSTOPPERS:
   * The mod_session* modules need to be checked that their hooks respect
     the returning of int (HTTP status codes) and apr_status_t as appropriate,
     and any anomolies fixed.
+    jim sez: from what I can see, mod_session* is no worse that other
+             modules that mix these 2 types... clean up is
+             forthcoming but should not be considered a blocker, imo
+
+  * mod_ssl's proxy support only allows one proxy client certificate per
+    frontend virtual host. Lift this restriction.
+    jim sez: Why a blocker?
 
 
   OLD ISSUES THAT WERE THOUGHT TO BE SHOWSTOPPERS FOR 2.2 BUT OBVIOUSLY WEREN'T:
@@ -116,8 +125,10 @@ CURRENT VOTES:
 
 RELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP:
 
-  * Add mod_allow_method or some other (usable) functionality to replace
-    Limit/LimitExcept.
+  * Clean up all the kruft and *extremely* outdated stuff below...
+
+  * Maybe remove Limit/LimitExcept or at least make it log warnings when
+    mis-used.
 
   * Sort out modules selections for most/all/reallyall. Maybe rename
     all -> most, reallyall -> all, and remove the old 'most'.
@@ -149,19 +160,6 @@ RELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP:
     wrowe suggests: it would be nice to see "MUST" v.s. "SHOULD" v.s. "MAY"
                     out of this list, without reviewing them individually.
 
-  * There is a bug in how we sort some hooks, at least the pre-config
-    hook.  The first time we call the hooks, they are in the correct 
-    order, but the second time, we don't sort them correctly.  Currently,
-    the modules/http/config.m4 file has been renamed to 
-    modules/http/config2.m4 to work around this problem, it should moved
-    back when this is fixed.
-
-      OtherBill offers that this is a SERIOUS problem.  We do not sort
-      correctly by the ordering arguments passed to the register hook
-      functions.  This was proven when I reordered the open_logs hook
-      to attempt to open the error logs prior to the access logs.  Possibly
-      the entire sorting code needs to be refactored.
-
   * pipes deadlock on all platforms with limited pipe buffers (e.g. both
     Linux and Win32, as opposed to only Win32 on 1.3).  The right solution
     is either GStein's proposal for a "CGI Brigade", or OtherBill's proposal
@@ -403,7 +401,7 @@ WISH LIST
     line server hooks (Ryan really hated this. It is great for
     performance, but bad because of the complications listed above).
 
-    mod_cache/mod_mem_cache/mod_disk_cache:
+    mod_cache/mod_mem_cache/mod_cache_disk:
 
   * mod_mem_cache: Consider adding a RevalidateTimeout directive to
     specify time at which local cached content is to be revalidated
@@ -413,7 +411,7 @@ WISH LIST
     jerenkrantz says: Too slow.  Get regexs away from speedy caches by
                       default.  Introduce a new CacheEnableRegex if you want.
 
-  * mod_mem_cache/mod_disk_cache: Need to be able to query cache
+  * mod_mem_cache/mod_cache_disk: Need to be able to query cache
     status (num of entries, cache object properties, etc.).
     mod_status could be extended to query optional hooks defined
     by modules for the purpose of reporting module status.