Yes to agressive backporting... Would be nice to

get the dev energy level back

PR:
Obtained from:
Submitted by:
Reviewed by:

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

diff --git a/STATUS b/STATUS
index a64b207b7b1871b72846063996d214815df6ba0d..e750928e28f105e5716594f0235dfbf28e69554f 100644 (file)
--- a/STATUS
+++ b/STATUS
@@ -1,5 +1,5 @@
 APACHE 2.0 STATUS:                                              -*-text-*-
-Last modified at [$Date: 2004/08/10 08:41:15 $]
+Last modified at [$Date: 2004/08/10 16:22:28 $]
 
 Release:
 
@@ -106,6 +106,11 @@ PATCHES TO BACKPORT FROM 2.1
        clar: +1, IMO all enhancements and RFCs fixes should go in 2.0 in order
                  to move the caching modules out of the exp area and then maybe
                  have more sites using them.
+       jim: +1   Making people who want to have a viable caching
+                 capability wait for 2.2 is unfair I think. Agressive
+                 backporting will allow more feedback and a shorter
+                 dev. time.
+
 
     *) Remove LDAP toolkit specific code from util_ldap and mod_auth_ldap.
          modules/experimental/mod_auth_ldap.c: 1.28