> On Sep 25, 2015, at 11:09 AM, Eric Covener <[email protected]> wrote: > > On Fri, Sep 25, 2015 at 11:06 AM, Yann Ylavic <[email protected]> wrote: >> On Fri, Sep 25, 2015 at 4:31 PM, Jim Jagielski <[email protected]> wrote: >>> I'd like to propose that we consider mod_h2 in 2.4.x as CTR and >>> in the same category as mod_lua... That is, somewhat "prod-experimental" >>> in that some features may still change, but stable enough to be >>> usable in production environs. >> >> I like "prod-experimental" because I think it is production ready, and >> still it lets us optimize the interface without giving developpers >> (not users!) strong garanties. >> >> Maybe the ALPN and protocol selection hooks could be marked as such >> too, we could have the need to change a RUN_ONCE to a RUN_ALL for >> those and shouldn't give too much garanties to other modules. >> >> So if we can find a good wording to also express "prod-ready" (I guess >> it already runs successfully in some prods), I'm +1. > > > Not to be a wet blanket, but I don't think we have any real data for > the production part of that. We could say the interfaces, > configuration and defaults are experimental in the volatile sense.
'prod-dev' ? :)
