diff options
| author | Ferenc Kovacs <tyrael@php.net> | 2015-01-22 21:27:38 +0100 |
|---|---|---|
| committer | Ferenc Kovacs <tyrael@php.net> | 2015-01-22 21:27:38 +0100 |
| commit | 61ad5e24ea2b17bf9a40e1238ffd53daad37df5e (patch) | |
| tree | 01ff1e9186e362e434d0c687be6e5496407e5761 | |
| parent | b3b155ffe24802f0c57aac11c2d19d73ac6239e9 (diff) | |
| download | php-git-61ad5e24ea2b17bf9a40e1238ffd53daad37df5e.tar.gz | |
fix some factual errors in the process
| -rw-r--r-- | README.RELEASE_PROCESS | 13 |
1 files changed, 7 insertions, 6 deletions
diff --git a/README.RELEASE_PROCESS b/README.RELEASE_PROCESS index 21305f2993..de166e418f 100644 --- a/README.RELEASE_PROCESS +++ b/README.RELEASE_PROCESS @@ -183,11 +183,11 @@ last commit id to web/php.git, then, mirrors will now sync Getting the stable release announced ------------------------------------ -1. Run the bumpRelease script for phpweb on your local checkout +1. Update phpweb/include/releases.inc with the old release info + (updates the download archives) - a. ``php bin/bumpRelease 5`` to create the release file (releases/x_y_z.php) - The release announcement file should list in detail security fixes and - changes in behavior (whether due to a bug fix or not). + a. You can run ``php bin/bumpRelease 5`` if you are making a release for the + highest branch, otherwise you have to do this manually, see point 1.b b. In case multiple PHP minor versions are in active development you have to manually copy the old information to include/releases.inc @@ -207,8 +207,9 @@ Getting the stable release announced f. if the windows builds aren't ready yet prefix the "windows" key with a dot (".windows") -3. Update phpweb/include/releases.php with the old release info - (updates the download archives) +3. Create the release file (releases/x_y_z.php) + Usually we use the same content as for point 6, but included in php template + instead of the release xml. 4. Update php-qa/include/release-qa.php and add the next version as an QARELEASE (prepare for next RC) |