You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Jim Jagielski <ji...@jaguNET.com> on 2011/06/17 13:39:59 UTC
Time for httpd 2.3.13...? And 2.4.0??
Are we ready for the next beta release???
And Maybe Even The Next Release being GA??
Re: Time for httpd 2.3.13...? And 2.4.0??
Posted by Stefan Fritsch <sf...@sfritsch.de>.
On Sunday 19 June 2011, Kaspar Brand wrote:
> - don't do OCSP checks for valid self-issued certs
>
> - address PR 48215 ("Renegotiation with SSLVerifyDepth 0 requires
> multiple client authentication")
Committed as r1137394 and r1137398, thanks.
Re: Time for httpd 2.3.13...? And 2.4.0??
Posted by Stefan Fritsch <sf...@sfritsch.de>.
On Wednesday 22 June 2011, Jim Jagielski wrote:
> > Jim, do you have time to RM again?
>
> Yes, I plan to T&R mon or tues.
Cool, thanks in advance.
Re: Time for httpd 2.3.13...? And 2.4.0??
Posted by Jim Jagielski <ji...@jaguNET.com>.
On Jun 22, 2011, at 1:51 PM, Stefan Fritsch wrote:
> On Monday 20 June 2011, Jim Jagielski wrote:
>> On Jun 19, 2011, at 1:55 AM, Rainer Jung wrote:
>>> On 18.06.2011 14:44, Stefan Fritsch wrote:
>
>>>> +1 to 2.3.13 as beta. Then hopefully the next release can be GA.
>>>
>>> Agreed.
>>
>> Cool...
>
> Jim, do you have time to RM again?
Yes, I plan to T&R mon or tues.
Re: Time for httpd 2.3.13...? And 2.4.0??
Posted by Stefan Fritsch <sf...@sfritsch.de>.
On Monday 20 June 2011, Jim Jagielski wrote:
> On Jun 19, 2011, at 1:55 AM, Rainer Jung wrote:
> > On 18.06.2011 14:44, Stefan Fritsch wrote:
> >> +1 to 2.3.13 as beta. Then hopefully the next release can be GA.
> >
> > Agreed.
>
> Cool...
Jim, do you have time to RM again?
Cheers,
Stefan
Re: Time for httpd 2.3.13...? And 2.4.0??
Posted by Jim Jagielski <ji...@jaguNET.com>.
On Jun 19, 2011, at 1:55 AM, Rainer Jung wrote:
> On 18.06.2011 14:44, Stefan Fritsch wrote:
>> On Friday 17 June 2011, William A. Rowe Jr. wrote:
>>> On 6/17/2011 6:39 AM, Jim Jagielski wrote:
>>>> Are we ready for the next beta release???
>>>>
>>>> And Maybe Even The Next Release being GA??
>>>
>>> 2.3.13 soon, I'll fix the mod_ldap load ordering quirk on Sunday
>>> and just do a bit more validation with apr trunk.
>>
>> I am currently working on limiting the parallel connections per
>> process on MPM event (see STATUS). I would really like to have this in
>> 2.3.13, but I hope I will be able to finish it until tomorrow.
>>
>>> The Next Release? I'm not seeing enough activity on users@ and not
>>> even seeing current ASF infra updated enough to justify that ;-)
>>> But if 2.2.13 proves rock solid, maybe the subsequent release?
>>
>> +1 to 2.3.13 as beta. Then hopefully the next release can be GA.
>
> Agreed.
>
Cool...
Re: Time for httpd 2.3.13...? And 2.4.0??
Posted by Rainer Jung <ra...@kippdata.de>.
On 18.06.2011 14:44, Stefan Fritsch wrote:
> On Friday 17 June 2011, William A. Rowe Jr. wrote:
>> On 6/17/2011 6:39 AM, Jim Jagielski wrote:
>>> Are we ready for the next beta release???
>>>
>>> And Maybe Even The Next Release being GA??
>>
>> 2.3.13 soon, I'll fix the mod_ldap load ordering quirk on Sunday
>> and just do a bit more validation with apr trunk.
>
> I am currently working on limiting the parallel connections per
> process on MPM event (see STATUS). I would really like to have this in
> 2.3.13, but I hope I will be able to finish it until tomorrow.
>
>> The Next Release? I'm not seeing enough activity on users@ and not
>> even seeing current ASF infra updated enough to justify that ;-)
>> But if 2.2.13 proves rock solid, maybe the subsequent release?
>
> +1 to 2.3.13 as beta. Then hopefully the next release can be GA.
Agreed.
Rainer
Re: Time for httpd 2.3.13...? And 2.4.0??
Posted by Kaspar Brand <ht...@velox.ch>.
What about these two small fixes for mod_ssl (which I already tried to
push for 2.3.11)?
- don't do OCSP checks for valid self-issued certs
- address PR 48215 ("Renegotiation with SSLVerifyDepth 0 requires
multiple client authentication")
The complete message is attached again, but the gist for the first patch is:
> I don't mind adding support for trusted responders, but until that
> happens, I consider hard-coding mod_ssl to skip OCSP checks for valid
> self-signed certs a sensible choice.
Assuming that trusted responder support won't be added anytime
soon, it would make sense to get this in before 2.4 GA, IMO.
Kaspar
Re: Time for httpd 2.3.13...? And 2.4.0??
Posted by Stefan Fritsch <sf...@sfritsch.de>.
On Friday 17 June 2011, William A. Rowe Jr. wrote:
> On 6/17/2011 6:39 AM, Jim Jagielski wrote:
> > Are we ready for the next beta release???
> >
> > And Maybe Even The Next Release being GA??
>
> 2.3.13 soon, I'll fix the mod_ldap load ordering quirk on Sunday
> and just do a bit more validation with apr trunk.
I am currently working on limiting the parallel connections per
process on MPM event (see STATUS). I would really like to have this in
2.3.13, but I hope I will be able to finish it until tomorrow.
> The Next Release? I'm not seeing enough activity on users@ and not
> even seeing current ASF infra updated enough to justify that ;-)
> But if 2.2.13 proves rock solid, maybe the subsequent release?
+1 to 2.3.13 as beta. Then hopefully the next release can be GA.
Re: Time for httpd 2.3.13...? And 2.4.0??
Posted by "William A. Rowe Jr." <wr...@rowe-clan.net>.
On 6/17/2011 6:39 AM, Jim Jagielski wrote:
> Are we ready for the next beta release???
>
> And Maybe Even The Next Release being GA??
2.3.13 soon, I'll fix the mod_ldap load ordering quirk on Sunday and
just do a bit more validation with apr trunk.
The Next Release? I'm not seeing enough activity on users@ and not
even seeing current ASF infra updated enough to justify that ;-)
But if 2.2.13 proves rock solid, maybe the subsequent release?
Re: Time for httpd 2.3.13...? And 2.4.0??
Posted by Igor Galić <i....@brainsware.org>.
----- Original Message -----
> Are we ready for the next beta release???
>
> And Maybe Even The Next Release being GA??
I'd say we give it another Beta. I think it also might be a good sign
if we updated eos.apache.org to the latest release to assure ourselves
and others of our confidence in the release.
It doesn't have to be a long sprint, if we're happy with the beta,
we can go straight for GA in ~two or so weeks.
i
--
Igor Galić
Tel: +43 (0) 664 886 22 883
Mail: i.galic@brainsware.org
URL: http://brainsware.org/