Ideally, getting mod_h2 into users hands will be MUCH easier by focusing
on finishing up the 2.4 backporting... This out of the blue notice
to alpha 2.5 seems to me some method to stall or circumvent action in that
direction by changing the goalposts...
-0.9
On Aug 26, 2015, at 11:21 AM,
The faster early adopters can get us bug feedback, the faster the stable and
tested module can be backported to 2.4 without experimental warnings, IMO.
Nobody is going to do that. No one is going to run 2.5 alpha to
test h2 and http/2 when people were ALREADY using and testing
h2|http/2
On Wed, Aug 26, 2015 at 12:13 PM, Jim Jagielski j...@jagunet.com wrote:
Ideally, getting mod_h2 into users hands will be MUCH easier by focusing
on finishing up the 2.4 backporting... This out of the blue notice
to alpha 2.5 seems to me some method to stall or circumvent action in
that
On Aug 26, 2015, at 1:24 PM, William A Rowe Jr wr...@rowe-clan.net wrote:
On Wed, Aug 26, 2015 at 12:13 PM, Jim Jagielski j...@jagunet.com wrote:
Ideally, getting mod_h2 into users hands will be MUCH easier by focusing
on finishing up the 2.4 backporting... This out of the blue notice
to
I'm planning to tag trunk on 11 Sept to get 2.5.0 and mod_h2 into users
hands ASAP and collect feedback on that module ahead of any merges back
into the stable 2.4.x branch.
Concerns/Questions/Roadblocks/Showstoppers?
From my side it's a go ahead. We will obviously find bugs in such a new
module impacting potentially all requests, but the tests we have are stable.
So, I think, getting it into more peoples hands is the way forward.
Btw. if you review the core_protocols.patch and find anything preventing a
On 2015-08-26 17:21, William A Rowe Jr wrote:
I'm planning to tag trunk on 11 Sept to get 2.5.0 and mod_h2 into users
hands ASAP and collect feedback on that module ahead of any merges back
into the stable 2.4.x branch.
Concerns/Questions/Roadblocks/Showstoppers?
In case there will be a
