Re: drop experimental from http2 for 2.4.next?

I was talking about the way ahead for HTTP/2 support in httpd. Regarding it as no longer "experimental" helps, I hope, to make better progress on this. There have been two aspects to "experimental" in my mind: 1. The "we do not guarantee that this is how it will stay". Anything may change

Re: drop experimental from http2 for 2.4.next?

On Mon, Apr 17, 2017 at 4:24 AM, Stefan Eissing wrote: > What needs to be done? From what I saw in the last two years, these > are key areas to improve: > > 1. separation of semantics and serialisation > 2. connections with >1 requests simultaneously > > mod_http

Re: drop experimental from http2 for 2.4.next?

Do we foresee an issue w/ it moving to RTC? I don't... I think we could get the required 3 +1s quite easily. > On Apr 18, 2017, at 2:35 PM, Eric Covener wrote: > > On Sat, Apr 15, 2017 at 8:15 PM, Nick Kew wrote: >> Why would it be good for a stable (i.e.

Re: drop experimental from http2 for 2.4.next?

On Sat, Apr 15, 2017 at 8:15 PM, Nick Kew wrote: > Why would it be good for a stable (i.e. non-experimental) > component of httpd to have an entirely different commit > policy to the project as a whole? Surely the CTR is in > recognition of its experimental status, to lubricate

Re: drop experimental from http2 for 2.4.next?

On 17 Apr 2017, at 10:24 AM, Stefan Eissing wrote: > These modules, they grow up so fast... > > For the project, it would be good to drop that "experimental" and > treat HTTP/2 as an integral part of httpd. Not only for political > posturing (which is important),

Re: drop experimental from http2 for 2.4.next?

On 15 Apr 2017, at 11:02 PM, Eric Covener wrote: > Hi everyone, shall we drop experimental from mod_http2 for 2.4.next? +1. > We could drop it and keep CTR. It can’t be not-experimental and CRT at the same time. Regards, Graham — smime.p7s Description: S/MIME

Re: drop experimental from http2 for 2.4.next?

On 04/16/2017 02:15 AM, Nick Kew wrote: > On Sat, 2017-04-15 at 17:02 -0400, Eric Covener wrote: >> Hi everyone, shall we drop experimental from mod_http2 for 2.4.next? >> >> We could drop it and keep CTR. >> > Why would it be good for a stable (i.e. non-experimental) > component of httpd to

Re: drop experimental from http2 for 2.4.next?

On 04/17/2017 01:24 AM, Stefan Eissing wrote: As much as I like to work on it, I am certainly not able to do that by myself. So, yes, I welcome getting rid of experimental. Sounds good to me. I agree with Nick that we should probably switch to RTC at the same time, for backports to 2.4.x.

Re: drop experimental from http2 for 2.4.next?

These modules, they grow up so fast... For the project, it would be good to drop that "experimental" and treat HTTP/2 as an integral part of httpd. Not only for political posturing (which is important), but also for very technical reasons. Looking at

Re: drop experimental from http2 for 2.4.next?

Agreed. The "tag" is being used to keep it out of distros as well as to continue the FUD that httpd doesn't "really" support http/2. > On Apr 15, 2017, at 5:02 PM, Eric Covener wrote: > > Hi everyone, shall we drop experimental from mod_http2 for 2.4.next? > > We could drop

Re: drop experimental from http2 for 2.4.next?

On Sat, 2017-04-15 at 17:02 -0400, Eric Covener wrote: > Hi everyone, shall we drop experimental from mod_http2 for 2.4.next? > > We could drop it and keep CTR. > Why would it be good for a stable (i.e. non-experimental) component of httpd to have an entirely different commit policy to the

drop experimental from http2 for 2.4.next?

Hi everyone, shall we drop experimental from mod_http2 for 2.4.next? We could drop it and keep CTR. -- Eric Covener cove...@gmail.com