Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:119794 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 67283 invoked from network); 30 Mar 2023 15:07:53 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 30 Mar 2023 15:07:53 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 83A17180507 for ; Thu, 30 Mar 2023 08:07:49 -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.5 required=5.0 tests=BAYES_20, FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM,HEADER_FROM_DIFFERENT_DOMAINS, HTML_MESSAGE,RCVD_IN_DNSWL_NONE,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-ed1-f49.google.com (mail-ed1-f49.google.com [209.85.208.49]) (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 ; Thu, 30 Mar 2023 08:07:48 -0700 (PDT) Received: by mail-ed1-f49.google.com with SMTP id cn12so77787095edb.4 for ; Thu, 30 Mar 2023 08:07:48 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680188867; x=1682780867; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=yHp9TJY37guURnameHUovWjeEZSFshRr+Yt14BhKK1A=; b=SR150R8qsASgkwLz1AQMb096bD1iGYhCXtEu9XXtaS2EHbilGMRddXuRWgPdZ2MJO+ mj2OGHJfDJAYEsxqQnKnc2fyctgvoWYjE7E++gKe4ACiQnqcFrfc8NM00DPkxlcm8UIR b9UWfBba3fVgCUeu0x0Yt9DphjgodIvxlprzG3Rl9rUgIsv/T0cqpZrQu002ecw7N67E Yy+D5Kt9ra9/dJ5nsOZT+qsL7wLcDsLQr3eloBXiRTzXaKVrKFvlpM7E/rrWinW3rLe9 ChG0opl4hWNNdGotg3YTyqG8blRegB3qjHG/hJ9/0dpuxSNvO4wMHAlD69yGLli712ol nO1w== X-Gm-Message-State: AAQBX9dYplaYsYvoFMgiDcarKLKSLQOo2OUfYNQKzVUAv/SF6EUrcV4+ hEglTQiNY4P9gX4o5ocHgP97jFL71i4SfjYmI/BmflGxERE= X-Google-Smtp-Source: AKy350ZDLtKf4BHarOhx08N1uYNtjZyMU6QztVg/1usZjHhxbd/PmDVYECz22ZivLI5vKKaNk1F3LQ/Z85pV6vfrZeM= X-Received: by 2002:a50:bb62:0:b0:4fa:ce07:639f with SMTP id y89-20020a50bb62000000b004face07639fmr11623967ede.5.1680188867326; Thu, 30 Mar 2023 08:07:47 -0700 (PDT) MIME-Version: 1.0 References: <4EF2F882-E34D-42C2-938F-79D58EFC98C0@php.net> In-Reply-To: <4EF2F882-E34D-42C2-938F-79D58EFC98C0@php.net> Date: Thu, 30 Mar 2023 16:07:36 +0100 Message-ID: To: Sergey Panteleev Cc: internals@lists.php.net Content-Type: multipart/alternative; boundary="00000000000097b66305f81f741f" Subject: Re: [PHP-DEV] Release Managers for PHP 8.3 From: bukka@php.net (Jakub Zelenka) --00000000000097b66305f81f741f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello, I would like to announce that I want to candidate to become a PHP 8.3 Release Manager. I have been contributing to PHP core for almost 10 years and maintain some parts of PHP. Specifically FPM, JSON, OpenSSL ext and some other bits. I'm part time funded by PHP Foundation and as part of that I'm looking to document and improve the internal processes (some of them will be soon proposed) which will also cover RM functioning and possibly improving the release flow as well. That would be much better done from the RM position and that's one of the main reasons why I candidate. Regards Jakub On Wed, Mar 1, 2023 at 8:21=E2=80=AFPM Sergey Panteleev wr= ote: > Hi all, > > It's time to start the process of finding and electing RMs for the next > minor PHP release. > > We are looking for three souls to take on this role. Whomsoever is electe= d > will be guided and helped by the current, as well as previous RMs and the > excellent documentation in release-process.md [1]. > > Candidates should have a reasonable knowledge of internals (without > necessarily being a C guru), be confident about merging pull requests > without breaking backward compatibility, doing triage for bugs, liaising > with previous release managers, and generally getting the branch in good > shape, as these are among the activities you will be undertaking as relea= se > manager. > > Notably, at least one of the volunteers must be a "veteran" release > manager, meaning they have participated in at least one release of PHP in > the past. The other may be an additional veteran, or more ideally, someon= e > new to the RM role (in order to increase our supply of veteran RMs). > > Please put your name forward here if you wish to be considered a > candidate. An initial TODO page has been added to the wiki and contains > provisional dates for GA and pre-releases [2]. > > [1] https://github.com/php/php-src/blob/master/docs/release-process.md > [2] https://wiki.php.net/todo/php83 > > Let's all make PHP awesome! > Pierrick Charron, Sergey Panteleev & Ben Ramsey > --00000000000097b66305f81f741f--