Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:107934 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 92369 invoked from network); 20 Dec 2019 10:36:58 -0000 Received: from unknown (HELO php-smtp3.php.net) (208.43.231.12) by pb1.pair.com with SMTP; 20 Dec 2019 10:36:58 -0000 Received: from php-smtp3.php.net (localhost [127.0.0.1]) by php-smtp3.php.net (Postfix) with ESMTP id 2D9192C05E2 for ; Fri, 20 Dec 2019 00:37:31 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp3.php.net X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_HELO_NONE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS8560 212.227.0.0/16 X-Spam-Virus: No Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by php-smtp3.php.net (Postfix) with ESMTPS for ; Fri, 20 Dec 2019 00:37:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1576831048; bh=go/YoJdEfaQr/7iGm3cKHA3i6DshZmQyGBDXFQNOo5I=; h=X-UI-Sender-Class:Subject:To:References:From:Date:In-Reply-To; b=JxcEDmEkujNZAdMchjKg7TZGwFvl0iYi6WNp6C1dqZvVC2GHcSWsoXgH4TJCRvTtY 1R748bvMdIrQG6k1/KaUAMPrBi+JGRP01dxa6DkySHqgoj849u7T8EjiOk0gu8ynzz sFlCs1XP3UFoaBURKEhoPFShQi6n2BaR8wEjdeOs= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Received: from [192.168.2.130] ([84.179.229.4]) by mail.gmx.com (mrgmx105 [212.227.17.168]) with ESMTPSA (Nemesis) id 1N17YY-1hgw1y11ze-012U1G; Fri, 20 Dec 2019 09:37:28 +0100 To: =?UTF-8?B?TcOhdMOpIEtvY3Npcw==?= , internals@lists.php.net References: Message-ID: Date: Fri, 20 Dec 2019 09:37:27 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: de-DE Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:0PkGO2hezZUadV7pm0Sji4heVrOQlRUxznewHxmPR6/Owiu6InW +rvHhn2TtXtB2rPeKitrbdihk/Ffp8JwoCsRkn1G+olUvJBvJiSK0Y9dwSFDrWa3YbBHjUT 3xYoIklyZ0MJV0dOYbcV7OI8jVTko/iw13S2FZsjGKPYciNLSTrY1fQ+NYDdeLx2Tqojwpa tvUCA+GwVpimO47RFrRsQ== X-UI-Out-Filterresults: notjunk:1;V03:K0:nQcJe2k2Vrw=:fCJ/oW2QiInVWJFG7Ox+u0 FtvY244w5/osSgA/KT79Z6VdVpAjX3xKzA+anpOfms4EG3SErrAe8VKGW74FKl7Y+XVMh64nY wkqgMqaNIaRUTb9dg9mfklZ8B1oMphnZQheW/UtNOCclUEsWNU5vDQKopmw8XGhik/wC2DF4T KYrb2iNbYibKitOPfcMPJ3tcSj3MLWY8Knk4BW1IdkKzsGc6dzWaRpbSE/thbSQvdUIbQlnq2 xqDgdMbExEldFmvirLabhDkUrTy1Yd4PqvHqAmPAJD+zPv3N8/nGbQ3LW2GPcw2ypD0rXHfes PAQUy7JJnBRegx4uWb0G7YisTCYUWcY5CBkyFkgkiTLva7CyweHTuqv8x/k5OMX04JawQ+3Cd eU7NFWVsGx3aq8rXtqsY0U/ISo+EjX5NAmjf2Adwqf1NKaDvs0d1lkgozVzD3KG/rHR1+2i8L kQrUq2rd6sbFVSI+oKrT8RPZBvcOdJi8idPIVU72qo5r/AYjkVn/AixPrD8zEBtAo+syLcv37 LZFxOvfSenb6XQvnMZz0W8HrPSw7tChotryUvPHEJd19NLHWOXHZiu48iHv+8kpOLW4nnQ58n GMEnL/nxFyfzHtX3WrLLvpJrFHxgqQ4VV1wo4hffVJJkjo9ocX9yGQY+BiWPYLfYIXzCJ2wpK VdEDfO419jsmA5dTaV5yb4jSl0mpD8qaCTKh2tTJ9l8nQ1tZFq5PhxroUwyaXihk6l++Zxwdr lrRiDJ1i0oLZTYrx38XKddpQSaMzfyglQ9jxBWb2LQUDG0tdedVuDc6qvcdbEmWtDnGN8XX+K aV1S56p2QGQW3QjRy9YkmiLAf2BFjT6wPE3xDofHmctYzX3+q1qLb0vw/9Ngx3jebaEwN8z2G dpBcCy39Pkm9UnEQ7E2k/5CopfdhI5m+IFXCZOmM9V63GArODLZcA4As9oEgzYpeH9kcJ74ZY NPT2MaWM3b/NgKtc4R+YoGSaSR981PClFHQTDX8UhejJ28NbHP2uZ2uLEh/rz9T9iypLl3AF0 ANXdDHWzSnrTbfN5o+BQOwaY2EgJmKuF0zzxnWqoaw8imm1FO8y9LgtevmMCehyIq0qL5h7H9 TAnAoW/erO2fdvjflSFl5tFJdMHdZmx80PVxnuFcEpL4pfj9c6yOOyyZCKmv7AD0G205AvkQZ KU9bMbkufknq+TRuSu2qJ48lGfimO3KtOATKFzIpwSWamLBTmP16XXykOJXjozflaD+EknDtD GorOq7S9sqIplqsI3SFwqf9Qa8J2JSw4sIMPwBAh7w480HlvhexK9kb57m1U= X-Envelope-From: Subject: Re: Changelog / upgrading notes for promoted warnings From: cmbecker69@gmx.de ("Christoph M. Becker") On 20.12.2019 at 00:05, M=C3=A1t=C3=A9 Kocsis wrote: > Although, the only problem I have with including every promoted warning = in > the upgrading notes > is that doing so would possibly cannibalise it as there are dozens (if n= ot > hundreds) of > promotions that have already taken place... > > Nevertheless, I'm happy to help collecting the converted warnings and > putting the list in either > the upgrading notes or any other place - whatever is going to be decided= . Maybe a sensible compromise would be to assemble a detailed list of these changes, and to hand it over to the doc team at some point, so that the manual pages could (hopefully) be updated in time just before PHP 8.0.0 will be released. Then users could check the manual's changelog[1] regarding the details. [1] =2D- Christoph M. Becker