You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Stefan Eissing <st...@greenbytes.de> on 2015/05/26 10:37:28 UTC
2.4 release backport list
Sorry, if this question has an obvious answer which I was unable to find: where would I find a list of the changes that will be backported to the 2.4.13 release in order to see if a change has received enough votes?
Thanks.
//Stefan
<green/>bytes GmbH
Hafenweg 16, 48155 Münster, Germany
Phone: +49 251 2807760. Amtsgericht Münster: HRB5782
Re: 2.4 release backport list
Posted by Stefan Eissing <st...@greenbytes.de>.
Flattery! (I experience I am not immune to this…)
Thanks for all the replies! I am currently making a patch that contains all the ALPN changes from trunk and works in 2.4. Hope that someone then can include this as proposal in the 2.4.13 STATUS. May it find votes!
Back soonish...
> Am 26.05.2015 um 11:42 schrieb Rainer Jung <ra...@kippdata.de>:
>
> Am 26.05.2015 um 11:07 schrieb Yann Ylavic:
>> Oups, several simultaneous responses...
>
> That shows how much we like him (his work) :)
<green/>bytes GmbH
Hafenweg 16, 48155 Münster, Germany
Phone: +49 251 2807760. Amtsgericht Münster: HRB5782
Re: 2.4 release backport list
Posted by Rainer Jung <ra...@kippdata.de>.
Am 26.05.2015 um 11:07 schrieb Yann Ylavic:
> Oups, several simultaneous responses...
That shows how much we like him (his work) :)
Re: 2.4 release backport list
Posted by Yann Ylavic <yl...@gmail.com>.
On Tue, May 26, 2015 at 2:26 PM, Yann Ylavic <yl...@gmail.com> wrote:
> On Tue, May 26, 2015 at 12:30 PM, Stefan Eissing
> <st...@greenbytes.de> wrote:
>> Thanks for the many answers!
>>
>> Now, can I win someone over to propose backporting the mod_ssl ALPN changes?
>
> Proposed in r1681749 by also including r1681741 (CHANGES entry) and
> r1681746 (revert on HTML docs changes).
> There is no vote for now though (I could not review it completely yet)...
Updated in r1681751 with patch v3 (without one remaining HAVE_TLS_NPN stuff).
Re: 2.4 release backport list
Posted by Stefan Eissing <st...@greenbytes.de>.
Thanks Yann!
> Am 26.05.2015 um 14:26 schrieb Yann Ylavic <yl...@gmail.com>:
>
> On Tue, May 26, 2015 at 12:30 PM, Stefan Eissing
> <st...@greenbytes.de> wrote:
>> Thanks for the many answers!
>>
>> Now, can I win someone over to propose backporting the mod_ssl ALPN changes?
>
> Proposed in r1681749 by also including r1681741 (CHANGES entry) and
> r1681746 (revert on HTML docs changes).
> There is no vote for now though (I could not review it completely yet)...
>
> Thanks for the work Stefan!
<green/>bytes GmbH
Hafenweg 16, 48155 Münster, Germany
Phone: +49 251 2807760. Amtsgericht Münster: HRB5782
Re: 2.4 release backport list
Posted by Yann Ylavic <yl...@gmail.com>.
On Tue, May 26, 2015 at 12:30 PM, Stefan Eissing
<st...@greenbytes.de> wrote:
> Thanks for the many answers!
>
> Now, can I win someone over to propose backporting the mod_ssl ALPN changes?
Proposed in r1681749 by also including r1681741 (CHANGES entry) and
r1681746 (revert on HTML docs changes).
There is no vote for now though (I could not review it completely yet)...
Thanks for the work Stefan!
Re: 2.4 release backport list
Posted by Yann Ylavic <yl...@gmail.com>.
On Tue, May 26, 2015 at 12:30 PM, Stefan Eissing
<st...@greenbytes.de> wrote:
>
> Now, can I win someone over to propose backporting the mod_ssl ALPN changes?
[to committers]
Who goes?
It would be funny to have 4 proposals though... :)
Re: 2.4 release backport list
Posted by Stefan Eissing <st...@greenbytes.de>.
Thanks for the many answers!
Now, can I win someone over to propose backporting the mod_ssl ALPN changes? I have prepared something:
* mod_ssl: add ALPN support by allowing other modules to register callbacks
for negotiation of the application layer protocol.
trunk patch: http://svn.apache.org/r1676709
http://svn.apache.org/r1676004
http://svn.apache.org/r1670578
http://svn.apache.org/r1675459
http://svn.apache.org/r1670436
http://svn.apache.org/r1670434
http://svn.apache.org/r1670397
http://svn.apache.org/r1332643
http://svn.apache.org/r1487772
http://svn.apache.org/r1332643
2.4.x patch: https://raw.githubusercontent.com/icing/mod_h2/master/sandbox/httpd/patches/httpd-2.4.x-alpn.patch
I tested today’s httpd/branches/2.4.x + patch with mod_h2 on OS X, using openssl 1.0.2. Works for me.
//Stefan
> Am 26.05.2015 um 11:07 schrieb Yann Ylavic <yl...@gmail.com>:
>
> Oups, several simultaneous responses...
> Hope too much information does not kill the information :p
>
> On Tue, May 26, 2015 at 11:03 AM, Yann Ylavic <yl...@gmail.com> wrote:
>> Hi Stefan,
>>
>> On Tue, May 26, 2015 at 10:37 AM, Stefan Eissing
>> <st...@greenbytes.de> wrote:
>>> Sorry, if this question has an obvious answer which I was unable to find: where would I find a list of the changes that will be backported to the 2.4.13 release in order to see if a change has received enough votes?
>>
>> Backports are proposed in the STATUS file of the target branch, where
>> each entry is removed once accepted and the backport is done.
>> There then only remains the CHANGES entry (if it was part of the
>> backport, but that's generally the case).
>>
>> But obviously, for a change to receive enough votes, it has first to
>> be proposed in STATUS...
>>
>> Regards,
>> Yann.
<green/>bytes GmbH
Hafenweg 16, 48155 Münster, Germany
Phone: +49 251 2807760. Amtsgericht Münster: HRB5782
Re: 2.4 release backport list
Posted by Yann Ylavic <yl...@gmail.com>.
Oups, several simultaneous responses...
Hope too much information does not kill the information :p
On Tue, May 26, 2015 at 11:03 AM, Yann Ylavic <yl...@gmail.com> wrote:
> Hi Stefan,
>
> On Tue, May 26, 2015 at 10:37 AM, Stefan Eissing
> <st...@greenbytes.de> wrote:
>> Sorry, if this question has an obvious answer which I was unable to find: where would I find a list of the changes that will be backported to the 2.4.13 release in order to see if a change has received enough votes?
>
> Backports are proposed in the STATUS file of the target branch, where
> each entry is removed once accepted and the backport is done.
> There then only remains the CHANGES entry (if it was part of the
> backport, but that's generally the case).
>
> But obviously, for a change to receive enough votes, it has first to
> be proposed in STATUS...
>
> Regards,
> Yann.
Re: 2.4 release backport list
Posted by Yann Ylavic <yl...@gmail.com>.
Hi Stefan,
On Tue, May 26, 2015 at 10:37 AM, Stefan Eissing
<st...@greenbytes.de> wrote:
> Sorry, if this question has an obvious answer which I was unable to find: where would I find a list of the changes that will be backported to the 2.4.13 release in order to see if a change has received enough votes?
Backports are proposed in the STATUS file of the target branch, where
each entry is removed once accepted and the backport is done.
There then only remains the CHANGES entry (if it was part of the
backport, but that's generally the case).
But obviously, for a change to receive enough votes, it has first to
be proposed in STATUS...
Regards,
Yann.
Re: 2.4 release backport list
Posted by Rainer Jung <ra...@kippdata.de>.
Hi Stefan,
Am 26.05.2015 um 10:37 schrieb Stefan Eissing:
> Sorry, if this question has an obvious answer which I was unable to find: where would I find a list of the changes that will be backported to the 2.4.13 release in order to see if a change has received enough votes?
The backports that are currently on vote are always in the STATUS file
which sits in the top level directory of the respective branch in svn.
For example:
http://svn.apache.org/viewvc/httpd/httpd/branches/2.4.x/STATUS?view=co
If an item has enough votes it is moved in the file from "PATCHES
PROPOSED TO BACKPORT FROM TRUNK:" to "PATCHES ACCEPTED TO BACKPORT FROM
TRUNK:". Next it gets applied to the code and removed from the file.
After the backport you can find the backported items in the CHANGES file
in svn (if the backport contains a user facing change). Most backports
also are done using "svn merge", so you can also look at the
svn:mergeinfo property of the top level directory of the branch. Finally
you can diff ...
Some parts can be applied without going through status, mostly docs
changes and some platform specific things.
All changes be it to STATUS, to CHANGES or some other files in svn are
mailed to cvs@httpd.apache.org to which you could subscribe, if you want
to follow more closely.
Regards,
Rainer
Re: 2.4 release backport list
Posted by Graham Leggett <mi...@sharp.fm>.
On 26 May 2015, at 10:37 AM, Stefan Eissing <st...@greenbytes.de> wrote:
> Sorry, if this question has an obvious answer which I was unable to find: where would I find a list of the changes that will be backported to the 2.4.13 release in order to see if a change has received enough votes?
Look in the STATUS file in the httpd v2.4 branch.
Similarly the STATUS file in other branches (eg v2.2) will list backport proposals there.
Regards,
Graham
—
Re: 2.4 release backport list
Posted by Nick Kew <ni...@webthing.com>.
On Tue, 26 May 2015 10:37:28 +0200
Stefan Eissing <st...@greenbytes.de> wrote:
> Sorry, if this question has an obvious answer which I was unable to find: where would I find a list of the changes that will be backported to the 2.4.13 release in order to see if a change has received enough votes?
The file STATUS in 2.4.x shows current votes.
(See also CHANGES, which documents what has already made it).
--
Nick Kew