From fe0e1d875b7982c1912d39967cde7f11e7e6fa5f Mon Sep 17 00:00:00 2001
From: Derick Rethans <github@derickrethans.nl>
Date: Thu, 18 Apr 2024 13:39:36 +0100
Subject: [PATCH] Describe what you need to ask systems@php.net for

---
 docs/release-process.md | 54 ++++++++++++++++++++++++++++-------------
 1 file changed, 37 insertions(+), 17 deletions(-)

diff --git a/docs/release-process.md b/docs/release-process.md
index 6b322d05e4a29..e41068fa342d2 100644
--- a/docs/release-process.md
+++ b/docs/release-process.md
@@ -777,10 +777,10 @@ slightly different steps. We'll call attention where the steps differ.
    > want their email client to automatically send the reply to each list, as
    > often occurs.
 
-11. Coordinate with the social media team (i.e., Derick) to post a tweet with
-    the release announcement and link to the news entry on php.net.
-    ([@official_php](https://twitter.com/official_php))
-
+13. Coordinate with the social media team (i.e., Derick) to
+    [create a PR request](https://github.com/derickr/toot-together/blob/main/toots/README.md)
+    for posting the release announcement to Mastodon. Posts need to be
+    approved.
 
 ## Re-releasing the same version or a patch-level (i.e., `-plN`)
 
@@ -971,10 +971,39 @@ volunteers to begin the selection process for the next release managers.
 
 ## New release manager checklist
 
-1. Email systems@php.net to get setup for access to downloads.php.net and to be
-   added to the release-managers@php.net distribution list.
+1. Request membership to the
+   [release managers group](https://github.com/orgs/php/teams/release-managers) on GitHub.
+
+2. Email systems@php.net to get setup for access to downloads.php.net, to be
+   added to the release-managers@php.net distribution list, and to be added to
+   the moderators for php-announce@lists.php.net so you are able to moderate
+   your release announcements.
+
+   Provide the following information in a single email:
+
+   - Prefered Unix username (will also become part of location to download RCs,
+     such as `https://downloads.php.net/~derick/`).
+   - An SSH public key, preferably a new unique one for PHP systems and
+     projects.
+   - Read [Machine Access](https://wiki.php.net/systems#machine_access) to set
+     up access to downloads.php.net through jump hosts, and provide a
+     `.google_authenticator` file for 2FA.
+   - Subscribe to the php-annouce@lists.php.net mailing list by emailing
+     php-announce+subscribe@lists.php.net
+   - Your @php.net email address to use for the release-managers@php.net
+     distribution list and php-announce@lists.php.net moderator address. This
+     should preferably not forward to a Gmail address.
+   - Your GitHub accounti name, so that your membership to the release managers
+     group may be approved.
+
+   A system admin will then contact you to go through with steps 5 through 8 of
+   [2FA setup instructions](https://wiki.php.net/systems#fa_setup_instructions).
+
+   > 💬 **Hint** \
+   > To send email from your @php.net address, you will need to use a custom
+   > SMTP server. If you use Gmail, you may
+   > "[Send emails from a different address or alias][]."
 
-2. Request membership to the release managers group on GitHub.
 
 3. Create a [GPG key][] for your @php.net address.
 
@@ -1041,16 +1070,7 @@ volunteers to begin the selection process for the next release managers.
    git push
    ```
 
-4. Request moderation access to php-announce@lists.php.net
-   so you are able to moderate your release announcements. All the announcements
-   should be sent from your @php.net address.
-
-   > 💬 **Hint** \
-   > To send email from your @php.net address, you will need to use a custom
-   > SMTP server. If you use Gmail, you may
-   > "[Send emails from a different address or alias][]."
-
-5. Make sure you have the following repositories cloned locally:
+4. Make sure you have the following repositories cloned locally:
 
    * https://github.com/php/php-src
    * https://github.com/php/web-php