fix some issues

Author: krakjoe

docs/release-process.md

@@ -26,8 +26,8 @@ explained at the end of this document in
 
  3. Ensure that the relevant tests on CI are green.
 
-    See: 
-      https://travis-ci.org/php/php-src/builds
+    See:
+      https://ci.appveyor.com/project/php/php-src
       https://dev.azure.com/phpazuredevops/PHP/
 
     It is recommended to do so a couple of days before the packaging day, to
@@ -41,8 +41,7 @@ explained at the end of this document in
  4. Follow all steps to the letter. When unclear ask previous RM's before
     proceeding. Ideally make sure that for the first releases one of the
     previous RM's is around to answer questions. For the steps related to the
-    php/QA/bug websites try to have someone from the webmaster team (Bjori) on
-    hand.
+    php/QA/bug websites try to have someone from the webmaster team on hand.
 
  5. Verify the tags to be extra sure everything was tagged properly.
 
@@ -57,18 +56,15 @@ explained at the end of this document in
 
 ## Packaging a non stable release (alpha/beta/RC)
 
- 1. Check Windows snapshot builder logs https://windows.php.net/downloads/snaps/
-    the last revision.
+ 1. Check the tests at https://travis-ci.org/php/php-src/builds.
 
- 2. Check the tests at https://travis-ci.org/php/php-src/builds.
-
- 3. Run the `scripts/dev/credits` script in php-src and commit the changes in
+ 2. Run the `scripts/dev/credits` script in php-src and commit the changes in
     the credits files in ext/standard.
 
- 4. Checkout the release branch for this release (e.g., PHP-7.4.2) from the main
+ 3. Checkout the release branch for this release (e.g., PHP-7.4.2) from the main
     branch.
 
- 5. Bump the version numbers in `main/php_version.h`, `Zend/zend.h`,
+ 4. Bump the version numbers in `main/php_version.h`, `Zend/zend.h`,
     `configure.ac` and possibly `NEWS`. Do not use abbreviations for alpha and
     beta. Do not use dashes, you should `#define PHP_VERSION "7.4.22RC1"` and
     not `#define PHP_VERSION "7.4.22-RC1"`.
@@ -80,31 +76,31 @@ explained at the end of this document in
     need to be rebuilt with each bump. Do *not* bump the API versions after
     RC1.
 
- 6. Compile and run `make test`, with and without ZTS, using the right Bison and
+ 5. Compile and run `make test`, with and without ZTS, using the right Bison and
     re2c version (for PHP 7.4, minimum Bison 3.0.0 and re2c 0.13.4 are used).
 
- 7. Check `./sapi/cli/php -v` output for version matching.
+ 6. Check `./sapi/cli/php -v` output for version matching.
 
- 8. If all is right, commit the changes to the release branch:
+ 7. If all is right, commit the changes to the release branch:
 
     ```sh
     git commit -a
     ```
 
- 9. Tag the repository release branch with the version, e.g.:
+ 8. Tag the repository release branch with the version, e.g.:
 
     ```sh
     git tag -u YOURKEYID php-7.4.2RC2
     ```
 
-10. Bump the version numbers in `main/php_version.h`, `Zend/zend.h`,
+ 9. Bump the version numbers in `main/php_version.h`, `Zend/zend.h`,
     `configure.ac` and `NEWS` in the *main* branch (PHP-7.4 for example) to
     prepare for the **next** version. For example, if the RC is "7.4.1RC1" then
     the new one should be `7.4.2-dev` - regardless if we get a new RC or not.
     This is to make sure `version_compare()` can correctly work. Commit the
     changes to the main branch.
 
-11. Push the changes to the `php-src`. 
+10. Push the changes to the `php-src`. 
 
     Non stable release branches don't need to be pushed 
       (a local temporary branch should be used).
@@ -115,21 +111,21 @@ explained at the end of this document in
     git push origin {release branch}
     ```
 
-12. Run: `./scripts/dev/makedist php-7.4.0RC2`, this will export the tree,
+11. Run: `./scripts/dev/makedist php-7.4.0RC2`, this will export the tree,
     create `configure` and build three tarballs (gz, bz2 and xz).
 
-13. Run `./scripts/dev/gen_verify_stub <version> [identity]`, this will sign the
+12. Run `./scripts/dev/gen_verify_stub <version> [identity]`, this will sign the
     tarballs and output verification information to be included in announcement
     email.
 
-14. Copy those tarballs (scp, rsync) to downloads.php.net, in your homedir there
+13. Copy those tarballs (scp, rsync) to downloads.php.net, in your homedir there
     should be a directory `public_html/`. Copy them into there. If you do not
     have this directory, create it.
 
-15. Now the RC can be found on https://downloads.php.net/~yourname,
+14. Now the RC can be found on https://downloads.php.net/~yourname,
     e.g. https://downloads.php.net/~derick/.
 
-16. Once the release has been tagged, contact the release-managers@ distribution
+15. Once the release has been tagged, contact the release-managers@ distribution
     list so that Windows binaries can be created. Once those are made, they can
     be found at https://windows.php.net/download.