Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:69526 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 6431 invoked from network); 9 Oct 2013 07:37:20 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 9 Oct 2013 07:37:20 -0000 Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.54 as permitted sender) X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.215.54 mail-la0-f54.google.com Received: from [209.85.215.54] ([209.85.215.54:42967] helo=mail-la0-f54.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 12/C5-06817-FA705525 for ; Wed, 09 Oct 2013 03:37:20 -0400 Received: by mail-la0-f54.google.com with SMTP id ea20so331816lab.13 for ; Wed, 09 Oct 2013 00:37:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Z5mfCqXUKEzyBW3gctUeBem1nwoGNjIHc+MOFg9hXzs=; b=KqUsoaoopSJJGB0Cv09Efqr8VuzyHsyKdxRVgYJeJGZ5vtefod4Vk7A3rAQ8R/MW92 b4v/JJ59ibgCVUN6mfLIqeQlRO9pidxFjhC7m7UV/6K3aFR0+EUeQQQ+zthZSvEgYiKk NKNKyskT0vW3b48UX7DNVJots3NsFQhj9z2dW2ih+TBd69oNgSyt9nh5utVjHRhD9xAC KvpkyobZLMuPAXx5tDYtja2sShjucpjS1amq/JoYiYO1R8l1LeNrV37WoJXSFlWDkfuS 8mU/jCIsbXpX/FI4moO0Z/03dNQBMJe7d0uXo5mQ6Ip1qjHv7/6f6zk+qSKRWbZo66AL p0Ig== MIME-Version: 1.0 X-Received: by 10.112.0.173 with SMTP id 13mr6113030lbf.8.1381304236304; Wed, 09 Oct 2013 00:37:16 -0700 (PDT) Received: by 10.112.148.138 with HTTP; Wed, 9 Oct 2013 00:37:16 -0700 (PDT) In-Reply-To: References: Date: Wed, 9 Oct 2013 09:37:16 +0200 Message-ID: To: Michael Wallner Cc: Martin Keckeis , Adam Harvey , PHP Internals Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [PHP-DEV] NEWS handling From: pierre.php@gmail.com (Pierre Joye) On Wed, Oct 9, 2013 at 9:07 AM, Michael Wallner wrote: >> 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 :) +1 And maybe we should begin to consider to force the new commit message format? (see https://wiki.php.net/vcs/gitworkflow#new_commit_message_format), may need a RFC and be done, almost :) -- Pierre @pierrejoye | http://www.libgd.org