Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:69523 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 96593 invoked from network); 9 Oct 2013 07:07:13 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 9 Oct 2013 07:07:13 -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.215.48 as permitted sender) X-PHP-List-Original-Sender: mike.php.net@gmail.com X-Host-Fingerprint: 209.85.215.48 mail-la0-f48.google.com Received: from [209.85.215.48] ([209.85.215.48:54500] helo=mail-la0-f48.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id FB/A3-06817-F9005525 for ; Wed, 09 Oct 2013 03:07:11 -0400 Received: by mail-la0-f48.google.com with SMTP id er20so307751lab.35 for ; Wed, 09 Oct 2013 00:07:08 -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; bh=o5U4qKPF3F4kUKF2KKOYFB96tnpNq5svzbfWatnMJcM=; b=fJ7rk+9/j3TQjWUY9MrpmHO+nvJ90x1+Y0gkdN8ko+yEXygYhq497BOIGBGpuf2iX7 HABly5ZX7csKxBy5/bmUHSb5yODSKgnd2QyGB7P+mzelhtfkKpEgloYlApppkbZqpMlG 3RJnJZ+cknOJzucveoEiV0874aDQ/0j4Q2oTeQYCcvyZlqYYLmy3JlGTlG50f/0j6j+/ LlKh7vut724epjNBAOjdw8RMX1XakvqevB1AN+AIbL03W3gDdgV67GTHYUbKm2i2lEsU okTI6n5Zga1kMEQWovF+/gZkAoEeLSwBMFtt0/cugdGYPRZCTaZQvk34RiQ4sFOYxylk vJNQ== MIME-Version: 1.0 X-Received: by 10.112.190.1 with SMTP id gm1mr5939329lbc.30.1381302428370; Wed, 09 Oct 2013 00:07:08 -0700 (PDT) Sender: mike.php.net@gmail.com Received: by 10.114.184.19 with HTTP; Wed, 9 Oct 2013 00:07:08 -0700 (PDT) In-Reply-To: References: Date: Wed, 9 Oct 2013 09:07:08 +0200 X-Google-Sender-Auth: vooa9TKY6riza_3KCO9qPfKC8e4 Message-ID: To: Martin Keckeis Cc: Pierre Joye , Adam Harvey , PHP Internals Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] NEWS handling From: mike@php.net (Michael Wallner) > Thanks for your feedback! I fixed NEWS for the upcoming releases. > Please let us have an eye on it in the future! 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. PS: I post that for other people that had not time to notice this discussion and I will most probably give a week or so for others to speek up before changing any settled rules. Could well be there are people who do not want to write two NEWS entries :) -- Regards, Mike