Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:118255 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 20043 invoked from network); 12 Jul 2022 13:14:30 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 12 Jul 2022 13:14:30 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id EEB6E1804B1 for ; Tue, 12 Jul 2022 08:09:02 -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.2 required=5.0 tests=BAYES_20,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,NICE_REPLY_A, 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-f53.google.com (mail-wr1-f53.google.com [209.85.221.53]) (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, 12 Jul 2022 08:09:02 -0700 (PDT) Received: by mail-wr1-f53.google.com with SMTP id h17so11646199wrx.0 for ; Tue, 12 Jul 2022 08:09:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=message-id:date:mime-version:user-agent:subject:content-language:to :references:from:in-reply-to:content-transfer-encoding; bh=MUkHdsWPP5rBPnckksTAg+6idxEbX19mVLy4/99e3rE=; b=H+gSWpV7kmiRLGl4EUdsHKjo7jJ4qeEITNoYUlVkKaSFHi2UxPMojcZEVOeJrPRh4J DB8qfMtculFrZaPAn2hHge5xK/7mKuOajN1+5/e1cUnC09Y1e1s6vbtejNWXxYaCRnHC 1tjt4C1cQQFAK4Ga7Hk0vZ1XtYnXXaz0D/9FYxb2KodWSpRdAR3nnUDXfsVVEuIhlJ1y V82c2zT09oFX2ztSaOp65ai533RQhF2yy1qEiDIjDKYVi8h4aLFz72T+bTmyKrzocUkr Y/l0HXunU9NNaya4iCWkzg9fmMnNIX3mLvtWT4D1vTiMBAAuZ+xW2SMoc3uB0q9GT5jU 8SRQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:references:from:in-reply-to :content-transfer-encoding; bh=MUkHdsWPP5rBPnckksTAg+6idxEbX19mVLy4/99e3rE=; b=Pf+FYKXc+e7dLJ9B+oTXHvpkajUHLncMIXxRT/cmc54PCbfWazfdd4riphmVPqbiAS ACOQy9kAUrHO9KB8MamSbIkXHM7g7oUTLncFgS0LDi7QwSvpILqCMtglfZHTqvPMGPjq +abnktZ1Rt/UfeoPk8jdTKCWLZoXLugi9YUQgO6lB7QazSCS/vRuVRD4W3YrHT1hLyGA NS8mXM6gNYjwN/ooTgdSItib8GtM6GcAIRwKzVlLpEyJVldbRPZUR68t+aj7jyLnciKR A/b0DAeJN85xPYdvsWWFcGLVVa3RGUYRunWlfOw5tUp7xFaS0ZYwRPPH+roz+goHxgQJ i9Lg== X-Gm-Message-State: AJIora/JeeY/Ke7sjM/HsjfpjHraKN7RZA7mh4WYtFMIL9ZB5jTVsGaW S7Y46vG4EkTe4OGkJnitdDa4RL6yYNw= X-Google-Smtp-Source: AGRyM1tsGe39iK04RIbvUBja3+VjHAR9eR0vHqkAaPNTras31woAPWIQs9fn334b7ypiE84/HrfCRA== X-Received: by 2002:a5d:6d0e:0:b0:21d:6d4c:e0e4 with SMTP id e14-20020a5d6d0e000000b0021d6d4ce0e4mr23597842wrq.355.1657638541261; Tue, 12 Jul 2022 08:09:01 -0700 (PDT) Received: from [192.168.0.22] (cpc104104-brig22-2-0-cust548.3-3.cable.virginm.net. [82.10.58.37]) by smtp.googlemail.com with ESMTPSA id h15-20020a1ccc0f000000b0039c54bb28f2sm10282034wmb.36.2022.07.12.08.08.59 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 12 Jul 2022 08:09:00 -0700 (PDT) Message-ID: <1ab9e7f1-1d79-bd97-9886-4cd10bb92b60@gmail.com> Date: Tue, 12 Jul 2022 16:08:59 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0 Content-Language: en-GB To: internals@lists.php.net References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [PHP8.2] Feature freeze in 2 weeks From: rowan.collins@gmail.com (Rowan Tommins) On 05/07/2022 19:08, Pierrick Charron wrote: > This is yet another friendly reminder from your RMs that the PHP 8.2 feature > -freeze is in 2 weeks now [1]. All RFC targeting 8.2 should now be in the > voting phase to respect the minimal period of 2 weeks. > > Also it would be appreciated if some of internal devs could start reviewing > PR labeled as "Waiting for review" [2] that are in their field of expertise. Hi all, Could somebody please merge / review this RFC implementation to make sure it gets into the first beta: https://github.com/php/php-src/pull/8823 It's been manually tagged "Waiting on Author", but I have no way to switch that back to "Waiting on Review" now that I've resolved the comments. Thanks, -- Rowan Tommins [IMSoP]