Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:103068
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmx.de designates 212.227.17.20 as permitted sender)
To: Stanislav Malyshev <smalyshev@gmail.com>,
 PHP internals <internals@lists.php.net>
References: <87f6edc8-a6a8-cf0e-5b48-4f407e652b79@gmx.de>
 <a9b38508-2def-cab2-baf4-c104ee8167df@gmail.com>
Message-ID: <dc9e783a-0bbd-bcac-0c55-2df5910ab27e@gmx.de>
Date: Thu, 9 Aug 2018 00:29:59 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101
 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <a9b38508-2def-cab2-baf4-c104ee8167df@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: de-DE
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] NEWS vs. UPGRADING
From: cmbecker69@gmx.de ("Christoph M. Becker")

On 08.08.2018 at 00:04, Stanislav Malyshev wrote:

>> Do we have clear rules which changes are supposed to be listed in NEWS,
>> and which ones in UPGRADING?
> 
> Bugfixes to bugs in the bug tracker and other bugs worth mentioning go
> to NEWS, so do substantial enhancements.
> 
> Stuff affecting BC goes to UPGRADING, and also everything that fits into
> the categories on top of UPGRADING file, with the focus on things that
> people would want to know upgrading between minor versions (7.x ->
> 7.x+1) or between majors of course.

Thanks, Stas!  That's suitable.

-- 
Christoph M. Becker