Move the Edge Connection Filter issue to a non-showstoper, as I mentioned on the...

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x@332920 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/STATUS b/STATUS
index a50ee581615ec79baf43fd83c493068dee0afbbd..e093165c0e72dcd1d10bc0f3553cad807c0523be 100644 (file)
--- a/STATUS
+++ b/STATUS
@@ -3,7 +3,7 @@ Last modified at [$Date$]
 
 The current version of this file can be found at:
 
-  * http://svn.apache.org/repos/asf/httpd/httpd/trunk/STATUS
+  * http://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x/STATUS
 
 Documentation status is maintained seperately and can be found at:
 
@@ -71,18 +71,6 @@ RELEASE SHOWSTOPPERS:
         showstopper.
       pquerna agrees: Not a regression from 2.0.x.
 
-    * the edge connection filter cannot be removed 
-      http://marc.theaimsgroup.com/?l=apache-httpd-dev&m=105366252619530&w=2
-
-      jerenkrantz asks: Why should this block a release?
-
-      stas replies: because it requires a rewrite of the filters stack
-            implementation (you have suggested that) and once 2.2 is
-            released you can't do that anymore. 
-
-      pquerna says: Rewriting the filter stack can happen after 2.2, imo.
-                    This isn't a regression from 2.0.x.
-
 CURRENT VOTES:
 
     * httpd-std.conf and friends
@@ -140,6 +128,18 @@ CURRENT VOTES:
 
 RELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP:
 
+    * the edge connection filter cannot be removed 
+      http://marc.theaimsgroup.com/?l=apache-httpd-dev&m=105366252619530&w=2
+
+      jerenkrantz asks: Why should this block a release?
+
+      stas replies: because it requires a rewrite of the filters stack
+            implementation (you have suggested that) and once 2.2 is
+            released you can't do that anymore. 
+
+      pquerna says: Rewriting the filter stack can happen after 2.2, imo.
+                    This isn't a regression from 2.0.x.
+
     * mod_cache currently trumps mod_authz_host. When serving local content,
       the directives: "Allow from 10.0.0.0/8\nDeny from all" become
       meaningless, as any content cached will be served to any IP address.