Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:122570 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 qa.php.net (Postfix) with ESMTPS id 88A531AD8F6 for ; Tue, 5 Mar 2024 17:30:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=php.net; s=mail; t=1709659864; bh=i4yfAfDneyYH3pR2yxuagIchgBtdWC+D0yxs0BKCvGg=; h=References:In-Reply-To:From:Date:Subject:To:From; b=GoziC9QGEU3AEBK6fC6BcL8pFQJLYUut2VoAqMkx6eibt6NNT1Xa1kNfZhKNt8biK ITC/EJrFEu3tlUutqVLcvK45PuN7UMcw2JRCm9mmguOTr2rtSB950fICkqewBncGZH e2cHaEoDTV+ewefSGpzin5TnV2Z2dxOzwzTAXT9GDc1cKT+i/YM1uaoto7k33rf1Ih sKKWlxkmqVDUwtzyg9p02PS+KFwsyT3LjUednic2RJxoWsZnJk9W7cm/xcJYLaj2rh SqcmP0/5eeaSdOY2tBm9vnMHf+76/0p3LM9YIZtN/vBmPgG945UXRtzS1UwQV9mB8y TdchtB4orNBaQ== Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 4330318005D for ; Tue, 5 Mar 2024 17:31:03 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-13) on php-smtp4.php.net X-Spam-Level: * X-Spam-Status: No, score=1.0 required=5.0 tests=BAYES_50,DMARC_MISSING, 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=4.0.0 X-Spam-Virus: No X-Envelope-From: Received: from mail-lj1-f170.google.com (mail-lj1-f170.google.com [209.85.208.170]) (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, 5 Mar 2024 17:31:02 +0000 (UTC) Received: by mail-lj1-f170.google.com with SMTP id 38308e7fff4ca-2d2505352e6so77781101fa.3 for ; Tue, 05 Mar 2024 09:30:50 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1709659849; x=1710264649; h=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=i4yfAfDneyYH3pR2yxuagIchgBtdWC+D0yxs0BKCvGg=; b=qQs1r/1ZF8bAvxMqjRHRO3NZ5i6GmjVWhyCAG1F9AAvUiwewCLS5M+kflsUKFzQ2On KfmtT1Kj3hqPLHuNhlutl4bI17nsFPUPnUxxzPdWPr4VxZtUS58+VU44ikJ/OgxDBLSE o24WwzS1xelD9unvlJDdMcpEUdsli5zBxA8BDSjKVQUNDsMlVKJ0TzLpUijjN3DDwuOl se1j9zxzTyB7+hJEWuY579jOHtnfs1oK/N0653hBPouQb2Fj2myL3rm5BfApGH2wCWui 4QqNQoCpz5Cwilc0J/13c470tqRVmT/dPSQlc7IVPG/JJnPy3PTKQaKtpuNWDV2eecZk nS/g== X-Gm-Message-State: AOJu0YzDMKuJ6ldGFZ0WMsxo9qLBY862wQn5wDA+xwZUb0iv5jAB8Lfz dNTsa8CrQiQr1BdEJGfIdREUyBaVQJ0y//hWAgokdbIPeW82RIiXcQJ3zop5tEmchFl7vY6yAjw 7b+14qAyxo/BNBK9kW9EHSE8Aoa/iRMV4O9A9sA== X-Google-Smtp-Source: AGHT+IHJcPuo243VDYarUzko8Mz7oVP67w3hkbh3NjJH6Zw/XuW/kkurbhCSAs/dKoM/F8i3KMPCxsuxbwVlfe4HHxI= X-Received: by 2002:a2e:8482:0:b0:2d2:a53d:bbb9 with SMTP id b2-20020a2e8482000000b002d2a53dbbb9mr1505879ljh.50.1709659848534; Tue, 05 Mar 2024 09:30:48 -0800 (PST) Precedence: bulk list-help: list-post: List-Id: internals.lists.php.net MIME-Version: 1.0 References: In-Reply-To: Date: Tue, 5 Mar 2024 17:30:37 +0000 Message-ID: Subject: [PHP-DEV] Re: Release Managers for PHP 8.4 To: PHP internals list Content-Type: multipart/alternative; boundary="000000000000f574cc0612ed330c" From: bukka@php.net (Jakub Zelenka) --000000000000f574cc0612ed330c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Mar 5, 2024 at 3:37=E2=80=AFPM Jakub Zelenka wrote: > 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, be confident > about merging pull requests without breaking backward compatibility, doin= g > 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 release manager. Ideally, at least one of > candidate should be a core developer that can assess more technical PR's. > Other candidates do not necessarily need to have deep knowledge of > internals but should understand above mentioned points. > > 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/php84 > > Let's all make PHP awesome! > Jakub Zelenka, Eric Mann & Pierrick Charron > > Apology I forgot add the deadline for the volunteer search and the voting phase: Applications will be accepted until 31 March 2024 12:00:00 UTC Elections (if needed) will start on 1 April and run until 15 April 12:00:00 UTC Cheers Jakub --000000000000f574cc0612ed330c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Tue, Mar 5, 2024 at 3:37=E2=80=AFPM Ja= kub Zelenka <bukka@php.net> wrot= e:
Hi all,

It's time to start the pr= ocess of finding and electing RMs for the next minor PHP=C2=A0release= .

We are looking for three souls to take on this role. Whomso= ever is elected will be guided and helped by the current, as well as previo= us RMs and the excellent documentation in=C2=A0release-process= .md [1].

Candidates should have a reasonable knowledge of internals,= be confident about merging pull requests without breaking backward compati= bility, doing triage for bugs, liaising with previous=C2=A0release=C2=A0managers, and generally getting the branch in good s= hape, as these are among the activities you will be undertaking as=C2=A0release=C2=A0manager. Ideally, at least one of candi= date should be a core developer that can assess more technical PR's. Ot= her candidates do not necessarily need to have deep knowledge of internals = but should understand above mentioned points.

Notably, at least one = of the volunteers must be a "veteran"=C2=A0release= =C2=A0manager, meaning they have participated in at least one= =C2=A0release=C2=A0of PHP in the past. The other may be an add= itional veteran, or more ideally, someone new to the RM role (in order to i= ncrease our supply of veteran RMs).

Please put your name forward her= e if you wish to be considered a candidate. An initial TODO page has been a= dded to the wiki and contains provisional dates for GA and pre-releases [2]= .

[1]=C2=A0https://github.c= om/php/php-src/blob/master/docs/release-process.md
[2]= =C2=A0https://wiki.php.net/todo/php84

Let's all make P= HP awesome!
Jakub Zelenka, Eric Mann & Pierrick Charron

Apology I forgot add the deadline = for the volunteer search and the voting phase:

Applications will be = accepted until 31 March 2024 12:00:00 UTC

Elections (if needed) will= start on 1 April and run until 15 April 12:00:00 UTC

Cheers

Jakub
--000000000000f574cc0612ed330c--