<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jan 30, 2017 at 7:30 PM, Xavier Hernandez <span dir="ltr"><<a href="mailto:xhernandez@datalab.es" target="_blank">xhernandez@datalab.es</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
I'm wondering how a new option needs to be created to be available to different versions of gluster.<br>
<br>
When a new option is created for 3.7 for example, it needs to have a GD_OP_VERSION referencing the next 3.7 release. This ensures that there won't be any problem with previous versions.<br>
<br>
However what happens with 3.8 ?<br>
<br>
3.8.0 is greater than any 3.7.x, however the new option won't be available until the next 3.8 release. How this needs to be handled ?<br></blockquote><div><br></div><div>I'd discourage to backport any new volume options from mainline to the stable releases branches like 3.7 & 3.8. This creates a lot of backward compatibility issues w.r.t clients. Any new option is actually an RFE and supposed to be slated for only upcoming releases.<br></div><div> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Thanks,<br>
<br>
Xavi<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></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><br></div><div>~ Atin (atinm)<br></div></div></div></div>
</div></div>