Another README update.

This commit is contained in:
mtail 2019-06-18 19:15:02 -07:00
parent 0fe6ad4b4c
commit 27dd77f4c9
1 changed files with 3 additions and 3 deletions

View File

@ -77,6 +77,9 @@ version of Istio is 0.6 and you wish to introduce 0.7 which has been under devel
1. Edit the file `scripts/gen_archive_site.sh` and add the new archive version 1. Edit the file `scripts/gen_archive_site.sh` and add the new archive version
(in this case release-0.6) to the `TOBUILD` variable. (in this case release-0.6) to the `TOBUILD` variable.
1. Edit the file `data/versions.yml`. Set the `preliminary` field to the next Istio release
("0.8") and the `main` field to the current release ("0.7").
1. Commit the previous edits to your local git repo and push your **master** branch to GitHub. 1. Commit the previous edits to your local git repo and push your **master** branch to GitHub.
1. Create a new release branch off of master, named as release-*major*.*minor*, which in this case would be 1. Create a new release branch off of master, named as release-*major*.*minor*, which in this case would be
@ -94,9 +97,6 @@ name for `istio.git` and `api.git` to point to the release branch. In this case
1. Switch to the istio/istio.io repo and make sure everything is up to date. 1. Switch to the istio/istio.io repo and make sure everything is up to date.
1. In the **master** branch, edit the file `data/versions.yml`. Set the `preliminary` field to the next Istio release
("0.8") and the `main` field to the current release ("0.7").
1. In the **master** branch, edit the file `data/args.yml`. Set the `version` and `full_version` fields to have the version 1. In the **master** branch, edit the file `data/args.yml`. Set the `version` and `full_version` fields to have the version
of the next Istio release. In this case, you would set the fields to "0.8" and "0.8.0" respectively. of the next Istio release. In this case, you would set the fields to "0.8" and "0.8.0" respectively.