Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:69519
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.49 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CADajX4CHpCPS-=x1X+c+-ZQ3_7QnH0e0+bXi8-Q1NxYyapks0w@mail.gmail.com>
References: <CALJZF3guxb3FOHYF2LGnevjuUfXg28pkkXT_5+Bqmv6m9b7KYQ@mail.gmail.com>
	<CADajX4CHpCPS-=x1X+c+-ZQ3_7QnH0e0+bXi8-Q1NxYyapks0w@mail.gmail.com>
Date: Wed, 9 Oct 2013 04:32:53 +0200
Message-ID: <CAEZPtU44LOVMqRPE=MnkC-mUzrDZ2jV6iL9CPO48ac+ez42hEA@mail.gmail.com>
To: Adam Harvey <aharvey@php.net>
Cc: Michael Wallner <mike@php.net>, PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] NEWS handling
From: pierre.php@gmail.com (Pierre Joye)

On Tue, Oct 8, 2013 at 7:09 PM, Adam Harvey <aharvey@php.net> wrote:
> On 8 October 2013 06:46, Michael Wallner <mike@php.net> wrote:
>> I was wondering how we are supposed to handle NEWS entries when a fix
>> goes into both branches, PHP-5.4 and 5.5. IIRC we used to add the BFN
>> only to the lowest numbered branch, but then again that was at times
>> we had mostly onle one stable release branch...
>
> The way I've done it (and it seems like most developers are doing it
> now) is to add the same entry to each stable branch as I merge
> upwards, so the 5.4 and 5.5 NEWS files each end up with something
> like:
>
> - Extension:
>   . Fixed bug #12345 (luggage combination is weak). (Adam)
>
> I think the bug number really has to be in each branch for the NEWS
> file to be useful =97 users need to be able to find out at a glance
> what's been fixed from 5.5.4 to 5.5.5, for instance.

agreed.

I never really liked the "lowest branch" only way, too confusing and
hard to see what was fixed where.

Cheers,
--=20
Pierre

@pierrejoye | http://www.libgd.org