-APACHE 2.1 STATUS: -*-text-*-
+APACHE 2.3 STATUS: -*-text-*-
Last modified at [$Date$]
The current version of this file can be found at:
-http://svn.apache.org/repos/asf/httpd/httpd/trunk/STATUS
-Release history:
- [NOTE that only Alpha/Beta releases occur in 2.1 development]
+ * http://svn.apache.org/repos/asf/httpd/httpd/trunk/STATUS
+
+Documentation status is maintained seperately and can be found at:
+
+ * docs/STATUS in this source tree, or
+ * http://svn.apache.org/repos/asf/httpd/httpd/trunk/docs/STATUS
+
+Consult the following STATUS files for information on related projects:
+
+ * http://svn.apache.org/repos/asf/apr/apr/trunk/STATUS
+ * http://svn.apache.org/repos/asf/apr/apr-util/trunk/STATUS
- 2.1.5 : in development
- 2.1.4 : not released.
- 2.1.3 : Released on 2/22/2005 as alpha.
- 2.1.2 : Released on 12/08/2004 as alpha.
- 2.1.1 : Released on 11/19/2004 as alpha.
- 2.1.0 : not released.
+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 only Alpha/Beta releases occur in 2.3 development]
-Please consult the following STATUS files for information on related projects:
+ 2.3.0 : in development
- * http://svn.apache.org/repos/asf/apr/apr/trunk/STATUS
- * http://svn.apache.org/repos/asf/apr/apr-util/trunk/STATUS
- * http://svn.apache.org/repos/asf/httpd/httpd/trunk/docs/STATUS
Contributors looking for a mission:
* Open bugs in the bug database.
+
CURRENT RELEASE NOTES:
+
RELEASE SHOWSTOPPERS:
* Handling of non-trailing / config by non-default handler is broken
http://marc.theaimsgroup.com/?l=apache-httpd-dev&m=105451701628081&w=2
jerenkrantz asks: Why should this block a release?
+ wsanchez agrees: this may be a change in behavior, but isn't
+ clearly wrong, and even if so, it doesn't seem like a
+ showstopper.
* 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.
+
CURRENT VOTES:
* httpd-std.conf and friends
c) tailored httpd-std.conf should be installed to
sysconfdir/examples or manualdir/exampleconf/
+1: slive, trawick, Ken, nd (prefer the latter), erikabele
+ +1: wsanchez (propose sysconfdir/examples/<version> for diffiness)
d) Installing a set of default config files when upgrading a server
doesn't make ANY sense at all.
pquerna: Do we want to change this for 2.2?
+
RELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP:
* Patches submitted to the bug database:
http://issues.apache.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Apache+httpd-2.0&keywords=PatchAvailable
- * The Event MPM does not work on Solaris 10. PR 34040.
-
* Filter stacks and subrequests, redirects and fast redirects.
There's at least one PR that suffers from the current unclean behaviour
(which lets the server send garbage): PR 17629
query cases; but I'm beginning to think that in these cases
the app should be querying ap{r,u}-config directly
gstein: agreed. apxs should deprecate the -q flag
+ pquerna: I vote for a httpd-config, and to deprecate the -q flag.
+ minfrin: +1 for httpd-config, and to deprecate -q.
+
TODO ISSUES REMAINING IN MOD_SSL:
* the shmcb code should just align its memory segment rather than
jumping through all the "safe" memcpy and memset hoops
+
WISH LIST
* mod_proxy: Ability to run SSL over proxy gateway connections,
encrypting (or reencrypting) at the proxy.
HTTP or SNMP?
jerenkrantz says: Yawn. Who cares.
-EXPERIMENTAL MODULES:
-
- Experimental modules should eventually be be promoted to fully supported
- status or removed from the repository entirely (ie, the
- 'experiment' failed). This section tracks what needs to happen to
- get the modules promoted to fully supported status.
-
-
-Other bugs that need fixing:
-
* MaxRequestsPerChild measures connections, not requests.
Until someone has a better way, we'll probably just rename it
"MaxConnectionsPerChild".
Status: Greg volunteers to investigate (esp. since he was most
likely the one to break it :-)
-Binaries (probably not till beta):
-
- Platform Avail. Volunteer
- ------------------------------------------------------------------
- AIX 4.3.3 no Bill Stoddard
- Mandrake 8.1 no open
- FreeBSD 4.1 no open
- hppa2.0w-hp-hpux11.00 no Cliff Woolley
- i386-pc-solaris2.8 no Aaron Bannert
- i386-unknown-freebsd4.5 no
- i386-unknown-freebsd4.6 no Cliff Woolley
- i686-pc-linux-gnu-slackware81 no Cliff Woolley
- i686-pc-linux-gnu-rh70 no Aaron Bannert
- i686-pc-linux-gnu-rh73 no Cliff Woolley
- ia64-hp-hpux11.20 no
- powerpc-apple-darwin5.5 no Aaron Bannert
- powerpc-unknown-linux-gnu no Graham Leggett
- s390-ibm-linux no Greg Ames
- sparc-sun-solaris2.8 no Jim Jagielski
- NetWare no Brad Nicholes
- OS/2 no Brian Havard
- OS/390 no Greg Ames
- Win32-x86 no William Rowe
+EXPERIMENTAL MODULES:
+
+ Experimental modules should eventually be be promoted to fully supported
+ status or removed from the repository entirely (ie, the
+ 'experiment' failed). This section tracks what needs to happen to
+ get the modules promoted to fully supported status.
+
+
projects / apache / blobdiff