propose merge of trivial "fix" related to log level of a message

yank some now-resolved votes related to which level of apr will be
used by APACHE_2_0_BRANCH

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

diff --git a/STATUS b/STATUS
index 19a22d730a2f563b95f68af65924a55ddbace0a1..25573925e37d246a3388712d2d54e890ef2fb0c7 100644 (file)
--- a/STATUS
+++ b/STATUS
@@ -1,5 +1,5 @@
 APACHE 2.0 STATUS:                                              -*-text-*-
-Last modified at [$Date: 2003/09/05 19:00:51 $]
+Last modified at [$Date: 2003/09/05 19:43:20 $]
 
 Release:
 
@@ -375,6 +375,12 @@ PATCHES TO PORT FROM 2.1
         server/mpm/worker/worker.c r1.138
       +1: trawick, stoddard
 
+    * Lower the severity of the "listener thread didn't exit" message
+      to debug, as it is of interest only to developers.
+        server/mpm/experimental/threadpool/threadpool.c r1.20
+        server/mpm/worker/worker.c
+      +1: trawick
+
 CURRENT RELEASE NOTES:
 
     * Backwards compatibility is expected of future Apache 2.0 releases,
@@ -391,36 +397,6 @@ CURRENT VOTES:
       items to be addressed as a supported module).
       +1: jim, stoddard, bnicholes
 
-    * APACHE_2_0_BRANCH *has* to work with an official stable version 
-      of APR (i.e., 1.0).
-      yes:
-      no:   trawick, jerenkrantz, wrowe, stoddard, striker, nd, gregames
-        wrowe: it's nice if we *can* compile against it, but as a
-               matter of a practical tarball or binary release, don't.
-        gstein: the Q is unclear. of course it has to work with an
-                official version. maybe the Q is really "we *require*
-                a stable version" ?
-
-    * APACHE_2_0_BRANCH uses a level of apr and apr-util code branched
-      from the APACHE_2_0_44 tag.
-      yes:   trawick, jerenkrantz, striker, nd, gregames
-        (but nd doesn't branch anything in apr repos)
-      no:    wrowe
-        (objection remains the same, APR 0.9 is pretty much in 'bugfix'
-         mode, all such bugfixes are helpful to the httpd project; some 
-         on the APR list have suggested branching APR 0.10.x when some
-         new code comes along.  Again, wrowe suggests the option below
-         is sufficient as long as eyeballs remain on binary compat.)
-
-    * APACHE_2_0_BRANCH uses a level of APR code versioned 0.9.2-dev
-        or later (to 0.9.9), so long it remains binary compatible.
-      yes:   wrowe
-      no:    
-        (wrowe suggests that when apr chooses to break compatibility,
-         httpd would continue to use that last compatible build.  It's
-         in the httpd project's interest to participate instead of fork
-         APR efforts.)
-
     * Develop in Review-Then-Commit or Commit-Then-Review mode 
       on APACHE_2_0_BRANCH (no vetoes, this is a straight vote.)
        R-T-C:   trawick, wrowe, jerenkrantz, stoddard, rederpj, striker, nd,