<div dir="ltr">Hi,<div> Would like to propose Cloudsync Xlator(for Archival use-case) for 4.1. (github issue-id #387).</div><div>Initial patch (under review) is posted here: <a href="https://review.gluster.org/#/c/18532/">https://review.gluster.org/#/c/18532/</a>.</div><div>Spec file: <a href="https://review.gluster.org/#/c/18854/">https://review.gluster.org/#/c/18854/</a></div><div><br></div><div>Thanks,<br>Susant </div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Mar 15, 2018 at 4:05 PM, Ravishankar N <span dir="ltr"><<a href="mailto:ravishankar@redhat.com" target="_blank">ravishankar@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
<br>
On 03/13/2018 07:07 AM, Shyam Ranganathan wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br>
As we wind down on 4.0 activities (waiting on docs to hit the site, and<br>
packages to be available in CentOS repositories before announcing the<br>
release), it is time to start preparing for the 4.1 release.<br>
<br>
4.1 is where we have GD2 fully functional and shipping with migration<br>
tools to aid Glusterd to GlusterD2 migrations.<br>
<br>
Other than the above, this is a call out for features that are in the<br>
works for 4.1. Please *post* the github issues to the *devel lists* that<br>
you would like as a part of 4.1, and also mention the current state of<br>
development.<br>
</blockquote></span>
Hi,<br>
<br>
We are targeting the 'thin-arbiter' feature for 4.1 :<a href="https://github.com/gluster/glusterfs/issues/352" rel="noreferrer" target="_blank">https://github.com/gluster/gl<wbr>usterfs/issues/352</a><br>
Status: High level design is there in the github issue.<br>
Thin arbiter xlator patch <a href="https://review.gluster.org/#/c/19545/" rel="noreferrer" target="_blank">https://review.gluster.org/#/c<wbr>/19545/</a> is undergoing reviews.<br>
Implementation details on AFR and glusterd(2) related changes are being discussed. Will make sure all patches are posted against issue 352.<br>
<br>
Thanks,<br>
Ravi<div class="HOEnZb"><div class="h5"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Further, as we hit end of March, we would make it mandatory for features<br>
to have required spec and doc labels, before the code is merged, so<br>
factor in efforts for the same if not already done.<br>
<br>
Current 4.1 project release lane is empty! I cleaned it up, because I<br>
want to hear from all as to what content to add, than add things marked<br>
with the 4.1 milestone by default.<br>
<br>
Thanks,<br>
Shyam<br>
P.S: Also any volunteers to shadow/participate/run 4.1 as a release owner?<br>
______________________________<wbr>_________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@gluster.org" target="_blank">Gluster-devel@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://lists.gluster.org/mailm<wbr>an/listinfo/gluster-devel</a><br>
</blockquote>
<br>
______________________________<wbr>_________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@gluster.org" target="_blank">Gluster-devel@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://lists.gluster.org/mailm<wbr>an/listinfo/gluster-devel</a></div></div></blockquote></div><br></div>