Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:129167 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 049F51A00BC for ; Sun, 9 Nov 2025 15:25:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=php.net; s=mail; t=1762701944; bh=3/gcKz/pcmGXYoTjI72fppzdgKzo+rkggtWVOLrUats=; h=Date:Subject:To:References:From:In-Reply-To:From; b=MHsbqsQRf8Ki/gP2TfUA0pObs6u+k69e4B3Q+WfxqSjFnlz4IkhWQWQkzoPBcTrDz pkNnpjpUQHV2si5DxwUkz27Tk7dZuCKtVvQS7deXK7+rfsMnwnoBR19K3UaYqdQL9U WU2vRohBmy2qrQoNaplXA+MQwf3RBItVj6PS4JfR89Q2WUgJRMV4YSL8qPkAmXdkic uPkhqwc94ztQKgj7OS5OmpxZVhNl/Uj4qB9YnzFfIuHlDVObjIwbHLcayuMUemzayv nbt7ivmf0j35Xz0a+c0FnXAYZAQXoblZ+sqH35+panT0U1Rg6ucQU9xuMJYnH7/pkx ZqqApqVBBjcGg== Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id DB8DA18002E for ; Sun, 9 Nov 2025 15:25:43 +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.2 required=5.0 tests=BAYES_40,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,DMARC_PASS,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=4.0.1 X-Spam-Virus: No X-Envelope-From: Received: from chrono.xqk7.com (chrono.xqk7.com [176.9.45.72]) (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 ; Sun, 9 Nov 2025 15:25:33 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bastelstu.be; s=mail20171119; t=1762701927; bh=Q2UAf4lVe4yk2sfDmXDZgdLKYNuoxZMuCbY9L73ggPU=; h=Message-ID:Date:MIME-Version:Subject:To:References:From: In-Reply-To:Content-Type:from:to:cc:subject:message-id; b=Me+txmH/Np0hM1V1rDQhyvM/ehs2OpR59EqtTZbBA0Sj7fmxo46+VWdf2VA04ciuf wo8XjYMewvxvyVMmPJuOaShYKuIYOliY5KoexF4X32ggr5alFc0fCgTtkZrK1VVidd tMBB8UwtB5XORdxu3LjvCZ3hNMra60ideYeBp7ZU67BIRcOQxFwTGyiXm17ucD5ndx j9ZkHcQSMgnTp9WXGccQ5h5l0M7Z8g40cbx+ZjroXroC37SNw4dz4JQytBZa9qle9o VaDOGislhy3Dw+gsl4VWn1I2J738hVp+fVQ06tbNyiJ/h2nYl5ULCwHt7eWV/GfRP1 /5jMRMUGq0H7A== Message-ID: <136c22d5-75c7-4a07-8c6b-1660184fb984@bastelstu.be> Date: Sun, 9 Nov 2025 16:25:25 +0100 Precedence: list list-help: list-unsubscribe: list-post: List-Id: x-ms-reactions: disallow MIME-Version: 1.0 Subject: Re: [PHP-DEV] [VOTE] Clarify discussion and voting period rules To: Rob Landers , internals@lists.php.net References: Content-Language: en-US In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit From: tim@bastelstu.be (=?UTF-8?Q?Tim_D=C3=BCsterhus?=) Hi On 11/9/25 16:15, Rob Landers wrote: > May I ask, as a follow-up task, to add some kind of copy/pastable templates to the rfc:howto (https://wiki.php.net/rfc/howto)? For example, what information needs to be sent in major/minor/editorial changes? Do you need to declare which type of change it is and its effect, or is it simply assumed everyone knows? I had planned to make some changes to the template at https://wiki.php.net/rfc/template, but not the How To. I can have a look at the How To as well. >> _Major and minor changes MUST be announced in the official discussion thread, either in a dedicated email summarizing a list of changes or in a reply to another email that clearly indicates that changes to the RFC text have been made in response to that email._ > > Does this mean "A major change has been made" as in literally announcing the type of change, or just that the change must be announced? The latter. The required email is intended as an invitation to the participants to have another look after the RFC authors believe that the changes to the RFC are complete (for now) and then to discuss the latest changes. The type of change (Major / Minor) should be clear for the majority of changes, but spelling it out explicitly can't hurt - if only for yourself to keep track of things. Keeping a changelog in the RFC will help as well. Best regards Tim Düsterhus