Re: 0.10.0 release

I think the problem with templates in examples is that they are already modified and it will be hard to merge any upstream template changes back to these examples. We need a method to consistently test and support official templates. We can probably use separate repositories, but I am not sure if w

Re: 0.10.0 release

Possible but we have template in examples/ for testing and that’s ok imo. If we think separate repos is the way to go why not ask? @mentors how hard would it be to get say 5 new repos tied to github mirrors? On Aug 15, 2016, at 1:47 PM, Chan Lee wrote: Regarding 1), I agree with Pat's points

Spark update

Hi, The recent version of Spark - 2.0.0 comes with many changes and improvements. The same is for the related Spark MLlib . -> Spark 2.0.0 release notes -> Spark 2.0.0 overview

Re: 0.10.0 release

Regarding 1), I agree with Pat's points for the need to maintain a separate repository and release cycle for templates. But for the purpose of making the donation process simple and ensuring consistency of templates with each new release of PIO, I think having the code reside inside PIO repo would

[jira] [Created] (PIO-23) links in release.md need to be removed or updated

Pat Ferrel created PIO-23: - Summary: links in release.md need to be removed or updated Key: PIO-23 URL: https://issues.apache.org/jira/browse/PIO-23 Project: PredictionIO Issue Type: Task Affects

[jira] [Created] (PIO-22) Install.sh issues

Pat Ferrel created PIO-22: - Summary: Install.sh issues Key: PIO-22 URL: https://issues.apache.org/jira/browse/PIO-22 Project: PredictionIO Issue Type: Task Affects Versions: 0.10.0 Re