Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:128604 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 912BC1A00BC for ; Tue, 2 Sep 2025 10:19:56 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=php.net; s=mail; t=1756808306; bh=RtdSkpeckdikgjtVdm9mWz/z55y2usOsV5vk+gY+qZg=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=a8M4SfEtjUZGsICwV7+4P5Wh98O0/X3lAniN1fwiBZKC16BkKMtAYkd4fGGl7ztsa aziPd6iC8R3x/py3PJIk5+aM8AZqME/D+4y3pzjLqSJvX+6tbTt2yz/EoeXLKcBPtz R7FRQY4bMXQo4d8bn90q/DHH0Csj5Df4ObzHTa9+tVBvpgrSImTLXYUSTW31FsDEyi ospKGKiZ9OQP1lXw9uRSAG+7dYNH9vSFJjfbygHWP1V8Ja1hY/zbAtKbaS6tgJ9KtX FBDlcut7jEPOUTL3gWRnycNY6iJWcWgq5xd/SoXutvO/t+KJm9bMisCLCDtrbqstM8 GWLska15sKu/A== Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 9A42218003C for ; Tue, 2 Sep 2025 10:18:25 +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 ; Tue, 2 Sep 2025 10:18:25 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bastelstu.be; s=mail20171119; t=1756808393; bh=rKrK1Jo6XzyPfQOVM+dNyWQrZdQyq0A2vUAHZFuQovI=; h=MIME-Version:Date:From:To:Cc:Subject:In-Reply-To:References: Message-ID:Content-Type:from:to:cc:subject:message-id; b=ByBD9q2n3QQlYV8bEEhaagGjJJ6DuRDBswL04BluwDtlo2yxmXeU+GhrvAU+m3am/ piS78QX5hu7xXeF74MLoSvsncN3O5yuAM4mgJF3LuBLi2MbwXaGc54X0QizrhOztaS krxt1lPlNxnGMKTveCk3eEGp+uqUYJaiAmt6bLKlbFN1N2o7YONJ7E0UfPPWhHIvoT 03FqnvxdK0sIH7kbZj7LJItC2otzm9rE+uAL2XFZMTR3GCYYs/Rx7TgrZPlz4GOGXQ BYAa2jCXpLhA7xNN2DJDQe9MLqhIVJbLghDoff3ZfO2EHg5lVfFnSwoYSd+s0xBCQj cp5jysf+FK4JA== Precedence: list list-help: list-post: List-Id: x-ms-reactions: disallow MIME-Version: 1.0 Date: Tue, 02 Sep 2025 12:19:53 +0200 To: Derick Rethans Cc: PHP internals Subject: Re: [PHP-DEV] [RFC] Clarify discussion and voting period rules In-Reply-To: References: <53cdbf5b-7c6e-4ba1-9987-332634cab527@bastelstu.be> Message-ID: <1c4ef8c694de3a8d3ed86bc598c413cd@bastelstu.be> 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 Am 2025-09-01 11:41, schrieb Derick Rethans: > This looks sensible to me, but I probably would like to see the history > of these time extensions in the RFC wiki page itself too. Some of them What specifically do you want to see? Just a changelog with “minor” / “major” indicators? I've intentionally used the email on the list as a source of truth, since that is when others become aware of the changes, allowing them to review. For complex RFCs it's often the case that changes to the RFC happen incrementally over multiple days, obvious things are adjusted right away and less trivial stuff is double-checked against the implementation and possibly discussed with a co-author. Only after having made all the changes and having proof-read them, they would then be announced on the list in bulk, ready for the next round of discussion and resetting the timer. Best regards Tim Düsterhus