APACHE 2.0 STATUS: -*-text-*-
-Last modified at [$Date: 2002/11/20 21:28:21 $]
+Last modified at [$Date: 2002/11/20 21:43:24 $]
Release:
modules are deferred for the next minor version bump (e.g. 2.1, 2.2
or 3.0).
+1: wrowe, jerenkrantz, aaron, brianp, trawick, stoddard, jwoolley,
- rbowen, rederpj, jim
+ rbowen, rederpj, jim, striker
0:
-1:
+1: wrowe, aaron, trawick, stoddard, jwoolley, rbowen, gregames,
rederpj, jim
0: jerenkrantz
- -1:
+ -1: striker
* Adopt an even/odd release paradigm (see VERSIONING) such that
even numbered releases are stable, and odd numbered releases
patches are (generally) first applied to the development branch,
tested, and then (after vote) applied to the stable branch.
+1: wrowe, jerenkrantz, aaron, trawick, stoddard, jwoolley, rbowen,
- gregames, rederpj, jim
+ gregames, rederpj, jim, striker
0:
-1:
to 2.1.0-dev.
+1 [from APACHE_2_0_43]: wrowe, aaron, trawick, stoddard, jwoolley,
gregames, rederpj, jim
- +1 [from HEAD]:
+ +1 [from HEAD]: striker
0: jerenkrantz
-1:
d) Installing a set of default config files when upgrading a server
doesn't make ANY sense at all.
- +1: striker
- ianh - medium/big sites don't use 'standard config' anyway, as it
- usually needs major customizations
+ +1: ianh - medium/big sites don't use 'standard config' anyway, as it
+ usually needs major customizations
-1: Ken, wrowe, jwoolley, jim
wrowe - diff is wonderful when comparing old/new default configs,
even for customized sites that ianh mentions