DevFW-CICD/ingress-nginx-helm
12
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Merge pull request #1228 from danielqsj/update-release

Browse source 
Update release doc in getting-started.md
This commit is contained in:
Manuel Alejandro de Brito Fontes 2017-08-23 13:02:27 -04:00 committed by GitHub
commit 83fc69284f
1 changed files with 4 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
docs/dev/getting-started.md
View file

@ -127,14 +127,15 @@ $ make push TAG=0.8.0 PREFIX=gcr.io/google_containers/glbc
Please follow these guidelines to cut a release: Please follow these guidelines to cut a release:
* Update the [release](https://help.github.com/articles/creating-releases/getting_started.md) * Update the [release](https://help.github.com/articles/creating-releases/)
page with a short description of the major changes that correspond to a given page with a short description of the major changes that correspond to a given
image tag. image tag.
* Cut a release branch, if appropriate. Release branches follow the format of * Cut a release branch, if appropriate. Release branches follow the format of
`controller-release-version`. Typically, pre-releases are cut from HEAD. `controller-release-version`. Typically, pre-releases are cut from HEAD.
All major feature work is done in HEAD. Specific bug fixes are All major feature work is done in HEAD. Specific bug fixes are
cherry-picked into a release branch. cherry-picked into a release branch.
* If you're not confident about the stability of the code, tag it as * If you're not confident about the stability of the code,
alpha or beta. Typically, a release branch should have stable code. [tag](https://help.github.com/articles/working-with-tags/) it as alpha or beta.
Typically, a release branch should have stable code.