<div dir="ltr"><div dir="ltr"><div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Fri, Oct 5, 2018 at 10:31 PM Shyam Ranganathan <<a href="mailto:srangana@redhat.com">srangana@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 10/05/2018 10:59 AM, Shyam Ranganathan wrote:<br>
> 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>
>> RC1 now stands to be tagged tomorrow, and patches that are being<br>
>> targeted for a back port include,<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>
RC1 is tagged and release tarball generated.<br>
<br>
We still have 2 issues to work on,<br>
<br>
1. The above messages from AFR in self heal logs<br>
<br>
2. We need to test with Py3, else we risk putting out packages there on<br>
Py3 default distros and causing some mayhem if basic things fail.<br>
<br>
I am open to suggestions on how to ensure we work with Py3, thoughts?<br>
<br>
I am thinking we run a regression on F28 (or a platform that defaults to<br>
Py3) and ensure regressions are passing at the very least. For other<br>
Python code that regressions do not cover,<br>
- We have a list at [1]<br>
- How can we split ownership of these?<br></blockquote><div><br></div><div>+1 for the regression run on py3 default platform. We don't need to run full regressions.<br></div><div>We can chose to run only those test cases related to python. Categorically we have</div><div>1. geo-rep</div><div>2. events framework</div><div>3. glusterfind</div><div>4. tools/scripts</div><div><br></div><div>I can take care of geo-rep. With following two patches, geo-rep works both on py2 and py3. <br></div><div>I have tested these locally on centos-7.5 (py2 is default) and fedora28 (making py3 default by</div><div>symlink /usr/bin/python -> python3). Again the test was very basic, we can fix going forward,</div><div>if there are any corner cases.<br></div><div><br></div><div>1. <a href="https://review.gluster.org/#/c/glusterfs/+/21356/">https://review.gluster.org/#/c/glusterfs/+/21356/</a> (Though this is events patch, geo-rep internally uses it, so is required for geo-rep.)<br></div><div>2. <a href="https://review.gluster.org/#/c/glusterfs/+/21357/">https://review.gluster.org/#/c/glusterfs/+/21357/</a></div><div><br></div>It think we need to add regression tests for events and glusterfind.<div>Adding milind to comment on glusterfind.<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
@Aravinda, @Kotresh, and @ppai, looking to you folks to help out with<br>
the process and needs here.<br>
<br>
Shyam<br>
<br>
[1] <a href="https://github.com/gluster/glusterfs/issues/411" rel="noreferrer" target="_blank">https://github.com/gluster/glusterfs/issues/411</a><br>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div>Thanks and Regards,<br></div>Kotresh H R<br></div></div></div></div></div>