Re: NEWS handling

Hello togehter, 2013/10/9 Pierre Joye <pierre.php@gmail.com> > 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 — 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, > -- > Pierre > > @pierrejoye | http://www.libgd.org > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > As more or less a "enduser" i have to agree. Writing in both is the easiest way, to get a "quick" overview what is releavant.