diff --git a/.github/release-drafter.yml b/.github/release-drafter.yml
index 7f083a093..eaf06559d 100644
--- a/.github/release-drafter.yml
+++ b/.github/release-drafter.yml
@@ -7,6 +7,9 @@ categories:
   - title: '⚠️ Breaking Changes'
     labels:
       - 'release/breaking-change'
+  - title: '🐛 Bug Fixes'
+    labels:
+      - 'release/bugfix'
 change-template: '- $TITLE @$AUTHOR (#$NUMBER)'
 template: |
   This is a draft for the next release.
@@ -16,3 +19,7 @@ template: |
   ## Changes
 
   $CHANGES
+
+  ## Contributors
+
+  $CONTRIBUTORS
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index f32cbac40..1b957eb23 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -93,6 +93,7 @@ This is a set of practices we try to live by when developing KUDO. These are jus
 - Labels: If your PR includes either **breaking changes** or should get additional attention in the release, add one of these label:
   - `release/highlight` For a big new feature, an important bug fix, the focus of the current release
   - `release/breaking-change`  For anything that breaks backwards compatibility and requires users to take special care when upgrading to the new version
+  - `release/bugfix` For noteworthy bugfixes
 
 - For a piece of work that takes >3-5 days, pair with somebody
 - When you pair with somebody, don't forget to appreciate their work using [co-authorship](https://help.github.com/en/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors)
diff --git a/RELEASE.md b/RELEASE.md
index 2b4c69992..f1fb4a288 100644
--- a/RELEASE.md
+++ b/RELEASE.md
@@ -27,7 +27,7 @@ The official binaries for KUDO are created using [goreleaser](https://goreleaser
 1. Ensure you are logged into Docker hub and have rights to push to kudobuilder.
 1. Tag repo with expected release `git tag -a v0.2.0 -m "v0.2.0"`  && push tag `git push --tags`.
 1. Invoke goreleaser `goreleaser --rm-dist`.
-1. Update the GH release with Release highlights and a changelog. There is a draft that contains categorized changes since the last release, use this as a template. It provides categories for highlights and breaking changes, the issues there should get a more detailed description.
+1. Update the GH release with Release highlights and a changelog. There is a draft that contains categorized changes since the last release, use this as a template. It provides categories for highlights and breaking changes, the issues there should get a more detailed description. After the contents are copied, the draft can be deleted.
 1. Send an announcement email to `kudobuilder@googlegroups.com` with the subject `[ANNOUNCE] Kudo $VERSION is released`
 1. Create a PR against [kudobuilder/kudo.dev](https://github.com/kudobuilder/kudo.dev) with an according [blog post](https://kudo.dev/internal-docs/blog-index.html#release-posts).
 1. Run `./hack/generate_krew.sh` and submit the generated `kudo.yaml` to https://github.com/kubernetes-sigs/krew-index/.