Skip to content

Commit f1ad170

Browse files
committed
update release process notes
1 parent add4f43 commit f1ad170

File tree

1 file changed

+10
-7
lines changed

1 file changed

+10
-7
lines changed

README.RELEASE_PROCESS

Lines changed: 10 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -93,24 +93,27 @@ Commit the changes to the main branch.
9393
12. run: ``PHPROOT=. ./makedist 5.4.2RC2``, this will export the tree, create configure
9494
and build three tarballs (gz, bz2 and xz).
9595

96-
13. Copy those tarballs (scp, rsync) to downloads.php.net, in your homedir there should be a
96+
13. run ``scripts/dev/gen_verify_stub <version> [identity]``, this will sign the tarballs
97+
and output verification information to be included in announcement email
98+
99+
14. Copy those tarballs (scp, rsync) to downloads.php.net, in your homedir there should be a
97100
directory "downloads/". Copy them into there, so that the system can generate
98101
MD5 sums. If you do not have this directory, talk to Derick or Dan.
99102

100-
14. Now the RC can be found on http://downloads.php.net/yourname,
103+
15. Now the RC can be found on http://downloads.php.net/yourname,
101104
f.e. http://downloads.php.net/derick/
102105

103-
15. Once the release has been tagged, contact the PHP Windows development team
106+
16. Once the release has been tagged, contact the PHP Windows development team
104107
(internals-win@lists.php.net) so that Windows binaries can be created. Once
105108
those are made, they should be placed into the same directory as the source snapshots.
106109

107110
Getting the non stable release (alpha/beta/RC) announced
108111
--------------------------------------------------------
109112

110-
1. Send an email (see example here: http://news.php.net/php.internals/19486)
111-
**To** ``internals@lists.php.net`` and ``php-general@lists.php.net`` lists
112-
pointing out "the location of the release" and "the possible release date of
113-
either the next RC, or the final release".
113+
1. Send an email **To** ``internals@lists.php.net`` and ``php-general@lists.php.net``
114+
lists pointing out "the location of the release" and "the possible release date of
115+
either the next RC, or the final release". Include in this information the verification
116+
information output by ``gen_verify_stub``.
114117

115118
2. Send an email (see example here http://news.php.net/php.pear.qa/5201) **To**
116119
``php-qa@lists.php.net`` and ``primary-qa-tester@lists.php.net``.

0 commit comments

Comments
 (0)