diff --git a/Release_Notes_3.0.5.md b/Release_Notes_3.0.5.md
new file mode 100644
index 0000000..2468759
--- /dev/null
+++ b/Release_Notes_3.0.5.md
@@ -0,0 +1,64 @@
+AppArmor 3.0.4 was released 2022-02-09.
+
+# Introduction
+
+AppArmor 3.0.4 fixes a build error in AppArmor 3.0.3 that could cause AppArmor builds to fail during tests in some build environments. It is a maintenance release of the user space components
+of the AppArmor security project. The kernel portion of the project
+is maintained and pushed separately.
+
+This version of the userspace should work with all kernel versions from
+2.6.15 and later (some earlier version of the kernel if they have the
+apparmor patches applied).
+
+The kernel portion of the project is maintained and pushed separately.
+
+# Notes
+
+
+
+# Obtaining the Release
+
+There are two ways to obtain this release either through gitlab or a tarball in launchpad. 
+
+**Important note:** the gitlab release tarballs differ from the launchpad release tarballs. The launchpad release tarball has a couple processing steps already performed:
+
+* libapparmor `autogen.sh` is already done, meaning distros only need to use ./configure in their build setup
+* the docs for everything but libapparmor have already been built
+
+### gitlab
+- https://gitlab.com/apparmor/apparmor/-/releases/v3.0.5
+
+### Launchpad
+
+  -   <https://launchpad.net/apparmor/3.0/3.0.5/+download/apparmor-3.0.5.tar.gz>
+  -   sha256sum: 
+  -   signature: <https://launchpad.net/apparmor/3.0/3.0.5/+download/apparmor-3.0.5.tar.gz.asc>
+
+# Changes in this Release
+
+These release notes cover all changes between 3.0.4 (939530b2b89ee26bef52ccfe3d271629f4da097d) and 3.0.5 () [apparmor-3.0 branch](https://gitlab.com/apparmor/apparmor/tree/apparmor-3.0).
+
+
+## Init
+
+## Library
+
+## Policy Compiler (a.k.a apparmor_parser)
+
+## Utils
+
+## Policy
+
+#### abstractions
+
+#### profiles
+
+
+# Additional Note
+
+There is a semantic change in the 4.8 kernel (commit
+9f834ec18defc369d73ccf9e87a2790bfa05bf46) that affects apparmor policy
+enforcement. Specifically it affects when the m permission bit is
+checked for elf binary executables. Policy and tests within apparmor
+2.12 and later have been updated to support running on pre 4.8 and 4.8+ kernels.
+