-APACHE 2.3 STATUS: -*-text-*-
+APACHE 2.3 STATUS: -*-text-*-
Last modified at [$Date$]
The current version of this file can be found at:
Patches considered for backport are noted in their branches' STATUS:
- * http://svn.apache.org/repos/asf/httpd/httpd/branches/1.3.x/STATUS
* http://svn.apache.org/repos/asf/httpd/httpd/branches/2.0.x/STATUS
* http://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x/STATUS
+
Release history:
[NOTE that x.{odd}.z versions are strictly Alpha/Beta releases,
while x.{even}.z versions are Stable/GA releases.]
- 2.3.11 : In development. Jim expects to T&R *as Beta* the week
- of Feb 28th.
+ 2.3.13 : In development.
+ 2.3.12 : Tagged on May 11, 2011.
+ 2.3.11 : Released as Beta on March 7, 2011.
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.
CURRENT RELEASE NOTES:
+GA PLAN:
+
+ Jim proposes another beta release the end of March, another in
+ April with a goal towards GA in May (at the latest). Jim volunteers
+ to RM these.
+
RELEASE SHOWSTOPPERS:
FOR GA:
- * Modules that are not ready for production use should be marked as
- experimental or be removed. The same for modules without documentation.
+ * Modules that are not ready for production use must be removed.
+ The same for modules without documentation.
Candidates:
- MPM simple
- - mod_serf
+ - mod_serf (which is optimal for async httpd anyways)
* Review the example configuration. It should be based on current best
practices and not use deprecated features.
-
- FOR BETA:
-
- * Not all MPMs are updated to set conn_rec::current_thread correctly.
- (Prefork, Worker, Event, Simple are updated).
- jim sez: Then we just ship with those... mark any others as
- experimental, pgollucci +1 jim
-
- FOR NEXT ALPHA:
+ wrowe sez: be specific or this isn't a SHOWSTOPPER
* 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,
modules that mix these 2 types... clean up is
forthcoming but should not be considered a blocker, imo
pgollucci: +1 jim
-
+ wrowe asks: what's the API change required?
+ wrowe asks; why are we shipping this if it requires apr_ssl
+
* mod_ssl's proxy support only allows one proxy client certificate per
frontend virtual host. Lift this restriction.
jim sez: Why a blocker?, pgollucci +1 jim
+ wrowe asks: what's the API change required?
+
+ * Clarify/potentially change the meaning of MaxConnections for Event MPM
+ with respect to accepting new connections and keep alive requests for
+ the docs and example config. This shouldn't change after users and
+ vendors have set up their stock config for event. This will end up
+ as a per-process thing for efficiency.
+
+ * INCLUDE mod_fcgid with 2.4.0, esp to help php users etc to enjoy
+ a painless event mpm experience.
+
+ * Decouple from apr_ldap to ease the transition to apr-2.0
+
+ FOR BETA:
OLD ISSUES THAT WERE THOUGHT TO BE SHOWSTOPPERS FOR 2.2 BUT OBVIOUSLY WEREN'T: