Had forgot to add milind, ccing. On Mon, Oct 8, 2018 at 11:41 AM Kotresh Hiremath Ravishankar < [email protected]> wrote:
> > > On Fri, Oct 5, 2018 at 10:31 PM Shyam Ranganathan <[email protected]> > wrote: > >> On 10/05/2018 10:59 AM, Shyam Ranganathan wrote: >> > On 10/04/2018 11:33 AM, Shyam Ranganathan wrote: >> >> On 09/13/2018 11:10 AM, Shyam Ranganathan wrote: >> >>> RC1 would be around 24th of Sep. with final release tagging around 1st >> >>> of Oct. >> >> RC1 now stands to be tagged tomorrow, and patches that are being >> >> targeted for a back port include, >> > We still are awaiting release notes (other than the bugs section) to be >> > closed. >> > >> > There is one new bug that needs attention from the replicate team. >> > https://bugzilla.redhat.com/show_bug.cgi?id=1636502 >> > >> > The above looks important to me to be fixed before the release, @ravi or >> > @pranith can you take a look? >> > >> >> RC1 is tagged and release tarball generated. >> >> We still have 2 issues to work on, >> >> 1. The above messages from AFR in self heal logs >> >> 2. We need to test with Py3, else we risk putting out packages there on >> Py3 default distros and causing some mayhem if basic things fail. >> >> I am open to suggestions on how to ensure we work with Py3, thoughts? >> >> I am thinking we run a regression on F28 (or a platform that defaults to >> Py3) and ensure regressions are passing at the very least. For other >> Python code that regressions do not cover, >> - We have a list at [1] >> - How can we split ownership of these? >> > > +1 for the regression run on py3 default platform. We don't need to run > full regressions. > We can chose to run only those test cases related to python. Categorically > we have > 1. geo-rep > 2. events framework > 3. glusterfind > 4. tools/scripts > > I can take care of geo-rep. With following two patches, geo-rep works both > on py2 and py3. > I have tested these locally on centos-7.5 (py2 is default) and fedora28 > (making py3 default by > symlink /usr/bin/python -> python3). Again the test was very basic, we can > fix going forward, > if there are any corner cases. > > 1. https://review.gluster.org/#/c/glusterfs/+/21356/ (Though this is > events patch, geo-rep internally uses it, so is required for geo-rep.) > 2. https://review.gluster.org/#/c/glusterfs/+/21357/ > > It think we need to add regression tests for events and glusterfind. > Adding milind to comment on glusterfind. > >> >> @Aravinda, @Kotresh, and @ppai, looking to you folks to help out with >> the process and needs here. >> >> Shyam >> >> [1] https://github.com/gluster/glusterfs/issues/411 >> > > > -- > Thanks and Regards, > Kotresh H R > -- Thanks and Regards, Kotresh H R
_______________________________________________ Gluster-devel mailing list [email protected] https://lists.gluster.org/mailman/listinfo/gluster-devel
