Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:121662 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 25617 invoked from network); 13 Nov 2023 08:20:58 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 13 Nov 2023 08:20:58 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 94C9A180511 for ; Mon, 13 Nov 2023 00:20:57 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS, 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-f42.google.com (mail-wr1-f42.google.com [209.85.221.42]) (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 ; Mon, 13 Nov 2023 00:20:57 -0800 (PST) Received: by mail-wr1-f42.google.com with SMTP id ffacd0b85a97d-32ddfb38c02so2497452f8f.3 for ; Mon, 13 Nov 2023 00:20:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1699863655; x=1700468455; darn=lists.php.net; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=k412WQ8n/5Z61c0gc6Kqea8Ed63D8gWr21zg64N9810=; b=AjMunrjAlT4MwTrOiqjF4osAkADXUo85h/1xkiCuZNuIM43RxeLuEMVo3ji0r9U95Q mWzhUk2C3rtlk72VaRPp3q33JkuLoSR/OBuWStp9W6ySJQs411gTchv6jU8ofIbXrapR Esk8D0a3cWV3UJDv3qvbV/vILPrXEi4OauTrPFBk9jwiLdW5u/4nriLbEbq6PDSZ0JoQ ewOJSbXmqPwsP68nfiVJryQkwg1zpvp/K660vIFJz4ve+paJJDx//4o822zujhkJeSU/ Z76KZeoGAGkqv9sq9qBaDwUXV+YRMqzwpPw18jNNYM0iz79R5u/tb/465u10zhVWTuW0 FW3Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1699863655; x=1700468455; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=k412WQ8n/5Z61c0gc6Kqea8Ed63D8gWr21zg64N9810=; b=QQwJ7QhoJGKtP3gpGprxJVLMCx34ZHGN8LbDMGeYloCLaI1CF4eIvZfRoFCivOnuwe HNbW9i+m1WAdNT027UfCDj2zkPt4PRwfbl0GH5s1pixPQ7D1TljI1XlA+o2YWk1EnthT AfBtY8KRPyZqzRCDhU4oSfJ+tdOKTDcYBF1E8EY35XvT9d+uML1a6NqtL8gUulWNIA1v vwKS4D+Q6rDNmPEc4kEiNdEj0XgBYdEn5ME19EuDhl2qmDs3WfSLUP+EjFGpdkhPEyVW ctwMgrh76WwXejkpTppD+dX8XCwjfYbuywF1kwNmc4YQSIw6KoL272+YsN9xVN8MG5yG wkqQ== X-Gm-Message-State: AOJu0YzL+LnLcyC4YvYRcWCAv5kv7sjW+euA2CL+JSOV5NVMqSXKTwwH BIVjrKXwjVOzTHdY2Drqc6mREu3eX3tAKuOf/CSMmshodIwYqHx8KA== X-Google-Smtp-Source: AGHT+IG9yg4VZFHUlxYQj6QA/XhB/4jASE++dMJsQIqvlOMpn1Sp7I9sYZrCFU6BD3OIqv4hiY5OSCi1sLEZ4kWqqps= X-Received: by 2002:a05:6000:118c:b0:32d:ad44:cec1 with SMTP id g12-20020a056000118c00b0032dad44cec1mr4365614wrx.3.1699863655328; Mon, 13 Nov 2023 00:20:55 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: Date: Mon, 13 Nov 2023 17:20:44 +0900 Message-ID: To: internals@lists.php.net Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] [RFC] [Discussion] Release cycle update From: youkidearitai@gmail.com (youkidearitai) 2023=E5=B9=B411=E6=9C=8811=E6=97=A5(=E5=9C=9F) 8:27 Rowan Tommins : > > On 10 November 2023 16:51:57 GMT, Jakub Zelenka wrote: > >Hello, > > > >I would like to propose a new process RFC for updates to PHP release cyc= le: > > > >https://wiki.php.net/rfc/release_cycle_update > > Hi, > > I started writing a suggestion that you add details to your RFC of what t= ext we would remove or change in the existing policy if approved - what you= 've presented so far is like a good commit message, but we probably want a = diff to go with it. > > However, looking at the existing "policy", most of the things you want to= change aren't actually in it - it doesn't even contain the word "beta". It= also has parts that are obviously outdated ("Features can use branch(es) i= f necessary" - because the project was using SVN, where branches are costly= to maintain), parts in the future tense, and even open questions (about wh= o can vote for RMs). > > So maybe what's really needed is to draft a new copy of the policy docume= nt, updating or removing those parts that are no longer relevant, and addin= g a timeline for the pre-release phases? > > Or possibly there's a different document I should be looking at, and the = RFC could contain proposed edits to that? > > Regards, > > -- > Rowan Tommins > [IMSoP] > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: https://www.php.net/unsub.php > Hi, Internals From mbstring point of view, PHP 8.0 is last version of not affected "Major overhaul of mbstring". For example, PHP 8.0's mb_detect_encoding not affected to below. - https://github.com/php/php-src/issues/10192 - https://github.com/php/php-src/issues/7871 If PHP 8.0's EOL is one more year, There is a one-year grace period for upgrades. Regards Yuya -- --------------------------- Yuya Hamada (tekimen) - https://tekitoh-memdhoi.info - https://github.com/youkidearitai -----------------------------