Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:107496 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 60464 invoked from network); 11 Oct 2019 13:18:20 -0000 Received: from unknown (HELO php-smtp3.php.net) (208.43.231.12) by pb1.pair.com with SMTP; 11 Oct 2019 13:18:20 -0000 Received: from php-smtp3.php.net (localhost [127.0.0.1]) by php-smtp3.php.net (Postfix) with ESMTP id 440BA2D203B for ; Fri, 11 Oct 2019 04:01:28 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp3.php.net X-Spam-Level: X-Spam-Status: No, score=-0.6 required=5.0 tests=BAYES_05,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,SPF_HELO_NONE,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS42831 5.101.168.0/21 X-Spam-Virus: No Received: from bard.thewebhostserver.com (bard.thewebhostserver.com [5.101.174.41]) (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, 11 Oct 2019 04:01:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lsces.uk; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version :Date:Message-ID:From:References:To:Subject:Sender:Reply-To:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=3lT9OxDm8V27okcqa0h8V135z0wSI+0yQF6HL4yZONo=; b=lAMyGc9+ZVxMEkhoPkopHuE2bA sZU4TAxcg575Jsd1yxSkYafm/WTa617jtgiyUXK+wrLUgDQKUSfmhCkWIk5TmKX3aQiWkmlKvObFp Qy+vua1lk4qvy8Pxvgx05q59rdPR5g667Ee9/YcuXlt35+OUF4QqvZobAChAaCCOaGJ/my8eLi4Ei C0Qp2lU8SzmUsikuKrtYwXov52cbnZsZe93ZfDqcFR4Q7xcJHdLIfUeOF0uccRKMUd3DK9DpePKQl 32FOLFYvLwS3sdzzxVZTazjwNUwixwKYv67jtK8/9WtjHvndjquoVY1LI50LLK/J1affZgqrvXIaO Ze7RSYcA==; Received: from [185.69.145.106] (port=21011 helo=[192.168.43.78]) by bard.thewebhostserver.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.92) (envelope-from ) id 1iIsfj-0085eO-V9 for internals@lists.php.net; Fri, 11 Oct 2019 12:01:24 +0100 To: internals@lists.php.net References: Message-ID: Date: Fri, 11 Oct 2019 12:01:09 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.1.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-thewebhostserver-MailScanner-Information: Please contact the ISP for more information X-thewebhostserver-MailScanner-ID: 1iIsfj-0085eO-V9 X-thewebhostserver-MailScanner: Found to be clean X-thewebhostserver-MailScanner-SpamCheck: X-thewebhostserver-MailScanner-From: lester@lsces.uk X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - bard.thewebhostserver.com X-AntiAbuse: Original Domain - lists.php.net X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - lsces.uk X-Get-Message-Sender-Via: bard.thewebhostserver.com: authenticated_id: lester@lsces.uk X-Authenticated-Sender: bard.thewebhostserver.com: lester@lsces.uk X-Envelope-From: Subject: Re: [PHP-DEV] Migration tooling and the cumulative cost of purely syntactical deprecations From: lester@lsces.uk (Lester Caine) On 11/10/2019 11:25, Nikita Popov wrote: > If we provide this kind of tooling, I think that the cost/benefit > calculation on deprecation changes: If we have any syntactic deprecations > at all, then it basically doesn't matter how many different (syntactical) > things get deprecated in one release, the migration cost is always going to > be the same. (This is of course a slightly simplified view, but close > enough.) A practical example ... I've just sorted out access to a new clients web hosting and fixed things so I can actually log into the wordpress admin panel. Since there has been no access since the previous support person who set up the site went awall there are a lot of messages to deal with. The first one being that PHP is out of date so wordpress can't upgrade. THAT is good to see since I already know that the site will be broken if it HAD simply updated as has happened on other sites! The question now is just what process to follow to update without taking the site off-line. This is not something the sites owner would ever be able to handle hence the request to help out ... In the case of wordpress, the next problem is working out just what plugins are currently active, which ones will work if wordpress is updated, and which may need to be replaced. But the starting point is what will happen if I start by switching PHP5.5 to PHP5.6 so that wordpress can be updated at all. Should I simply move direct to 7.2 which I have other wordpress sites running on and crib sheets to help fixing the problems I have already tracked. None of this can be sorted by using tools that fix the raw code. The only route is via third party upgrades which relate to which version of PHP is running. *IF* php was a lot more stable when RUNNING older code then one COULD simply update the version and then play catch-up with other updates, but with the current situation, one often has to fix raw code problems to get the older stable site into a state that the upgrade process will actually work. Bottom line ... can I justify a decent price for the time sorting all of this will take when there is no indication just how long it WILL take, and then what work will be required in addition to simply removing the nannying messages from wordpress ... -- Lester Caine - G8HFL ----------------------------- Contact - https://lsces.uk/wiki/Contact L.S.Caine Electronic Services - https://lsces.uk Model Engineers Digital Workshop - https://medw.uk Rainbow Digital Media - https://rainbowdigitalmedia.uk