diff --git a/docs/source/release_notes_1.15.rst b/docs/source/release_notes_1.15.rst
index f144d729..bb42d4b1 100644
--- a/docs/source/release_notes_1.15.rst
+++ b/docs/source/release_notes_1.15.rst
@@ -152,14 +152,105 @@ With this change:
 
 
 
-
 System changes
 --------------
 
-Deprecations
-^^^^^^^^^^^^
+Volume policy support
+^^^^^^^^^^^^^^^^^^^^^
+
+| PR: https://pagure.io/koji/pull-request/622
+
+Koji has for many years had the ability to split its storage across multiple
+volumes. However, there is no automatic process for placing builds onto
+volumes other than the primary. To do so often requires a lot of manual work
+from an admin.
+
+This feature:
+
+    * adds a volume policy check to the key import pathways
+    * adds an applyVolumePolicy call to apply the policy to existing builds
+
+The hub consults the volume policy at various points to
+determine where a build should live. This allows admins to make rules like:
+
+    all kernel builds go to the volume named kstore
+    all builds built from the epel-7-build tag go to the volume named epel7
+    all builds from the osbs content generator go to the volume named osbs
+
+The default policy would places all builds on the default volume.
+
+See also: :doc:`volumes`
+
+messagebus plugin changes
+^^^^^^^^^^^^^^^^^^^^^^^^^
+
+| PR: https://pagure.io/koji/pull-request/537
+
+There are two notable changes to the messagebus plugin this release.
 
 
-Removed calls
-^^^^^^^^^^^^^
+Deferred sending
+""""""""""""""""
+
+
+Similar to the current behavior of the protonmsg plugin. Messages are queued
+up during hub calls and only sent out during the ``postCommit`` callback.
+
+This avoids sending messages about failed calls, which can be confusing to
+message consumers (e.g. build state change messages about a build that does
+not exist because it failed to import).
+
+Test mode
+"""""""""
+
+The plugin now looks for a boolean ``test_mode`` option. If it is true, then
+the messages are still queued up, but not actually sent. This makes it
+possible to enable the plugin in test environments without having to set up a
+separate message bus.
+
+
+No notifications for disabled users or hosts
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+| PR: https://pagure.io/koji/pull-request/615
+
+
+Koji will no longer send out email notifications to disabled users or
+to users corresponding to a host.
+
+
+Protonmsg plugin changes
+^^^^^^^^^^^^^^^^^^^^^^^^
+
+protonmsg: include the arch in the headers of rpm sign messages
+
+| PR: https://pagure.io/koji/pull-request/657
+| PR: https://pagure.io/koji/pull-request/651
+
+There are two changes to how the protonmsg plugin handles rpmsign events:
+
+    1. The arch of the rpm is included in messages
+    2. The message are omitted when the sigkey is empty
+
+
+
+Replace pycurl with requests
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+| PR: https://pagure.io/koji/pull-request/601
+
+All uses of the pycurl library have been replaced with calls
+to python-requests, so pycurl is no longer required.
+
+
+drop importBuildInPlace call
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+| PR: https://pagure.io/koji/pull-request/606
+
+The deprecated ``importBuildInPlace`` call has been dropped.
+
+This call was an artifact of a particular bootstrap event that happened a long
+time ago. It was never not really documented or recommended for use.
+