<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jun 5, 2017 at 3:30 PM, Jiffin Tony Thottan <span dir="ltr"><<a href="mailto:jthottan@redhat.com" target="_blank">jthottan@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 01/06/17 22:47, Shyam wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br>
Here are some top reminders for the 3.12 release:<br>
<br>
1) When 3.12 is released 3.8 will be EOL'd, hence users are encouraged to prepare for the same as per the calendar posted here.<br>
<br>
2) 3.12 is a long term maintenance (LTM) release, and potentially the last in the 3.x line of Gluster!<br>
<br>
3) From this release onward, the feature freeze date is moved ~45 days in advance, before the release. Hence, for this one release you will have lesser time to get your features into the release.<br>
<br>
Release calendar:<br>
<br>
- Feature freeze, or branching date: July 17th, 2017<br>
- All feature post this date need exceptions granted to make it into the 3.12 release<br>
<br>
- Release date: August 30th, 2017<br>
<br>
Release owners:<br>
<br>
- Shyam<br>
- <TBD> Any volunteers?<br>
<br>
</blockquote>
<br></span>
I am interested<br>
--<br>
Jiffin<br>
<br></blockquote><div><br></div><div> I am also interested<br></div><div> Ankit <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
Features and major changes process in a nutshell:<br>
1) Open a github issue<br>
<br>
2) Refer the issue # in the commit messages of all changes against the feature (specs, code, tests, docs, release notes) (refer to the issue as "updates gluster/glusterfs#N" where N is the issue)<br>
<br>
3) We will ease out release-notes updates form this release onward. Still thinking how to get that done, but the intention is that a contributor can update release notes before/on/after completion of the feature and not worry about branching dates etc. IOW, you can control when you are done, than the release dates controlling the same for you.<br>
<br>
Thanks,<br>
Shyam<br>
______________________________<wbr>_________________<br></span>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">http://lists.gluster.org/mailm<wbr>an/listinfo/gluster-users</a><br>
</blockquote><div class="HOEnZb"><div class="h5">
<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>
</div></div></blockquote></div><br></div></div>