From: Sara Golemon Date: Tue, 6 Jun 2017 16:45:20 +0000 (-0400) Subject: Remove instructions to email internals-win@ X-Git-Tag: php-7.2.0alpha2~66 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=5f055273932d5f2a5ef21f4aace92c32e685fad0;p=php Remove instructions to email internals-win@ Use the release-managers@ distribution list instead for a better audience. --- diff --git a/README.RELEASE_PROCESS b/README.RELEASE_PROCESS index bd0c7261a7..b6b46ada52 100644 --- a/README.RELEASE_PROCESS +++ b/README.RELEASE_PROCESS @@ -103,9 +103,9 @@ MD5 sums. If you do not have this directory, create it. 15. Now the RC can be found on http://downloads.php.net/~yourname, f.e. http://downloads.php.net/~derick/ -16. Once the release has been tagged, contact the PHP Windows development team -(internals-win@lists.php.net) so that Windows binaries can be created. Once -those are made, they should be placed into the same directory as the source snapshots. +16. Once the release has been tagged, contact the release-managers@ distribution list +so that Windows binaries can be created. Once those are made, they should be placed +into the same directory as the source snapshots. Getting the non stable release (alpha/beta/RC) announced -------------------------------------------------------- @@ -319,7 +319,8 @@ will not accidentally hit the php-announce@ mailinglist. New Release Manager Checklist ----------------------------- -1. Email systems@ to get setup for access to downloads.php.net +1. Email systems@ to get setup for access to downloads.php.net and to be added to the + release-managers@ distribution list. 2. Create a GPG key for your @php.net address and publish it by editing `include/gpg-keys.inc` in the `web-php` repository, adding the output of `gpg --fingerprint "$USER@php.net"`. Let