Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:69517
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain adamharvey.name designates 209.85.214.169 as permitted sender)
MIME-Version: 1.0
Sender: adam@adamharvey.name
In-Reply-To: <CALJZF3guxb3FOHYF2LGnevjuUfXg28pkkXT_5+Bqmv6m9b7KYQ@mail.gmail.com>
References: <CALJZF3guxb3FOHYF2LGnevjuUfXg28pkkXT_5+Bqmv6m9b7KYQ@mail.gmail.com>
Date: Tue, 8 Oct 2013 10:09:49 -0700
Message-ID: <CADajX4CHpCPS-=x1X+c+-ZQ3_7QnH0e0+bXi8-Q1NxYyapks0w@mail.gmail.com>
To: Michael Wallner <mike@php.net>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] NEWS handling
From: aharvey@php.net (Adam Harvey)

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 =E2=80=94 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.

Adam