doc: release notes for GlusterFS 3.5.7v3.5.7

BUG: 1263307
Change-Id: I5570ddf98ddb130a72cb25443d0c13dccf6f1766
Signed-off-by: Niels de Vos <ndevos@redhat.com>
Reviewed-on: http://review.gluster.org/12957
Tested-by: Gluster Build System <jenkins@build.gluster.com>

1 files changed, 55 insertions, 0 deletions

diff --git a/doc/release-notes/3.5.7.md b/doc/release-notes/3.5.7.md
new file mode 100644
index 00000000000..59c19267326
--- /dev/null
+++ b/doc/release-notes/3.5.7.md
@@ -0,0 +1,55 @@
+## Release Notes for GlusterFS 3.5.7
+
+This is a bugfix release. The [Release Notes for 3.5.0](3.5.0.md),
+[3.5.1](3.5.1.md), [3.5.2](3.5.2.md), [3.5.3](3.5.3.md), [3.5.4](3.5.4.md),
+[3.5.5](3.5.5.md) and [3.5.6](3.5.6.md) contain a listing of all the new
+features that were added and bugs fixed in the GlusterFS 3.5 stable release.
+
+### Bugs Fixed:
+
+- [1283542](https://bugzilla.redhat.com/1283542): glusterfs does not register with rpcbind on restart
+- [1283691](https://bugzilla.redhat.com/1283691): core dump in protocol/client:client_submit_request
+
+### Known Issues:
+
+- The following configuration changes are necessary for 'qemu' and 'samba vfs
+  plugin' integration with libgfapi to work seamlessly:
+
+   1. `gluster volume set <volname> server.allow-insecure on`
+   2. restarting the volume is necessary
+
+       ~~~
+       gluster volume stop <volname>
+       gluster volume start <volname>
+       ~~~
+
+   3. Edit `/etc/glusterfs/glusterd.vol` to contain this line:
+
+       ~~~
+       option rpc-auth-allow-insecure on
+       ~~~
+
+   4. restarting glusterd is necessary
+
+       ~~~
+       service glusterd restart
+       ~~~
+
+   More details are also documented in the Gluster Wiki on the [Libgfapi with qemu libvirt](http://www.gluster.org/community/documentation/index.php/Libgfapi_with_qemu_libvirt) page.
+
+- For Block Device translator based volumes open-behind translator at the
+  client side needs to be disabled.
+
+  ~~~
+  gluster volume set <volname> performance.open-behind disabled
+  ~~~
+
+- libgfapi clients calling `glfs_fini` before a successful `glfs_init` will cause the client to
+  hang as reported [here](http://lists.gnu.org/archive/html/gluster-devel/2014-04/msg00179.html).
+  The workaround is NOT to call `glfs_fini` for error cases encountered before a successful
+  `glfs_init`. This is being tracked in [Bug 1134050](https://bugzilla.redhat.com/1134050) for
+  glusterfs-3.5 and [Bug 1093594](https://bugzilla.redhat.com/1093594) for mainline.
+
+- If the `/var/run/gluster` directory does not exist enabling quota will likely
+  fail ([Bug 1117888](https://bugzilla.redhat.com/show_bug.cgi?id=1117888)).
+