Description of problem: Tracker for the next release of 3.10 (i.e 3.10.3)
REVIEW: https://review.gluster.org/17432 (doc: release notes for 3.10.3) posted (#1) for review on release-3.10 by Raghavendra Talur (rtalur)
COMMIT: https://review.gluster.org/17432 committed in release-3.10 by Raghavendra Talur (rtalur) ------ commit 4e1818914547cd43e3e35180957417041b5e809b Author: Raghavendra Talur <rtalur> Date: Thu Jun 1 04:17:04 2017 +0530 doc: release notes for 3.10.3 Change-Id: Ic150825cec9b1f75e4d77f0d8e71d10d8578436a BUG: 1457513 Signed-off-by: Raghavendra Talur <rtalur> Reviewed-on: https://review.gluster.org/17432 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.3, please open a new bug report. glusterfs-3.10.3 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-June/031399.html [2] https://www.gluster.org/pipermail/gluster-users/