Kotresh, Could you please provide the details? On Thu, Mar 31, 2016 at 6:43 PM, Aravinda <avishwan@xxxxxxxxxx> wrote: > Hi Kaushal, > > We have a Changelog bug which can lead to data loss if Glusterfind is > enabled(To be specific, when changelog.capture-del-path and > changelog.changelog options enabled on a replica volume). > > http://review.gluster.org/#/c/13861/ > > This is very corner case. but good to go with the release. We tried to merge > this before the merge window for 3.7.10, but regressions not yet complete :( > > Do you think we should wait for this patch? > > @Kotresh can provide more details about this issue. > > regards > Aravinda > > > On 03/31/2016 01:29 PM, Kaushal M wrote: >> >> The last change for 3.7.10 has been merged now. Commit 2cd5b75 will be >> used for the release. I'll be preparing release-notes, and tagging the >> release soon. >> >> After running verification tests and checking for any perf >> improvements, I'll make be making the release tarball. >> >> Regards, >> Kaushal >> >> On Wed, Mar 30, 2016 at 7:00 PM, Kaushal M <kshlmster@xxxxxxxxx> wrote: >>> >>> Hi all, >>> >>> I'll be taking over the release duties for 3.7.10. Vijay is busy and >>> could not get the time to do a scheduled release. >>> >>> The .10 release has been scheduled for tagging on 30th (ie. today). >>> In the interests of providing some heads up to developers wishing to >>> get changes merged, >>> I'll be waiting till 10PM PDT, 30th March. (0500UTC/1030IST 31st >>> March), to tag the release. >>> >>> So you have ~15 hours to get any changes required merged. >>> >>> Thanks, >>> Kaushal >> >> _______________________________________________ >> maintainers mailing list >> maintainers@xxxxxxxxxxx >> http://www.gluster.org/mailman/listinfo/maintainers > > _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
