Add tip to speed up release process to releasing doc

[Sunnatillo]

This PR adds tip to speed up release process to releasing doc.

Fixing issues identified with hack/verify-release.sh script would really speed up release process.

[metal3-io-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign lentzi90 for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[tuminoid]

This is already part of each repositorys docs/releasing.md, not sure if it needs to be duplicated here?

[Sunnatillo]

This is already part of each repositorys docs/releasing.md, not sure if it needs to be duplicated here?

docs/releasing.md is for repo specific. I followed that. For each repo I had to open and wait few PRs until release proceeds. The idea here to check each release branch in each repo at the beginning of release process.

[tuminoid]

This is already part of each repositorys docs/releasing.md, not sure if it needs to be duplicated here?

docs/releasing.md is for repo specific. I followed that. For each repo I had to open and wait few PRs until release proceeds. The idea here to check each release branch in each repo at the beginning of release process.

I don't see the benefit as its a pre-check for before cutting anything, same as this doc,, but if you feel this benefits someone, then lets merge it.

[tuminoid]

/lgtm

[metal3-io-bot]

New changes are detected. LGTM label has been removed.

[tuminoid]

The more you edit this, the more I dislike it. The point of verify-release.sh is to make sure something wasn't missed. Its not supposed to be "part" of release process to bump the CVEs etc. All those should've happened as part of normal development process, and the script is just safeguard for verification of that work.

[Sunnatillo]

This paragraph is giving the same idea as here:
https://github.com/metal3-io/baremetal-operator/blob/230a562f7e3b09299f60fc4c9c684b0210707149/docs/releasing.md?plain=1#L18

[Sunnatillo]

This is already part of each repositorys docs/releasing.md, not sure if it needs to be duplicated here?

docs/releasing.md is for repo specific. I followed that. For each repo I had to open and wait few PRs until release proceeds. The idea here to check each release branch in each repo at the beginning of release process.

I don't see the benefit as its a pre-check for before cutting anything, same as this doc,, but if you feel this benefits someone, then lets merge it.

I have updated slightly to clarify my point about speeding up the process.

[metal3-io-bot]

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

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

/lifecycle stale

[smoshiur1237]

We always need to go through release doc from each repo and there it mentioned to run the verify script, I can't foresee any benefits or need of this part. I think we are good without this tip..