pbacsko commented on code in PR #315: URL: https://github.com/apache/yunikorn-site/pull/315#discussion_r1229314790
########## src/pages/community/release_procedure.md: ########## @@ -54,62 +57,90 @@ The instructions and tools obey the ASF [release policy](http://www.apache.org/l ## Release Procedure Simplified release procedure: -1. Create a release branch for the target release in all git repos, such as `branch-0.8` +1. Create a release branch for the target release in all git repos, such as `branch-1.3` 2. Stabilize the release by fixing test failures and bugs only -3. Tag update release for a new version to prepare a release candidate, e.g `v0.8.0-1` for RC1 +3. Tag update release for a new version to prepare a release candidate, e.g `v1.3.0-1` for RC1 4. Update the CHANGELOG 5. Configure [release-configs.json](https://github.com/apache/yunikorn-release/tree/master/tools/release-configs.json) 6. Run script [build-release.py](https://github.com/apache/yunikorn-release/tree/master/tools/build-release.py) to generate source code tarball, checksum and signature. 7. Voting and releasing the candidate ## Step-by-step procedure -### Tag and update release for version Branching and tagging can, and in most cases will, require changes in the go mod files. + +### Branching Branching is part of the release preparation and often has happened some time before the release process starts. +As an example the steps to create the branch for the `v1.3.0` release: +```shell script +git checkout -b branch-1.3 master +git push -u origin branch-1.3 +``` + +### Tag for RCs Review Comment: This is a better place to elaborate on the tagging details. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
