On Tue, Dec 8, 2015 at 4:31 PM, William A Rowe Jr <[email protected]> wrote: > On Tue, Dec 8, 2015 at 9:21 AM, Stefan Eissing > <[email protected]> wrote: >> >> >> > On Tue, Dec 8, 2015 at 8:34 AM, Stefan Eissing >> > <[email protected]> wrote: >> > +1 for deferring any upgrade changes >> > >> > Agreed, as spelled out in my top-post, simplest path to 2.4.18, and >> > these >> > interesting discussions over the past day point to no single simple >> > path. >> > >> > Does it make sense to @bug the new Protocol API's stating that these >> > remain experimental and still subject to change, and refer prospective >> > developer/consumers to dev@httpd? It seems something will change >> > in a later 2.4 release, and its simply a matter of what is the >> > appropriate >> > straight path that can satisfy all of the prospective upgrade consumers. >> >> +1 > > > Something like the attached? Edits/suggestions welcome.
+1, we discussed this already for 2.4.17 but it did not make its way. Thanks for doing it.
