So I've been in the process of proposing use of the Prow release-note plugin <https://git.k8s.io/community/contributors/guide/release-notes.md> for easier compilation of release notes for our next dot release. As part of that, PR https://github.com/shipwright-io/build/pull/585 was intended to propose a PR template that would facilitate use of that plugin and start the discussion. Now, for the unintended. We needed the OpenShift Test Platform team to approve changes to the prow config for our repo before we could tag that change for merge when we were ready. However, they inadvertently merged that change instead of only adding the approve label. So, what to do in the interim: - I've added the 'release-note-none' and 'release-note' labels needed to make the plugin happy and not block PR merge. Approvers (i.e. folks in the OWNERS file) should be able to add the 'release-note-none' label manually while we sort out https://github.com/shipwright-io/build/pull/585 - Until the PR template is updated, if you'd like to tag your PR for a release note, you can follow the process described at https://git.k8s.io/community/contributors/guide/release-notes.md which will result in the `release-note` label getting added to your PR. - Or I can pursue reverting the enablement of the plugin, where I again need approval from the test platform team, and we would then need to repeat the process if we wanted to use it. Pending reaching a consensus today via PR/slack/email, I'll add this to the Monday agenda. Apologies for the unintended churn in our process as it currently stands.