Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:121644 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 42109 invoked from network); 10 Nov 2023 16:52:11 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 10 Nov 2023 16:52:11 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 05028180211 for ; Fri, 10 Nov 2023 08:52:10 -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=0.5 required=5.0 tests=BAYES_40, FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM,HEADER_FROM_DIFFERENT_DOMAINS, HTML_MESSAGE,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-ej1-f44.google.com (mail-ej1-f44.google.com [209.85.218.44]) (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 ; Fri, 10 Nov 2023 08:52:09 -0800 (PST) Received: by mail-ej1-f44.google.com with SMTP id a640c23a62f3a-9dd6dc9c00cso376408666b.3 for ; Fri, 10 Nov 2023 08:52:09 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1699635128; x=1700239928; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=hor7khl4UqiMkGCebJcqH338e9GRZ53qjqiAVjTrFuA=; b=f24wcfjuR9xW7ICviB8z91na5otBnDS+jt0bVrZvIfUr3M41kyjknkB53MvbwKhBeW NzpBW1c2HPa5Nxb4g5KEXwbyojWbiNRm5s5CTE99shu1UAh8Q0NS3d+gD8p/WeT/LXhn DejKTiYfsOY+CEVUnt0El7Nz1469pUl3n7fboIdl//LQFuSTB2Ikq4PWKi/kmTuDrqY2 ojE2zMo3J+oIUNQvOETsls5Nd9enYU/DQThAvfApHrnr/2exAAq2bw5LDLfm6Nfczuh7 LwRxH8NeIkdQgJnzbWyxF0F69YsrS2Kw4vL1l9vYAFzObBDwsQx2msIALxFF4Edfad7e aizQ== X-Gm-Message-State: AOJu0YwkcGeA9YqBgi2zuCA1zjqDq5xVm9DZJ+6O6bQH9eScZbh7pf/7 3UgFyZ7EsJxK3Sp4EEMJHJLF0wGn7tIjK1Yon4knj6cwi+M= X-Google-Smtp-Source: AGHT+IFeW1NDnG5OEAqa+/e1Roo7KJKBK1CglcpNiBUcWPacSVrNJFa9TDdib35BFMpobHk+2yljKy5RPtTi5kF8Rxg= X-Received: by 2002:a17:907:2da9:b0:9de:32bb:fa94 with SMTP id gt41-20020a1709072da900b009de32bbfa94mr6883843ejc.64.1699635127758; Fri, 10 Nov 2023 08:52:07 -0800 (PST) MIME-Version: 1.0 Date: Fri, 10 Nov 2023 16:51:57 +0000 Message-ID: To: PHP internals list Content-Type: multipart/alternative; boundary="00000000000009b3e40609cf24c0" Subject: [RFC] [Discussion] Release cycle update From: bukka@php.net (Jakub Zelenka) --00000000000009b3e40609cf24c0 Content-Type: text/plain; charset="UTF-8" Hello, I would like to propose a new process RFC for updates to PHP release cycle: https://wiki.php.net/rfc/release_cycle_update This has been discussed between release managers to make sure that all are happy as some of the points impact release managers (e.g. longer security support). I also opened a PR to my new personal repo for RFC's if anyone has got any suggestion for better wording or notices any typo: https://github.com/bukka/php-rfc/pull/1 Cheers Jakub --00000000000009b3e40609cf24c0--