[Umbrella] Automate updates to k-sigs/release-notes

[jeefy]

This outlines the primary efforts identified to get the ball rolling in automating updates to the release notes website. Doing this will ensure timely updates to relnotes.k8s.io and removes the human bottleneck. :) Yay!

• Update the release-notes golang tool to automatically create a PR against the k-sigs/relnotes repo.
  This is going to be the majority of effort, and some sane defaults will need to be put in place to handle things like checking for a fork of the repo.
• Update the relnotes bash script to, instead, generate/include a link to relnotes.k8s.io for the specific release
• Propose and change cadence of "weekly release notes updates" to match the alpha/beta/RC cuts.
• Document (within the Release Team handbook) policy around handling alpha/beta/RC PRs to k-sigs/release-notes (For the release team updates, link to the PR's preview site)

/assign @onyiny-ang @saschagrunert
/priority important-soon
/sig release
/area release-eng
/cc

[jeefy]

@onyiny-ang @saschagrunert If I missed anything let me know and I'll update this. :)

[saschagrunert]

@paulbouwer, @kcmartin @cartyc let's follow up and check how we could start working on this.

From the website point of view I started proposing a PR today which should give us the ability to hide unpublished releases: kubernetes-sigs/release-notes#83

[saschagrunert]

Hey, I'm now moving forward with this, so there are three automation enhancements ready for review:

• Preserve markdown order when generating release notes #875
• Allow specifying a repo-path for local clones #879
• Add SHA auto discovery feature for release notes #880

If we can get these in I can continue with the PR creation automation.

[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

[markjacksonfishing]

/remove-lifecycle stale
Going to keep this open as I think it is worthy

[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

[puerco]

/remove-lifecycle stale
This is now in krel but we are actively working on it

[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

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten

[saschagrunert]

Most of the mentioned enhancements are now in place, whereas the relnotes bash script does not exist any more. We have additional improvements planned which can be tracked in other issues.

Let’s 🙂
/close

[k8s-ci-robot]

@saschagrunert: Closing this issue.

In response to this:

Most of the mentioned enhancements are now in place, whereas the relnotes bash script does not exist any more. We have additional improvements planned which can be tracked in other issues.

Let’s 🙂
/close

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.