Re: NEWS handling
| From: | Adam Harvey | Date: | Wed, 09 Oct 2013 07:16:46 +0000 |
| Subject: | Re: NEWS handling | ||
| References: | 1 2 3 4 5 6 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-69524@lists.php.net to get a copy of this message | ||
On 9 October 2013 00:07, Michael Wallner <mike@php.net> wrote:
> Okay -- looking at NEWS.GIT-RULES it actually says the opposite:
>
> 2. All news updates intended for public viewing, such as new features,
> bug fixes, improvements, etc., should go into the NEWS file of the
> *first* to be released version with the given change. In other words
> any NEWS file change only needs to done in one branch.
>
> How about changing it to:
>
> 2. All news updates intended for public viewing, such as new features,
> bug fixes, improvements, etc., should go into the NEWS file of *any
> stable release* version with the given change. In other words,
> news about a bug fix which went into PHP-5.4, PHP-5.5 and master
> should be noted in both PHP-5.4/NEWS and PHP-5.5/NEWS but
> not master, which is not a public released version yet.
+1. Copying the NEWS entry across is pretty easy when merging upwards,
even if you're using the touch driver for NEWS.
Adam