Build release notes for alpha.0 and beta.0 releases

[saschagrunert]

We should build the release notes for both alpha.0 and beta.0 releases as well which is currently not the case. This is also the reason why anago still removes the unnecessary CHANGELOG/CHANGELOG-x.y.md files from the release branch on its creation:

release/anago

Lines 561 to 573 in 3c23261

	# Clear all CHANGELOG-N.NN.md files on the branch and insert the
	# generated one, if # $PARENT_BRANCH==master, which seems to be in the
	# weeks between branch creation the first official release of the branch.
	# TODO: can this condition on whether the branch is "beta" or "rc" and be
	# more simply readable to a maintainer?
	if [[ "$PARENT_BRANCH" == "master" && "$branch" != "master" ]]; then
	logecho -n "Remove any previous CHANGELOG-*.md files: "
	logrun -s git rm -f "$CHANGELOG_DIR"/CHANGELOG-*.md || return 1
	logecho -n "Copy master $CHANGELOG_FILEPATH to $branch branch: "
	logrun -s git checkout master -- $CHANGELOG_FILEPATH || return 1
	logecho -n "Committing deleted CHANGELOG-*.md files: "
	logrun -s git commit -am "Delete extraneous CHANGELOG-*.md files on branch." || return 1
	fi

This ☝️ code part should not be done by anago but the krel changelog command invocation to have a single point of responsibilities inside our tooling.

I suggest in keeping this issue open and address it after/during the migration of anago to krel.

Refers to #918

[xmudrii]

@saschagrunert What is the status of this issue? Should we move it away from the v1.18 milestone? Are you still interested to work on this one or should we reassign it?

[saschagrunert]

@saschagrunert What is the status of this issue? Should we move it away from the v1.18 milestone? Are you still interested to work on this one or should we reassign it?

The work has not started yet. I guess we can tackle that issue when we're moving to a krel based anago version, which has been started in #1106

[xmudrii]

Thanks for the update! I'll move this issue to the v1.19 milestone for now.
/milestone v1.19

[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

[saschagrunert]

/remove-lifecycle stale

[saschagrunert]

I think it is intended to not create release notes for those .0 alphas and betas. We only create them with the first alpha, because then we would actually have something to diff to.