<div dir="ltr">I would like to turn features.sdfs on by default starting from 4.1. Details can be found in issue:<br><a href="https://github.com/gluster/glusterfs/issues/421">https://github.com/gluster/glusterfs/issues/421</a><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Mar 16, 2018 at 1:00 PM, Xavi Hernandez <span dir="ltr"><<a href="mailto:jahernan@redhat.com" target="_blank">jahernan@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span class="">On Tue, Mar 13, 2018 at 2:37 AM, Shyam Ranganathan <span dir="ltr"><<a href="mailto:srangana@redhat.com" target="_blank">srangana@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);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><div><br></div></span><div>I would like to propose the transaction framework [1] as an experimental feature for 4.1. The design [2] is done and I'm currently developing it.</div><div><br></div><div>Xavi</div><div><br></div><div>[1] <a href="https://github.com/gluster/glusterfs/issues/342" target="_blank">https://github.com/<wbr>gluster/glusterfs/issues/342</a></div><div>[2] <a href="https://docs.google.com/document/d/1Zp99bsfLsB51tPen_zC8enANvOhX3o451pd5LyEdRSM/edit?usp=sharing" target="_blank">https://docs.google.com/<wbr>document/d/1Zp99bsfLsB51tPen_<wbr>zC8enANvOhX3o451pd5LyEdRSM/<wbr>edit?usp=sharing</a></div><span class=""><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);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>
maintainers mailing list<br>
<a href="mailto:maintainers@gluster.org" target="_blank">maintainers@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/maintainers" rel="noreferrer" target="_blank">http://lists.gluster.org/mailm<wbr>an/listinfo/maintainers</a><br>
</blockquote></span></div><br></div></div>
<br>______________________________<wbr>_________________<br>
maintainers mailing list<br>
<a href="mailto:maintainers@gluster.org">maintainers@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/maintainers" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/maintainers</a><br>
<br></blockquote></div><br></div>