Is now tagged and being packaged. If anyone gets a chance, please test the packages from CentOS SIG, as I am unavailable for the next 4 days. Thanks, Shyam On 4/16/19 9:53 AM, Shyam Ranganathan wrote: > Status: Tagging pending > > Waiting on patches: > (Kotresh/Atin) - glusterd: fix loading ctime in client graph logic > https://review.gluster.org/c/glusterfs/+/22579 > > Following patches will not be taken in if CentOS regression does not > pass by tomorrow morning Eastern TZ, > (Pranith/KingLongMee) - cluster-syncop: avoid duplicate unlock of > inodelk/entrylk > https://review.gluster.org/c/glusterfs/+/22385 > (Aravinda) - geo-rep: IPv6 support > https://review.gluster.org/c/glusterfs/+/22488 > (Aravinda) - geo-rep: fix integer config validation > https://review.gluster.org/c/glusterfs/+/22489 > > Tracker bug status: > (Ravi) - Bug 1693155 - Excessive AFR messages from gluster showing in > RHGSWA. > All patches are merged, but none of the patches adds the "Fixes" > keyword, assume this is an oversight and that the bug is fixed in this > release. > > (Atin) - Bug 1698131 - multiple glusterfsd processes being launched for > the same brick, causing transport endpoint not connected > No work has occurred post logs upload to bug, restart of bircks and > possibly glusterd is the existing workaround when the bug is hit. Moving > this out of the tracker for 6.1. > > (Xavi) - Bug 1699917 - I/O error on writes to a disperse volume when > replace-brick is executed > Very recent bug (15th April), does not seem to have any critical data > corruption or service availability issues, planning on not waiting for > the fix in 6.1 > > - Shyam > On 4/6/19 4:38 AM, Atin Mukherjee wrote: >> Hi Mohit, >> >> https://review.gluster.org/22495 should get into 6.1 as it’s a >> regression. Can you please attach the respective bug to the tracker Ravi >> pointed out? >> >> >> On Sat, 6 Apr 2019 at 12:00, Ravishankar N <ravishankar@xxxxxxxxxx >> <mailto:ravishankar@xxxxxxxxxx>> wrote: >> >> Tracker bug is https://bugzilla.redhat.com/show_bug.cgi?id=1692394, in >> case anyone wants to add blocker bugs. >> >> >> On 05/04/19 8:03 PM, Shyam Ranganathan wrote: >> > Hi, >> > >> > Expected tagging date for release-6.1 is on April, 10th, 2019. >> > >> > Please ensure required patches are backported and also are passing >> > regressions and are appropriately reviewed for easy merging and >> tagging >> > on the date. >> > >> > Thanks, >> > Shyam >> > _______________________________________________ >> > Gluster-devel mailing list >> > Gluster-devel@xxxxxxxxxxx <mailto:Gluster-devel@xxxxxxxxxxx> >> > https://lists.gluster.org/mailman/listinfo/gluster-devel >> _______________________________________________ >> Gluster-devel mailing list >> Gluster-devel@xxxxxxxxxxx <mailto:Gluster-devel@xxxxxxxxxxx> >> https://lists.gluster.org/mailman/listinfo/gluster-devel >> >> >> -- >> - Atin (atinm) >> >> _______________________________________________ >> Gluster-devel mailing list >> Gluster-devel@xxxxxxxxxxx >> https://lists.gluster.org/mailman/listinfo/gluster-devel >> > _______________________________________________ > Gluster-devel mailing list > Gluster-devel@xxxxxxxxxxx > https://lists.gluster.org/mailman/listinfo/gluster-devel > _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-devel
