<div><br></div><div><br><div class="gmail_quote"><div dir="ltr">On Fri, 5 Oct 2018 at 20:29, Shyam Ranganathan <<a href="mailto:srangana@redhat.com">srangana@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 10/04/2018 11:33 AM, Shyam Ranganathan wrote:<br>
> On 09/13/2018 11:10 AM, Shyam Ranganathan wrote:<br>
>> RC1 would be around 24th of Sep. with final release tagging around 1st<br>
>> of Oct.<br>
> <br>
> RC1 now stands to be tagged tomorrow, and patches that are being<br>
> targeted for a back port include,<br>
<br>
We still are awaiting release notes (other than the bugs section) to be<br>
closed.<br>
<br>
There is one new bug that needs attention from the replicate team.<br>
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1636502" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1636502</a><br>
<br>
The above looks important to me to be fixed before the release, @ravi or<br>
@pranith can you take a look?<br>
<br>
> <br>
> 1) <a href="https://review.gluster.org/c/glusterfs/+/21314" rel="noreferrer" target="_blank">https://review.gluster.org/c/glusterfs/+/21314</a> (snapshot volfile in<br>
> mux cases)<br>
> <br>
> @RaBhat working on this.<br>
<br>
Done<br>
<br>
> <br>
> 2) Py3 corrections in master<br>
> <br>
> @Kotresh are all changes made to master backported to release-5 (may not<br>
> be merged, but looking at if they are backported and ready for merge)?<br>
<br>
Done, release notes amend pending<br>
<br>
> <br>
> 3) Release notes review and updates with GD2 content pending<br>
> <br>
> @Kaushal/GD2 team can we get the updates as required?<br>
> <a href="https://review.gluster.org/c/glusterfs/+/21303" rel="noreferrer" target="_blank">https://review.gluster.org/c/glusterfs/+/21303</a><br>
<br>
Still awaiting this.</blockquote><div dir="auto"><br></div><div dir="auto">Kaushal has added a comment into the patch providing the content today morning IST. Any additional details are you looking for?</div><div dir="auto"><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
> <br>
> 4) This bug [2] was filed when we released 4.0.<br>
> <br>
> The issue has not bitten us in 4.0 or in 4.1 (yet!) (i.e the options<br>
> missing and hence post-upgrade clients failing the mount). This is<br>
> possibly the last chance to fix it.<br>
> <br>
> Glusterd and protocol maintainers, can you chime in, if this bug needs<br>
> to be and can be fixed? (thanks to @anoopcs for pointing it out to me)<br>
<br>
Release notes to be corrected to call this out.<br>
<br>
> <br>
> The tracker bug [1] does not have any other blockers against it, hence<br>
> assuming we are not tracking/waiting on anything other than the set above.<br>
> <br>
> Thanks,<br>
> Shyam<br>
> <br>
> [1] Tracker: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-5.0" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-5.0</a><br>
> [2] Potential upgrade bug:<br>
> <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1540659" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1540659</a><br>
> _______________________________________________<br>
> maintainers mailing list<br>
> <a href="mailto:maintainers@gluster.org" target="_blank">maintainers@gluster.org</a><br>
> <a href="https://lists.gluster.org/mailman/listinfo/maintainers" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/maintainers</a><br>
> <br>
_______________________________________________<br>
maintainers mailing list<br>
<a href="mailto:maintainers@gluster.org" target="_blank">maintainers@gluster.org</a><br>
<a href="https://lists.gluster.org/mailman/listinfo/maintainers" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/maintainers</a><br>
</blockquote></div></div>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature">- Atin (atinm)</div>