Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Message-ID: <556436DF.1050306@kippdata.de>
Date: Tue, 26 May 2015 11:03:27 +0200
From: Rainer Jung <rainer.jung@kippdata.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: dev@httpd.apache.org
Subject: Re: 2.4 release backport list
References: <A5FF9249-3038-47C5-9EBF-FDD36E5CE5EE@greenbytes.de>
In-Reply-To: <A5FF9249-3038-47C5-9EBF-FDD36E5CE5EE@greenbytes.de>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

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