Sig-release: Update and clarify release notes process for k/k pull requests

[guineveresaenger]

We have a lot of new processes and tools for improving our release notes, and need to make sure that someone opening a k/k pull request does not experience major stumbling blocks.

Currently, the pull request template links to the release notes doc but the process is not explained too well, and in fact links back to a "brief example" in the pull request template, which a) doesn't exist, and b) this experience is circular. 😨

We also have https://relnotes.k8s.io/ which should be mentioned somewhere.

There is automation underway that I don't have any details on - if @justaugustus could elaborate?

/sig contributor-experience
/sig testing
/sig release

/cc @simplytunde
/cc @saschagrunert
/cc @onyiny-ang
/cc @justaugustus
/cc @jeefy

[saschagrunert]

Thanks for the issue creation @guineveresaenger 🙏 We still have to implement the display of the new docs section in the release notes website. I will propose a PR in the next couple of days if no one else is already planning to do this.

[guineveresaenger]

@saschagrunert do we have any updates on this? Thank you! 🙇‍♀

[saschagrunert]

@saschagrunert do we have any updates on this? Thank you!

Yes, the major implementation has been done in

• https://github.com/kubernetes-sigs/release-notes/pull/76
• https://github.com/kubernetes-sigs/release-notes/pull/81

We still want to be able to filter these docs on the website, where I will start working on corresponding issue (https://github.com/kubernetes-sigs/release-notes/issues/82) in the upcoming days.

For sake of automation we have this one, but it's not directly related to the additional docs section:

• https://github.com/kubernetes/release/issues/834

[saschagrunert]

Hey @guineveresaenger as an update the referencing PR (https://github.com/kubernetes/kubernetes/pull/81159) got merged. We still have these two open

• https://github.com/kubernetes/community/pull/4004
• https://github.com/kubernetes/kubernetes/pull/81278

Do you think we can drop https://github.com/kubernetes/kubernetes/pull/81278 from referencing here from here since it's already related to https://github.com/kubernetes/sig-release/issues/668 ?

[guineveresaenger]

@saschagrunert yes, that sounds right to me. and 🎉 for getting that merged!

[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]

@guineveresaenger do you think we can close this issue? We're tracking multiple technical enhancements already in release engineering, whereas regarding the contributor experience we still have this one open: https://github.com/kubernetes/community/issues/484

[justaugustus]

At this stage, I think we've sufficiently documented and improved the process to close this out.

/close

[k8s-ci-robot]

@justaugustus: Closing this issue.

In response to this:

At this stage, I think we've sufficiently documented and improved the process to close this out.

/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.