Re: 2.4.x and 2.6.x ... next steps

I should have read this (shorter) reply first :) Le 12/09/2018 à 03:30, William A Rowe Jr a écrit : On Tue, Sep 11, 2018, 13:35 Jim Jagielski > wrote: And finally, we have some things in trunk that will likely need to be majorly fixed or else scrapped.

Re: 2.4.x and 2.6.x ... next steps

Le 12/09/2018 à 03:15, William A Rowe Jr a écrit : On Tue, Sep 11, 2018, 17:42 Graham Leggett > wrote: On 11 Sep 2018, at 20:35, Jim Jagielski wrote: > This is what I propose: > >  o Later on this week I svn cp trunk over to branches/2.5.x -1 ...

Re: 2.4.x and 2.6.x ... next steps

Le 12/09/2018 à 00:25, Yann Ylavic a écrit : Possibly: https://lists.apache.org/thread.html/%3ccakq1svnw_vdpbzk6c+f30y5nbhhosbbwt_fubttsnc+r7mb...@mail.gmail.com%3E ? That was a proposal (nothing committed), I don't think the regression suspected by Bill was there, but had to work on

Re: 2.4.x and 2.6.x ... next steps

On Tue, Sep 11, 2018, 13:35 Jim Jagielski wrote: > > And finally, we have some things in trunk that will likely > need to be majorly fixed or else scrapped. > Please catalog these things. The reason that even-odds minor versions exist is to clean up trunk for a GA release. Otherwise we would

Re: 2.4.x and 2.6.x ... next steps

On Tue, Sep 11, 2018, 17:42 Graham Leggett wrote: > On 11 Sep 2018, at 20:35, Jim Jagielski wrote: > > > This is what I propose: > > > > o Later on this week I svn cp trunk over to branches/2.5.x > -1 ... Veto on the basis of project bylaws. Propose a revision for voting. > o That branch

Re: 2.4.x and 2.6.x ... next steps

On 11 Sep 2018, at 20:35, Jim Jagielski wrote: > This is what I propose: > > o Later on this week I svn cp trunk over to branches/2.5.x > o That branch becomes the initial source for 2.6.x > o trunk remains CTR, whereas branches/2.5.x becomes RTC >ala 2.4.x (ie: using STATUS and

Re: 2.4.x and 2.6.x ... next steps

On Tue, Sep 11, 2018 at 10:07 PM Christophe JAILLET wrote: > > Le 11/09/2018 à 20:35, Jim Jagielski a écrit : > > I'd like for us to seriously consider the next steps > > related to the future of httpd. ++1 > > This is what I propose: > > > >o Later on this week I svn cp trunk over to

Re: 2.4.x and 2.6.x ... next steps

> + clearly document the changes in 2.4 -> 2.5/2.6, to start building the > next https://httpd.apache.org/docs/current/upgrading.html. as well as docs/manual/new_features_2.5.xml I am not sure 2.6 has much to offer. But it's a bit of a chicken-and-egg problem I guess. -- Eric Covener

Re: 2.4.x and 2.6.x ... next steps

Le 11/09/2018 à 20:35, Jim Jagielski a écrit : I'd like for us to seriously consider the next steps related to the future of httpd. In trunk we have some stuff that can be easily, or, at least, *somewhat* easily backported to 2.4.x, and I personally think that we should do that. +1 But we

2.4.x and 2.6.x ... next steps

I'd like for us to seriously consider the next steps related to the future of httpd. In trunk we have some stuff that can be easily, or, at least, *somewhat* easily backported to 2.4.x, and I personally think that we should do that. But we also have some items which cannot be backported due to

Re: svn commit: r1840585 - in /httpd/httpd/trunk: docs/log-message-tags/next-number modules/ssl/ssl_engine_kernel.c

On Tue, Sep 11, 2018 at 06:35:17PM +0200, Yann Ylavic wrote: > On Tue, Sep 11, 2018 at 6:01 PM wrote: > > > > Author: jorton > > Date: Tue Sep 11 16:01:47 2018 > > New Revision: 1840585 > > > > URL: http://svn.apache.org/viewvc?rev=1840585=rev > > Log: > > * modules/ssl/ssl_engine_kernel.c

Re: svn commit: r1840585 - in /httpd/httpd/trunk: docs/log-message-tags/next-number modules/ssl/ssl_engine_kernel.c

On Tue, Sep 11, 2018 at 6:01 PM wrote: > > Author: jorton > Date: Tue Sep 11 16:01:47 2018 > New Revision: 1840585 > > URL: http://svn.apache.org/viewvc?rev=1840585=rev > Log: > * modules/ssl/ssl_engine_kernel.c (ssl_hook_Access_modern): Fail with > 403 if SSL_verify_client_post_handshake()

Speakers needed for Apache DC Roadshow

We need your help to make the Apache Washington DC Roadshow on Dec 4th a success. What do we need most? Speakers! We're bringing a unique DC flavor to this event by mixing Open Source Software with talks about Apache projects as well as OSS CyberSecurity, OSS in Government and and OSS Career

Speakers needed for Apache DC Roadshow

We need your help to make the Apache Washington DC Roadshow on Dec 4th a success. What do we need most? Speakers! We're bringing a unique DC flavor to this event by mixing Open Source Software with talks about Apache projects as well as OSS CyberSecurity, OSS in Government and and OSS Career

Re: TLSv1.3 supprt for 2.4.x?

On Tue, Sep 11, 2018 at 03:39:42PM +0200, Yann Ylavic wrote: > On Tue, Sep 11, 2018 at 12:13 PM Joe Orton wrote: > > > > Does anybody have successful test results with post-handshake auth? I'm > > testing against Fedora's OpenSSL 1.1.1pre9 which has merged the changes > > for

Re: TLSv1.3 supprt for 2.4.x?

On Tue, Sep 11, 2018 at 12:13 PM Joe Orton wrote: > > Does anybody have successful test results with post-handshake auth? I'm > testing against Fedora's OpenSSL 1.1.1pre9 which has merged the changes > for https://github.com/openssl/openssl/issues/6933 Just tried trunk+openssl-1.1.1pre9

Re: 2.4.35 in Sept?

If there is still interest, there are a handful of useful backports in STATUS that could use review, testing and voting :-) > On Aug 29, 2018, at 10:10 AM, Jim Jagielski wrote: > > Looking to maybe do an interim release in Sept... > > Comments? Feedback?

Re: TLSv1.3 supprt for 2.4.x?

On Tue, Sep 11, 2018 at 10:42:02AM +0200, Stefan Eissing wrote: > > Am 10.09.2018 um 10:59 schrieb Joe Orton : > > http://svn.apache.org/viewvc?view=revision=1828220 > > - I think this is merged in the branch slightly differently? > > I think this overlaps with a subsequent change of

Re: TLSv1.3 supprt for 2.4.x?

> Am 10.09.2018 um 10:59 schrieb Joe Orton : > > On Wed, Sep 05, 2018 at 01:36:06PM +0200, Stefan Eissing wrote: >> A member of the OpenSSL project gave me a "go ahead" and we now have branch: >> >> https://svn.apache.org/repos/asf/httpd/httpd/branches/tlsv1.3-for-2.4.x >> >> as a copy of