Tracker for the next release of 3.10 (i.e 3.10.1)
REVIEW: https://review.gluster.org/16957 (doc: release-notes for GlusterFS-3.10.1) posted (#1) for review on release-3.10 by Shyamsundar Ranganathan (srangana)
REVIEW: https://review.gluster.org/16957 (doc: release-notes for GlusterFS-3.10.1) posted (#2) for review on release-3.10 by Shyamsundar Ranganathan (srangana)
REVIEW: https://review.gluster.org/16957 (doc: release-notes for GlusterFS-3.10.1) posted (#3) for review on release-3.10 by Shyamsundar Ranganathan (srangana)
COMMIT: https://review.gluster.org/16957 committed in release-3.10 by Shyamsundar Ranganathan (srangana) ------ commit dc4aa17e617b21d9faa00dc5048e3396bde63d95 Author: Shyam <srangana> Date: Mon Mar 27 12:54:17 2017 -0400 doc: release-notes for GlusterFS-3.10.1 Change-Id: Ia825f0fdfffbc1c75c6ac24e27887e9ff96f3dc6 BUG: 1427207 Signed-off-by: Shyam <srangana> Reviewed-on: https://review.gluster.org/16957 CentOS-regression: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> Smoke: Gluster Build System <jenkins.org>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.10.1, please open a new bug report. glusterfs-3.10.1 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://lists.gluster.org/pipermail/gluster-users/2017-April/030494.html [2] https://www.gluster.org/pipermail/gluster-users/