On 11/11/2011 9:43 AM, Paul Querna wrote:
On Fri, Nov 11, 2011 at 7:36 AM, Stefan Fritsch<[email protected]> wrote:
In any case, if including apreq in some version of 2.4.x is planned, we
should not release mod_request with 2.4.0.
After some reflection I agree with Stefan.
+1 to branch 2.4.x from r1200449.
(There will be a handful of non-apreq revs to merge, but should be a
15 minute thing)
If the goal is to drive towards 3.0 with the major input/output filtering
improvements you've suggested, integrate apreq, and drop some of these
dirt-simple-stupid modules into core where they belong, then by all means,
let's fork so that people aren't stepping on one another's toes with
both stability changes and new development.
Nothing says that apreq couldn't then be backported from trunk for 2.4.1.
We aren't API-stable throughout a {rev}.{even} cycle, only backwards
compatible throughout that cycle.
But if we are now at 2.0/2.2/2.4/3.0 then it is time to kill 2.0. I've
started a thread on that topic.
