Update instructions for patch releases

[lbernick]

Thanks @JeromeJu for catching this! Our patch release docs are out of date.

We should discuss the process in this doc and decide if we want to make changes to it, as we aren't following the process right now. Also, we should add instructions for using the new cherry-pick automation, and give some examples of git cherry-pick commands and how to create a cherry-pick PR in case manual rebase is needed.

[lbernick]

Discussion at this week's Pipeline WG:

• we used to use milestones for patch releases but started deleting milestones after the release was done. If we want to continue doing so we'd need someone to take on the milestone (possibly the release captain can also handle patch releases, but this is a bit unfair to LTS release captains).
• would be nice to have more automation for patch releases (but shouldn't block updates to these docs)
• the "needs-cherry-pick" label might not be super useful anymore, especially since it doesn't specify which release(s) a PR needs to be cherry-picked to

AIs for right now are just to update the docs to explain how to use the cherry-pick prow command, and an example git cherry-pick command that can be used if manual rebase is needed.

[vdemeester]

• we used to use milestones for patch releases but started deleting milestones after the release was done. If we want to continue doing so we'd need someone to take on the milestone (possibly the release captain can also handle patch releases, but this is a bit unfair to LTS release captains).

I don't think we delete them though, just mark them as completed.

• would be nice to have more automation for patch releases (but shouldn't block updates to these docs)

Definitely !

[tekton-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
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 with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[tekton-robot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

[tekton-robot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

[tekton-robot]

@tekton-robot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

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.