Add updating publishing-bot rules to Branch Mgmt handbook

Signed-off-by: Marko Mudrinić <[email protected]>

.github/ISSUE_TEMPLATE/cut-release.md

@@ -62,6 +62,10 @@ Collect Metrics:
 Run krel history --branch release-1.mm --date-from 2021-mm-dd
 http://bit.ly/relmanagers-handbook#adding-data-about-the-cloud-build-jobs
 
+Finish post-release branch creation tasks:    ← Only for rc.0 release
+See the Branch Creation section of the handbook for more details:
+http://bit.ly/relmanagers-handbook#branch-creation
+
 Help? Ring @release-managers on slack!
 
 -->
@@ -81,7 +85,7 @@ Help? Ring @release-managers on slack!
 - [ ] Notify #release-management: <!-- Paste link to slack -->
 - [ ] Send notification: <!-- Paste link to kubernetes-dev email -->
 - [ ] Collect metrics and add them to the `Release steps` table below
-
+<!-- ONLY FOR RC.0 RELEASE - [ ] Finish post-release branch creation tasks -->
 
 ## Release Tools Version
 

release-engineering/role-handbooks/branch-manager.md

@@ -41,6 +41,7 @@
     - [Update milestone requirements](#update-milestone-requirements)
     - [Update e2e variants](#update-e2e-variants)
     - [Generate release branch jobs](#generate-release-branch-jobs)
+    - [Update publishing-bot rules](#update-publishing-bot-rules)
   - [Configure Merge Automation](#configure-merge-automation)
     - [Tide](#tide)
     - [Code Freeze](#code-freeze)
@@ -587,6 +588,17 @@ This task should be done after the release is complete and previous PRs are merg
 
 1. [Announce in #sig-release and #release-management](https://kubernetes.slack.com/archives/C2C40FMNF/p1565746110248300?thread_ts=1565701466.241200&cid=C2C40FMNF) that this work has been completed
 
+#### Update publishing-bot rules
+
+The Kubernetes Publishing Bot is responsible for:
+
+* ensuring that the master and release branches in the staging repositories are in-sync with the appropriate branches in `kubernetes/kubernetes`
+* creating tags in the staging repositories for each Kubernetes release
+
+It's required to create the appropriate publishing-bot rules for the publishing-bot to work with the release branches. Once a new release branch is created in `kubernetes/kubernetes`, the Release Manager needs to update the publishing-bot rules as described in the [`k/publishing-bot` repository](https://git.k8s.io/publishing-bot#updating-rules).
+
+Here's an [example PR](https://github.com/kubernetes/kubernetes/pull/100616).
+
 [sig-release-x.y-blocking]: https://testgrid.k8s.io/sig-release-1.17-blocking
 [`krel ff`]: https://git.k8s.io/release