update to release process

[kensipe]

Updates for a number of things:

1. Moved release preconditions to a precondition block.
2. Ignore the krew file kudo.yaml which is generated (it shouldn't dirty the build)
3. Removing author from change logs... this is often a group effort. the author is captured as a contributor.
4. there is no release blog... we need to have a blog for releases but it is not the release managers responsibility IMO. There is a note added to encourage it.

Signed-off-by: Ken Sipe kensipe@gmail.com

[porridge]

I was wondering how we could increase the chance of actually creating a blog post regularly.

Do you think it would it make sense to add a step for the release engineer to start a blank, draft blog PR for the next release after finishing this one? This would in turn allow us to point contributors at it from our pull request template in order to encourage contributions to the upcoming release's blog post as we go along?

[porridge]

Suggested change

	# created with krew gen scripts
	# created by /hack/generate_krew.sh during release

[kensipe]

@porridge after some thought... I'm not sure how to encourage a blog action here... it is noted... repeating it doesn't make sense. A task of creating blank fill in the blank that will be opened for a long time doesn't really do much IMO other than give the release manager another task. If a blog is to done for a release which is focused on highlighting a new feature (instead of just repeating the release notes) then it seems like a project task needs to be created and someone needs to be assigned to it. I would rather have the release manager create a blog task than a PR with a blank or templated page.

We should talk about this as a team and make an update based on outcome instead of holding up this PR.