Sig-release: Improve doc release handbook

[daminisatya]

1. Explain why we need release-[current release], dev-[future release] branches.
2. Importance of the Integration branch and the contents to go in the issue description.
3. Example message to send to the enhancement owners to followup for docs

[daminisatya]

/assign @daminisatya

[daminisatya]

/sig release
/area release-team
/kind documentation

[alejandrox1]

/cc @VineethReddy02 @sethmccombs @irvifa @savitharaghunathan @iheanyi1
ptal

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[savitharaghunathan]

/remove-lifecycle rotten

[savitharaghunathan]

1 & 2 are done. 3 is tracked in a separate effort. Closing this issue.

/close

[k8s-ci-robot]

@savitharaghunathan: Closing this issue.

In response to this:

1 & 2 are done. 3 is tracked in a separate effort. Closing this issue.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.