<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Apr 13, 2015 at 10:43 PM, Vijay Bellur <span dir="ltr"><<a href="mailto:vbellur@redhat.com" target="_blank">vbellur@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Here is a quick status update on 3.7.0 branching.<span class=""><br>
<br>
On 04/07/2015 03:51 PM, Vijay Bellur wrote:<br>
</span><span class=""><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Hi All,<br>
<br>
I am planning to branch release-3.7 by the end of this week. Here is a<br>
list of tasks that we would need to accomplish by then:<br>
<br>
</blockquote>
<br></span>
We have not yet branched release-3.7. I intend doing that tomorrow after we hear back from maintainers.<span class=""><br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
1. Review and merge as many fixes for coverity found issues. [1]<br>
</blockquote>
<br></span>
We made good progress here. Still a few more to be covered but can be taken up post branching.<span class=""><br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
2. Review and merge as many logging improvement patches. [2]<br>
</blockquote>
<br></span>
Lot of ground to cover here. The patches are quite large for reviewing, intend to not hold branching due to this.<span class=""><br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
3. Spurious regression tests listed in [3] to be fixed.<br>
To not impede the review & merge workflow on release-3.7/master, I<br>
plan to drop those test units which still cause<br>
spurious failures by the time we branch release-3.7.<br>
</blockquote>
<br></span>
As discussed previously on this thread, pushing this out as a release blocker.<span class=""><br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
4. Maintainers to ACK sanity of their respective components.<br>
</blockquote>
<br></span>
Haven't heard any feedback here. Maintainers - can you please chime in with ACK/NACK here for your components?</blockquote><div><br></div><div style>Quota</div><div style>=====</div><div style><br></div><div style>There is an issue where removing any of the size-limit, dir-limit, file-limit would remove other limits too. Sachin/Vijay mallikarjuna will be working on this. Patch can be taken post branching but before release.</div><div style><br></div><div style>DHT</div><div style>====</div><div style>Patches review pending:</div><div style><br></div><div style><a href="http://review.gluster.org/9657">http://review.gluster.org/9657</a><br></div><div style><a href="http://review.gluster.org/10146">http://review.gluster.org/10146</a><br></div><div style><a href="http://review.gluster.org/#/c/8912/">http://review.gluster.org/#/c/8912/</a><br></div><div style><a href="http://review.gluster.org/10212">http://review.gluster.org/10212</a><br></div><div style><a href="http://review.gluster.org/#/c/7702/">http://review.gluster.org/#/c/7702/</a><br></div><div style><br></div><div style>I doubt any of these will be merged by tomorrow. So, can review and merging be targeted post branching but before release?</div><div style><br></div><div style>rpc/protocol: No patches in my incoming review requests. So, I assume its good to go.</div><div style><br></div><div style><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span class="im"><br>
<br>
Thanks,<br>
Vijay<br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
[1]<br>
<a href="http://review.gluster.org/#/q/status:open+project:glusterfs+branch:master+topic:bug-789278,n,z" target="_blank">http://review.gluster.org/#/q/<u></u>status:open+project:glusterfs+<u></u>branch:master+topic:bug-<u></u>789278,n,z</a><br>
<br>
<br>
[2]<br>
<a href="http://review.gluster.org/#/q/status:open+project:glusterfs+branch:master+topic:bug-1194640,n,z" target="_blank">http://review.gluster.org/#/q/<u></u>status:open+project:glusterfs+<u></u>branch:master+topic:bug-<u></u>1194640,n,z</a><br>
<br>
<br>
[3] <a href="https://public.pad.fsfe.org/p/gluster-spurious-failures" target="_blank">https://public.pad.fsfe.org/p/<u></u>gluster-spurious-failures</a><br>
<br>
</blockquote>
<br></span><div class=""><div class="h5">
______________________________<u></u>_________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@gluster.org" target="_blank">Gluster-devel@gluster.org</a><br>
<a href="http://www.gluster.org/mailman/listinfo/gluster-devel" target="_blank">http://www.gluster.org/<u></u>mailman/listinfo/gluster-devel</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">Raghavendra G<br></div>
</div></div>