diff --git a/releasenotes/notes/fix_auth_issue_for_root_path-b15e1c4e92e4e8b1.yaml b/releasenotes/notes/fix_auth_issue_for_root_path-b15e1c4e92e4e8b1.yaml
new file mode 100644
index 000000000..f98f8dfbb
--- /dev/null
+++ b/releasenotes/notes/fix_auth_issue_for_root_path-b15e1c4e92e4e8b1.yaml
@@ -0,0 +1,7 @@
+---
+fixes:
+  - |
+    When access the root path of Zaqar service, for example:
+    curl GET http://127.0.0.1:8888/, user will see 401 error. Which
+    will cause some front end proxy (like HAProxy) to complain. Now this issue
+    has been fixed.
diff --git a/releasenotes/notes/show_default_attributes_for_queue-3d87333752484c87.yaml b/releasenotes/notes/show_default_attributes_for_queue-3d87333752484c87.yaml
new file mode 100644
index 000000000..844acf0ba
--- /dev/null
+++ b/releasenotes/notes/show_default_attributes_for_queue-3d87333752484c87.yaml
@@ -0,0 +1,8 @@
+---
+features:
+  - Currently Zaqar can support more built-in/reserved attributes in queue.
+    For now there are two important attributes 'max_messages_post_size' and
+    'max_message_ttl'. With this feature, when user query queues Zaqar will show
+    those two attributes (read from config file if there is no customized value
+    from user) in queue metadata so that user can know what value it is.
+
diff --git a/releasenotes/notes/user_ipv6_sockets-1e1b436de6b81ae3.yaml b/releasenotes/notes/user_ipv6_sockets-1e1b436de6b81ae3.yaml
new file mode 100644
index 000000000..3d1f22cd1
--- /dev/null
+++ b/releasenotes/notes/user_ipv6_sockets-1e1b436de6b81ae3.yaml
@@ -0,0 +1,7 @@
+---
+fixes:
+  - In IPv6 management network environment, starting Zaqar server will
+    run into 'Address family for hostname not support' error when use WSGI
+    simple server. The root cause is that Python's TCPServer implementation
+    is hard-coded to use IPv4, even in IPv6 environments. Now this issue has
+    been fixed.