Update the Release Script and Doc for a Patch Release

[danehans]

#291 adds initial support for release automation. The script and release doc hardcodes the patch version as 0. Update the hard-coded patch version in the script and doc to use a variable for the patch version.

Note: The best time to fix this issue is when cutting the first patch release.

[adarshagrawal38]

/assign

[danehans]

@adarshagrawal38 thanks for your willingness to help the project. However, a maintainer should be assigned to this issue during the first patch release. We have several other issues that need attention if you can help elsewhere.

[kfswain]

/assign danehans
/assign ahg-g
/assign

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten