[Fuego] Regarding next release of Fuego

[Bird, Timothy]

> -----Original Message-----
> From: dhinakar k [mailto:dhinakar.k at gmail.com]
> Sent: Thursday, July 20, 2017 6:07 AM
> 
> Just curious, have you collaborated or worked for Samsung anytime before?

No.  Not in any commercial sense, in my current job.  Lineo (a company I worked
for many years ago) did some work for Samsung, but that was a long time ago.
I have worked with Samsung engineers in Open Source projects.  My most recent
work was with Shuah Khan on some kernel selftest issues.
 -- Tim


> On Jul 18, 2017 8:42 PM, "dhinakar k" <dhinakar.k at gmail.com
> <mailto:dhinakar.k at gmail.com> > wrote:
> 
> 
> 	Thanks Tim for the response.
> 	I really appreciate the work on unified output format. It is something
> which I am looking forward to. In the 'next' branch, some tests are failing for
> me. I know that for a couple of them fixes are available. I need to analyze the
> others, could be arm64 toolchain configuration issues. Iam also closely
> following your recent thread on renesas on this. I thought I will wait for the
> official release before getting into other failures as I have other
> commitments. May be if you can give me the list of fixes/patches available it
> will help. The rest I will troubleshoot.
> 
> 	Regards,
> 	Dhinakar
> 
> 
> 	On Jul 18, 2017 8:03 PM, "Bird, Timothy" <Tim.Bird at sony.com
> <mailto:Tim.Bird at sony.com> > wrote:
> 
> 
> 
> 
> 		> -----Original Message-----
> 		> From: dhinakar k on Monday, July 17, 2017 9:07 AM
> 		>
> 		> May I know when you are planning the release of Fuego
> v1.2?
> 
> 
> 		We just had a conference call on the status of the unified
> output format
> 		recently.  We are still discussing some issues with how to
> store, process,
> 		and share some of the data (such as the 'pass-criteria').  Once
> we have
> 		finalized that, we will need to do conversions on the
> parser.py modules
> 		for all of the existing tests (and add them to the Functional
> tests).
> 
> 		At the moment, I don't have a good idea how long this will
> take.  I had hoped
> 		to have a release candidate about this time (mid-July), but
> my educated guess is
> 		that we're at least another month away from the 1.2 release
> candidate.
> 
> 		Are there bugs in 1.1 that have been fixed in 1.2 that you are
> waiting for?
> 		Maybe we could backport some bugfixes if that's blocking
> your work.
> 		 -- Tim
> 
> 
>