Thanks for clarifying that point. Does this mean that the fix for this bug will get backported to the next 3.12 release? ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On April 9, 2018 2:31 PM, Ravishankar N <ravishankar@xxxxxxxxxx> wrote: > > > On 04/09/2018 05:54 PM, Dmitry Melekhov wrote: > > > 09.04.2018 16:18, Ravishankar N пишет: > > > > > On 04/09/2018 05:40 PM, mabi wrote: > > > > > > > Again thanks that worked and I have now no more unsynched files. > > > > > > > > You mentioned that this bug has been fixed in 3.13, would it be > > > > > > > > possible to backport it to 3.12? I am asking because 3.13 is not a > > > > > > > > long-term release and as such I would not like to have to upgrade to > > > > > > > > 3.13. > > > > > > I don't think there will be another 3.12 release. > > > > Why not? It is LTS, right? > > My bad. Just checked the schedule [1], and you are right. It is LTM. > > [1] https://www.gluster.org/release-schedule/ > > > Gluster-users mailing list > > > > Gluster-users@xxxxxxxxxxx > > > > http://lists.gluster.org/mailman/listinfo/gluster-users > > Gluster-users mailing list > > Gluster-users@xxxxxxxxxxx > > http://lists.gluster.org/mailman/listinfo/gluster-users _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-users
