📖 Add release tasks doc and corresponding issue template

[sbueringer]

What this PR does / why we need it:

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):

Let's ignore the markdown checker. The links won't actually be broken after merge.

Examples:

• Example release tracking issue: Tasks for v1.4 release cycle sbueringer/cluster-api#80
• Issue creation: https://github.com/sbueringer/cluster-api/issues/new/choose
  

Part of #7389

[sbueringer]

@ykakarap @dntosas @cpanato @hackeramitkumar
@oscr @sayantani11 @VibhorChinda
@furkatgofurov7 @nawazkh @aniruddha2000 @alexander-demicev

@CecileRobertMichon @enxebre @fabriziopandini @vincepri

Hey folks, please take a look :)

[nawazkh]

Thank you for putting this together!
I just have one request to update my slack user ID in the doc below :)

[fabriziopandini]

This is outstanding work, kudos!
only a few nits from my side.

@ykakarap let's make sure all the folks in the release team take a look at this PR, but also that everyone is aware that we can improve this iteratively in follow up PRs

[ykakarap]

cc @kubernetes-sigs/cluster-api-release-team

[sbueringer]

Fixed some of the easier findings. Will push another commit with the ones that take more time soon.

[sbueringer]

cc @joekr (PTAL :))

[sbueringer]

Thank you very much for the reviews. All findings should be addressed or answered.

I updated the example issue accordingly:

• Example release tracking issue: Tasks for v1.4 release cycle sbueringer/cluster-api#80
• Issue creation: https://github.com/sbueringer/cluster-api/issues/new/choose

Also testing the process for v1.3: #7527 (as applicable)

[hackeramitkumar]

/lgtm

[hackeramitkumar]

@sbueringer , Before merging this PR , we should squash the commits to a single commit.

[sbueringer]

Before merging this PR , we should squash the commits to a single commit.

Will do, just waiting to get the conversations above resolved and consensus. Then it's a quick squash + lgtm/approve.

[CecileRobertMichon]

/lgtm

I think this is a great start, huge thank you @sbueringer for putting this together so thoroughly and eloquently 💯

This will be a living doc and the release team and docs manager (@oscr 👀) can keep improving it as we go but I'm in favor of merging this for now so we have it in place for the v1.4 release cycle start.

[dntosas]

thnx for your effort @sbueringer , nice and essential work 🚀

[sbueringer]

Everything should be adressed now + squashed:

• added a note about alphabetically sorting release note entries
• added a note about checking for CI signal as a first step in cutting a release
• added a note in release-team.md to link to release-tasks
• updated release date for v1.2.x releases during the v1.4 release cycle

Thx for the reviews :)

[sbueringer]

Given all the lgtm's above I would merge this relatively soon
@fabriziopandini WDYT?

[fabriziopandini]

/lgtm
/approve
Go for it! feel free to unhold at your convenience
Echoing from slack:
This doc provides a great foundation for the first iteration; let’s merge it asap, keep track of areas of improvement in issues, and iterate while we learn during the next cycle

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fabriziopandini

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [fabriziopandini]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[fabriziopandini]

/hold

[sbueringer]

Thx!
I'll merge tomorrow if there are no objections until then together with the other "lazy consensus" PRs.

[sbueringer]

/hold cancel

[sbueringer]

/cherry-pick release-1.3

[k8s-infra-cherrypick-robot]

@sbueringer: new pull request created: #7563

In response to this:

/cherry-pick release-1.3

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.