@@ -777,10 +777,10 @@ slightly different steps. We'll call attention where the steps differ.
777
777
> want their email client to automatically send the reply to each list, as
778
778
> often occurs.
779
779
780
- 11 . Coordinate with the social media team (i.e., Derick) to post a tweet with
781
- the release announcement and link to the news entry on php.net.
782
- ([@official_php](https://twitter.com/official_php))
783
-
780
+ 13 . Coordinate with the social media team (i.e., Derick) to
781
+ [create a PR request](https://github.com/derickr/toot-together/blob/main/toots/README.md)
782
+ for posting the release announcement to Mastodon. Posts need to be
783
+ approved.
784
784
785
785
## Re-releasing the same version or a patch-level (i.e., `-plN`)
786
786
@@ -971,10 +971,39 @@ volunteers to begin the selection process for the next release managers.
971
971
972
972
# # New release manager checklist
973
973
974
- 1. Email systems@php.net to get setup for access to downloads.php.net and to be
975
- added to the release-managers@php.net distribution list.
974
+ 1. Request membership to the
975
+ [release managers group](https://github.com/orgs/php/teams/release-managers) on GitHub.
976
+
977
+ 2. Email systems@php.net to get setup for access to downloads.php.net, to be
978
+ added to the release-managers@php.net distribution list, and to be added to
979
+ the moderators for php-announce@lists.php.net so you are able to moderate
980
+ your release announcements.
981
+
982
+ Provide the following information in a single email:
983
+
984
+ - Prefered Unix username (will also become part of location to download RCs,
985
+ such as ` https://downloads.php.net/~derick/` ).
986
+ - An SSH public key, preferably a new unique one for PHP systems and
987
+ projects.
988
+ - Read [Machine Access](https://wiki.php.net/systems#machine_access) to set
989
+ up access to downloads.php.net through jump hosts, and provide a
990
+ ` .google_authenticator` file for 2FA.
991
+ - Subscribe to the php-annouce@lists.php.net mailing list by emailing
992
+ php-announce+subscribe@lists.php.net
993
+ - Your @php.net email address to use for the release-managers@php.net
994
+ distribution list and php-announce@lists.php.net moderator address. This
995
+ should preferably not forward to a Gmail address.
996
+ - Your GitHub accounti name, so that your membership to the release managers
997
+ group may be approved.
998
+
999
+ A system admin will then contact you to go through with steps 5 through 8 of
1000
+ [2FA setup instructions](https://wiki.php.net/systems#fa_setup_instructions).
1001
+
1002
+ > 💬 ** Hint** \
1003
+ > To send email from your @php.net address, you will need to use a custom
1004
+ > SMTP server. If you use Gmail, you may
1005
+ > " [Send emails from a different address or alias][]."
976
1006
977
- 2. Request membership to the release managers group on GitHub.
978
1007
979
1008
3. Create a [GPG key][] for your @php.net address.
980
1009
@@ -1041,16 +1070,7 @@ volunteers to begin the selection process for the next release managers.
1041
1070
git push
1042
1071
```
1043
1072
1044
- 4. Request moderation access to php-announce@lists.php.net
1045
- so you are able to moderate your release announcements. All the announcements
1046
- should be sent from your @php.net address.
1047
-
1048
- > 💬 **Hint** \
1049
- > To send email from your @php.net address, you will need to use a custom
1050
- > SMTP server. If you use Gmail, you may
1051
- > "[Send emails from a different address or alias][]."
1052
-
1053
- 5. Make sure you have the following repositories cloned locally:
1073
+ 4. Make sure you have the following repositories cloned locally:
1054
1074
1055
1075
* https://github.com/php/php-src
1056
1076
* https://github.com/php/web-php
0 commit comments