com php-src: [ci skip] yet more info for new rm: README.RELEA SE_PROCESS
[email protected] (Anatol Belski)
| Newsgroups | php.cvs |
|---|---|
| Message-ID | <[email protected]> |
Commit: 9cec5e2c1d1c333dd9eff8d3879816c45f3db5ef Author: Anatol Belski <[email protected]> Fri, 28 Apr 2017 19:15:32 +0200 Parents: f708f0bb72b182ae371156435c4a00586dca06d7 Branches: master Link: http://git.php.net/?p=php-src.git;a=commitdiff;h=9cec5e2c1d1c333dd9eff8d3879816c45f3db5ef Log: [ci skip] yet more info for new rm Changed paths: M README.RELEASE_PROCESS Diff: diff --git a/README.RELEASE_PROCESS b/README.RELEASE_PROCESS index fb4d93d..192d349 100644 --- a/README.RELEASE_PROCESS +++ b/README.RELEASE_PROCESS @@ -322,4 +322,15 @@ New Release Manager Checklist 1. Email systems@ to get setup for access to downloads.php.net 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 "[email protected]"` + in the `web-php` repository, adding the output of `gpg --fingerprint "[email protected]"`. Let + one or more of the previous RMs sign your key. + +3. Request karma to eding main/php_version.h. Possibly karma for other restricted parts of + php-src might come in question. + +4. Request karma for web/qa.git and web/php.git for publishing release announcements. + +5. Request moderation access to [email protected] and [email protected] lists, to + be able to moderate your release announcements. All the announcements should be sent from + the @php.net alias. +