Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:69522 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 91188 invoked from network); 9 Oct 2013 06:18:50 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 9 Oct 2013 06:18:50 -0000 Authentication-Results: pb1.pair.com header.from=mike.php.net@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=mike.php.net@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.177 as permitted sender) X-PHP-List-Original-Sender: mike.php.net@gmail.com X-Host-Fingerprint: 209.85.217.177 mail-lb0-f177.google.com Received: from [209.85.217.177] ([209.85.217.177:53298] helo=mail-lb0-f177.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id BF/A2-06817-945F4525 for ; Wed, 09 Oct 2013 02:18:50 -0400 Received: by mail-lb0-f177.google.com with SMTP id w7so359161lbi.36 for ; Tue, 08 Oct 2013 23:18:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=V9skE1M3DOFZWVbuxOfnGD6mZTg6FapSamb3ni93464=; b=YzwoKFiyhJu+04v3xO3GVy1HT/xE2+mYXePEkGRXsGEclztb2yz92Nj4C1qX3xBo5q q5StDR7Ze80XKxrxk1kiHAlEFCv4muAx/0hW8KeSNECDkcjdT1TrGXXf0FptEgE/I1dv Ixa6ryJ8xqG+SV31rERyRRRfRHoJ+UJHDOL7bkjan1iBse798Zg3Qy61ufLjcYf0dxH/ RBcYrDr4bRcLQWH3MkcBO53mtJjznsFFlxl925wZMUm3U9u+wkeYixOQ2yk4P8nHMTDE qC8y87SIf56Ukx/e2TZgqo1KLutCkl5gLg6TGLhkC4PsDydL7F8oUApGdq5b8gpkXwI+ nPgg== MIME-Version: 1.0 X-Received: by 10.152.116.109 with SMTP id jv13mr4895539lab.30.1381299526976; Tue, 08 Oct 2013 23:18:46 -0700 (PDT) Sender: mike.php.net@gmail.com Received: by 10.114.184.19 with HTTP; Tue, 8 Oct 2013 23:18:46 -0700 (PDT) In-Reply-To: References: Date: Wed, 9 Oct 2013 08:18:46 +0200 X-Google-Sender-Auth: 9HnZtlQfJm5oGnVBDte7LCn82kg Message-ID: To: Martin Keckeis Cc: Pierre Joye , Adam Harvey , PHP Internals Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] NEWS handling From: mike@php.net (Michael Wallner) On 9 October 2013 08:01, Martin Keckeis wrote: > Hello togehter, > > 2013/10/9 Pierre Joye >> >> On Tue, Oct 8, 2013 at 7:09 PM, Adam Harvey wrote: >> > On 8 October 2013 06:46, Michael Wallner 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 gla= nce >> > 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 easie= st > way, to get a "quick" overview what is releavant. > Thanks for your feedback! I fixed NEWS for the upcoming releases. Please let us have an eye on it in the future! --=20 Regards, Mike