Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:119902 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 50271 invoked from network); 11 Apr 2023 09:09:40 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 11 Apr 2023 09:09:40 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id E923F1804D7 for ; Tue, 11 Apr 2023 02:09:36 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-0.5 required=5.0 tests=BAYES_05,RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from mail-wr1-f48.google.com (mail-wr1-f48.google.com [209.85.221.48]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Tue, 11 Apr 2023 02:09:36 -0700 (PDT) Received: by mail-wr1-f48.google.com with SMTP id e2so6723978wrc.10 for ; Tue, 11 Apr 2023 02:09:36 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1681204175; h=message-id:in-reply-to:to:references:date:subject:mime-version :content-transfer-encoding:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=l0WlqUFeIoC67bWY7Fev1QDWM5xGixwSaoeXGwd+sdo=; b=KVomHj16M+gM+P3ohcmSUmvQnYLKNw2t8AYOJHQjEb1VNxQqbSiJog/4pEOcsPcetJ II7IePb9R+5L7daBGRAxTJL79ch+vu3/1EDt4DFmp0ZpwOhFufnCtX5a/bHcTxUrroSR bRS/Wo+bfE8muq1IYgAgbmZjY11tpnuJ06pc94MftxF7vNWtbe3wUPyKjJbH60wMU0F4 TIGiOoUmjzJNerb8atZqZaL+z2UbqFZBk9r+U8AcLt3EM2YLjX7wHKFhVAFBlJo1P/vD jajkb6ixsuOj5xG5FdCp07TNvaYpdP3rp8LOYPUUKOQ8pEr1fm1VEsT4w/8SfDX9J2Uc vH3g== X-Gm-Message-State: AAQBX9diFQO3qTYRjhs68cAD0azW7EI8pgpM46xrYrT7LmclZuxyo/SA 3nRO4QgBniyaMBjhdzbBCW5UDE3AAfIyXbpIGFjSCg== X-Google-Smtp-Source: AKy350YOG6JcUO2VpfKnTvvRCs2dpmGr0i9fiinz47zwPIS3LivafCIPkMchzHlWYB/Or+yUJnzu7Q== X-Received: by 2002:adf:e588:0:b0:2ce:a828:b248 with SMTP id l8-20020adfe588000000b002cea828b248mr5591921wrm.71.1681204174993; Tue, 11 Apr 2023 02:09:34 -0700 (PDT) Received: from smtpclient.apple ([5.151.136.121]) by smtp.gmail.com with ESMTPSA id f4-20020adff8c4000000b002cff06039d7sm14031164wrq.39.2023.04.11.02.09.34 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 11 Apr 2023 02:09:34 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.400.51.1.1\)) Date: Tue, 11 Apr 2023 10:09:23 +0100 References: <8abbed60-5569-4eca-ad12-957877feed9b@app.fastmail.com> To: php internals In-Reply-To: Message-ID: X-Mailer: Apple Mail (2.3731.400.51.1.1) Subject: Re: [PHP-DEV] Future stability of PHP? From: php@sewell.info (Matthew Sewell) What's meaningful in this sense? I have a budget for supporting open source projects (back to my money v = time point) and a percentage of that is for the PHP Foundation. I'd = happily pay LTS fees we pay elsewhere (even sometimes as a safety net) = to the Foundation but believe that the money we give to projects is just = that, a donation that the project can use as it sees fit, rather than = the purchasing of a service as we do commercially. Best wishes, Matt > On 11 Apr 2023, at 09:56, Marco Pivetta wrote: >=20 > I'm also curious to hear whether any participants in this thread = do/did > support the PHP foundation in any tangible way :D >=20 > If you treat it like an LTS provider, perhaps it's time to pay up the = LTS > support fees? >=20 > Marco Pivetta >=20 > https://mastodon.social/@ocramius >=20 > https://ocramius.github.io/ >=20 >=20 > On Tue, 11 Apr 2023 at 10:40, Alex Wells wrote: >=20 >> On Tue, Apr 11, 2023 at 6:10=E2=80=AFAM Deleu = wrote: >>=20 >>> I don't want to use those weird stuff, but I'm >>> doing the best I can to replace every single line of old code that = has >> been >>> written in an era that "best practices for PHP development" were not = what >>> you and I know today. >>>=20 >>=20 >> I still do not understand why you're expecting the whole PHP project = to put >> in enormous efforts to keep the backwards compatibility and solve = your >> problems (temporarily) instead of you doing so. What's stopping you = from >> using the last supported PHP version by that codebase and fixing or, = worst >> case scenario, rewriting it if you wish, while on that (non latest) = PHP >> version? What causes the desperation to update to the latest PHP? Is = it new >> features or security fixes, or both? >>=20