Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:130393 X-Original-To: internals@lists.php.net Delivered-To: internals@lists.php.net Received: from php-smtp4.php.net (php-smtp4.php.net [45.112.84.5]) by lists.php.net (Postfix) with ESMTPS id A5B001A00E0 for ; Wed, 18 Mar 2026 12:39:20 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=php.net; s=mail; t=1773837565; bh=c/Cqn3HogYVRkqrm5ejdyCozIJW2zrOPcrCpa+0i19M=; h=Date:To:From:Subject:In-Reply-To:References:From; b=ZFrUdodnOK95cGl5XsMIYeHouYroJwBJH3SKotg3ZDREKyEeX7BIzHCh81SfXBuwD 0bepIRjNr5hMmEno4Chhid4khQOHtRXJ+jjXslTgJLGfsiLk6fkrxx/wFgIvCX8UD6 3B9dDkHt1r3rMNyaaRY1uNlJDOHW/SQQ5TjwCIU8EWMjGXN0Mf+r157gyFc6k/qCVx OLcDDgAkP4B/exqfwpb1wRVpNgP24+jklOe9aU4o/4lPRQhg20vG9FeCQYLaTAM1ob 1h9Y2kCtTTnEYHb4Zg71XgFwxexWRZUtbiQbyYDnbx06m2yzA08f0BoSb1lLAgeIvz Vn+/JnwEslnPw== Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 83E2118073A for ; Wed, 18 Mar 2026 12:39:23 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-25) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-0.1 required=5.0 tests=BAYES_50,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,DMARC_PASS,RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H5,RCVD_IN_MSPIKE_WL,SPF_HELO_PASS,SPF_PASS autolearn=no autolearn_force=no version=4.0.1 X-Spam-Virus: No X-Envelope-From: Received: from mail-10625.protonmail.ch (mail-10625.protonmail.ch [79.135.106.25]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Wed, 18 Mar 2026 12:39:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gpb.moe; s=protonmail2; t=1773837553; x=1774096753; bh=c/Cqn3HogYVRkqrm5ejdyCozIJW2zrOPcrCpa+0i19M=; h=Date:To:From:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=kECnB3EwpBT8JcBVabcQowHkLR6+9fuwNEgIkwYHrGShV1LmH/8N5BYdkNvkagyFG /dWk96jQuU9aEHvNuBuCA/6HVVdJzUK+zMVccoLJekwW5E3PFIE+do6atP9wAQcbjP n2XC+Cb3nsbhMeBv95iR5uGk63WmTSKsUSv2mqC0s7tPk+v6E7epH3s3C28r+Y1UUC 78KoSS5dOrw3jxxicZapT3h/KKQRcWCW/OWk/e9YAOa7QZwFa2lRF1I/M8UHVbqPgy grA6xT2xLnFxpNvjYVrurJDFgmscDAurZw08hSqpiU4v3ezUXEoyGuMPa+qu9l8fps GpzoZVNk/Dx2A== Date: Wed, 18 Mar 2026 12:39:10 +0000 To: PHP internals Subject: [PHP-DEV] Re: [RFC] Exempt input type and value validation from BC Break policy Message-ID: In-Reply-To: References: Feedback-ID: 96993444:user:proton X-Pm-Message-ID: 3320f613b36fbacff2f5f6c8216307e1e81a0fad Precedence: list list-help: list-unsubscribe: list-post: List-Id: x-ms-reactions: disallow MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable From: internals@gpb.moe ("Gina P. Banyard") On Monday, 2 March 2026 at 13:13, Gina P. Banyard wrote= : > Hello internals, >=20 > I would like to propose a short policy RFC to formally exempt input type = and value validation from our BC Break policy. > The current wording of the policy already permits us to add validation of= inputs, but recently any such changes have been asked to submit an RFC ins= tead. > We believe that requiring an RFC for this type of change is detrimental a= nd adds unnecessary friction for routine maintenance activity and new contr= ibutors. >=20 > RFC: https://wiki.php.net/rfc/policy-exempt-type-value-error-bc-policy >=20 > Best regards, >=20 > Gina P. Banyard As the discussion has lasted over 2 weeks and was focused on, IMHO, irrecon= cilable differences in policy position; I intend to open the vote on Friday= afternoon/evening European time. Best regards, Gina P. Banyard