github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-09-03 18:27:49 +00:00
Code Issues Projects Releases Wiki Activity

Merge pull request #18847 from caesarxuchao/release-doc

Browse Source 
Auto commit by PR queue bot
This commit is contained in:
k8s-merge-robot
2015-12-18 10:38:25 -08:00
parent 40e4ce2879 fcca71f7d8
commit 3700036f95
1 changed files with 10 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
docs/devel/releasing.md
View File

@@ -46,6 +46,7 @@ release breaks down into four pieces:
1. cutting/branching the release; 1. cutting/branching the release;
1. building and pushing the binaries; and 1. building and pushing the binaries; and
1. publishing binaries and release notes. 1. publishing binaries and release notes.
1. updating the master branch.
You should progress in this strict order. You should progress in this strict order.
@@ -216,6 +217,15 @@ Finally, from a clone of upstream/master, *make sure* you still have
`RELEASE_VERSION` set correctly, and run `./build/mark-stable-release.sh `RELEASE_VERSION` set correctly, and run `./build/mark-stable-release.sh
${RELEASE_VERSION}`. ${RELEASE_VERSION}`.
### Updating the master branch
If you are cutting a new release series, please also update the master branch:
change the `latestReleaseBranch` in `cmd/mungedocs/mungedocs.go` to the new
release branch (`release-X.Y`), run `hack/update-generated-docs.sh`. This will
let the unversioned warning in docs point to the latest release series. Please
send the changes as a PR titled "Update the latestReleaseBranch to release-X.Y
in the munger".
## Injecting Version into Binaries ## Injecting Version into Binaries
*Please note that this information may be out of date. The scripts are the *Please note that this information may be out of date. The scripts are the