<div><br><div class="gmail_quote"><div>On Wed, 1 Feb 2017 at 17:06, Kaushal M <<a href="mailto:kshlmster@gmail.com">kshlmster@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br class="gmail_msg">
<br class="gmail_msg">
GlusterFS-3.7.20 is intended to be the final release for release-3.7.<br class="gmail_msg">
3.7 enters EOL with the expected release of 3.10 in about 2 weeks.</blockquote><div><br></div><div>Am I missing any key points here? With 3.10 coming in, 3.9 goes EOL considering it is short term and then don't we need to maintain 3 releases at a point? In that case 3.7 still needs to be active with 3.8 & 3.10, no?</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br class="gmail_msg">
<br class="gmail_msg">
Once 3.10 is released I'll be closing any open bugs on 3.7 and<br class="gmail_msg">
abandoning any patches on review.<br class="gmail_msg">
<br class="gmail_msg">
So as the subject says, developers please stop sending changes to<br class="gmail_msg">
release-3.7, and maintainers please don't merge any more changes onto<br class="gmail_msg">
release-3.7.<br class="gmail_msg">
<br class="gmail_msg">
~kaushal<br class="gmail_msg">
_______________________________________________<br class="gmail_msg">
maintainers mailing list<br class="gmail_msg">
<a href="mailto:maintainers@gluster.org" class="gmail_msg" target="_blank">maintainers@gluster.org</a><br class="gmail_msg">
<a href="http://lists.gluster.org/mailman/listinfo/maintainers" rel="noreferrer" class="gmail_msg" target="_blank">http://lists.gluster.org/mailman/listinfo/maintainers</a><br class="gmail_msg">
</blockquote></div></div><div dir="ltr">-- <br></div><div data-smartmail="gmail_signature">- Atin (atinm)</div>