Bug 1693300 (glusterfs-5.6) - GlusterFS 5.6 tracker
Summary: GlusterFS 5.6 tracker
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: glusterfs-5.6
Deadline: 2019-05-10
Product: GlusterFS
Classification: Community
Component: core
Version: 5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On: 1687051 1692959
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-27 13:36 UTC by Shyamsundar
Modified: 2019-04-18 11:12 UTC (History)
2 users (show)

Fixed In Version: 5.6
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-04-09 11:53:52 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gluster.org Gerrit 22538 0 None Merged doc: Added release 5.6 notes 2019-04-09 11:53:51 UTC

Description Shyamsundar 2019-03-27 13:36:33 UTC
Tracker for the release 5.6

Comment 1 Worker Ant 2019-04-09 11:32:42 UTC
REVIEW: https://review.gluster.org/22538 (doc: Added release 5.6 notes) posted (#1) for review on release-5 by Shyamsundar Ranganathan

Comment 2 Worker Ant 2019-04-09 11:53:52 UTC
REVIEW: https://review.gluster.org/22538 (doc: Added release 5.6 notes) merged (#1) on release-5 by Shyamsundar Ranganathan

Comment 3 Shyamsundar 2019-04-18 11:12:12 UTC
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-5.6, please open a new bug report.

glusterfs-5.6 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] https://lists.gluster.org/pipermail/announce/2019-April/000123.html
[2] https://www.gluster.org/pipermail/gluster-users/


Note You need to log in before you can comment on or make changes to this bug.