Sounds good. Will try to fill in as much as possible before Tuesday evening.
On Fri, Jul 1, 2016 at 3:13 PM, Andrew Purtell wrote:
> Because of the long weekend we won't have much time to work on this.
> Hopefully we can have a draft ready by Tuesday evening.
>
> On Thu, Jun 30, 2016 at 2:56 PM,
Because of the long weekend we won't have much time to work on this.
Hopefully we can have a draft ready by Tuesday evening.
On Thu, Jun 30, 2016 at 2:56 PM, Andrew Purtell wrote:
> It's time to produce the first report for the Apache PredictionIO
> (incubating) podling!
>
> The report must be p
Hey Andrew,
Account name is 'mvivero'
Thanks,
Marco
On Fri, Jul 1, 2016 at 3:09 PM, Tom Chan wrote:
> 'tchan'
>
> Thanks,
> Tom
>
> On Fri, Jul 1, 2016 at 2:48 PM, Justin Yip wrote:
>
>> Hello Andrew,
>>
>> My jira account is yipjustin.
>>
>> Thanks.
>>
>> Justin
>>
>> On Fri, Jul 1, 2016 at
'tchan'
Thanks,
Tom
On Fri, Jul 1, 2016 at 2:48 PM, Justin Yip wrote:
> Hello Andrew,
>
> My jira account is yipjustin.
>
> Thanks.
>
> Justin
>
> On Fri, Jul 1, 2016 at 2:34 PM, Andrew Purtell
> wrote:
>
> > Added!
> >
> >
> > On Fri, Jul 1, 2016 at 2:28 PM, Kenneth Chan wrote:
> >
> >> Hey
Hello Andrew,
My jira account is yipjustin.
Thanks.
Justin
On Fri, Jul 1, 2016 at 2:34 PM, Andrew Purtell wrote:
> Added!
>
>
> On Fri, Jul 1, 2016 at 2:28 PM, Kenneth Chan wrote:
>
>> Hey Andrew, sorry for late reply
>> my ASF JIRA account is
>>
>> k4hoo
>>
>> Thank!
>> Kenenth
>>
>> On Fri
Added!
On Fri, Jul 1, 2016 at 2:28 PM, Kenneth Chan wrote:
> Hey Andrew, sorry for late reply
> my ASF JIRA account is
>
> k4hoo
>
> Thank!
> Kenenth
>
> On Fri, Jul 1, 2016 at 2:20 PM, Andrew Purtell
> wrote:
>
> > Thank you everyone who responded. You have been added to the appropriate
> > r
Definitely moving to JIRA. We just want to explain to the community why
they are closed, since some of them asked.
On Friday, July 1, 2016, Andrew Purtell wrote:
> What about moving all of those PRs, and their changes (as patch) to the new
> PIO JIRA instance?
>
> There is some discussion about
Matthew Tovbin created PIO-5:
Summary: Replace all *.prediction.io urls
Key: PIO-5
URL: https://issues.apache.org/jira/browse/PIO-5
Project: PredictionIO
Issue Type: Task
Reporter: Ma
Hey Andrew, sorry for late reply
my ASF JIRA account is
k4hoo
Thank!
Kenenth
On Fri, Jul 1, 2016 at 2:20 PM, Andrew Purtell wrote:
> Thank you everyone who responded. You have been added to the appropriate
> role.
>
> On Thu, Jun 30, 2016 at 4:42 PM, Andrew Purtell
> wrote:
>
>> The PIO JIRA
Matthew Tovbin created PIO-4:
Summary: Update Travis build URL
Key: PIO-4
URL: https://issues.apache.org/jira/browse/PIO-4
Project: PredictionIO
Issue Type: Task
Reporter: Matthew Tov
What about moving all of those PRs, and their changes (as patch) to the new
PIO JIRA instance?
There is some discussion about allowing GH Issues as a blessed resource for
development workflow, but we are not there yet where there is guidance for
podlings (or even TLPs).
On Thu, Jun 30, 2016 at 4:
Matthew Tovbin created PIO-3:
Summary: Update all the file headers with ASF License
Key: PIO-3
URL: https://issues.apache.org/jira/browse/PIO-3
Project: PredictionIO
Issue Type: Task
Thank you everyone who responded. You have been added to the appropriate
role.
On Thu, Jun 30, 2016 at 4:42 PM, Andrew Purtell wrote:
> The PIO JIRA instance is ready.
>
> Please sign up for an Apache JIRA account at
> https://issues.apache.org/jira if you do not already have one.
>
> Send me yo
Matthew Tovbin created PIO-2:
Summary: Rename the packages
Key: PIO-2
URL: https://issues.apache.org/jira/browse/PIO-2
Project: PredictionIO
Issue Type: Task
Reporter: Matthew Tovbin
Good point on Elasticsearch support. I believe this is exactly why Spark
uses a multi-profile Maven build on a single release branch to support
different Hadoop versions. We can explore the possibility of using multiple
SBT configurations for a similar effect.
On Fri, Jul 1, 2016 at 10:55 AM, Matt
Donald / Pat,
Agreed. And having a multiple release branches is a non-issue.
-Matthew
On Fri, Jul 1, 2016 at 10:26 AM, Pat Ferrel wrote:
> +1 (in general)
>
> The only issue will be when we have more than one release to support. For
> instance Elasticsearch 2.x forces an upgrade on all users
+1 (in general)
The only issue will be when we have more than one release to support. For
instance Elasticsearch 2.x forces an upgrade on all users and so may not be a
good idea to add to our songle release branch, which is the master. This or
other cases will eventually require us to have more
Hi all,
Really excited that PredictionIO is now part of Apache. To commence
development, I suggest that we continue PredictionIO's previous development
model that was based on
http://nvie.com/posts/a-successful-git-branching-model/.
If you have any concerns, doubts, or objections please voice.
T
If it's the first time build, it's possible that SBT is downloading a lot
of dependencies. Remember we used to ask people to put the --verbose flag
to make sure? I recall advising the user to add this flag in another
thread. Still waiting to hear back.
On Fri, Jul 1, 2016 at 10:07 AM, Pat Ferrel
Any idea why he is having a build failure then? Some user error?
On Jul 1, 2016, at 10:05 AM, Donald Szeto wrote:
The upgrade checker is implemented to run in a separate thread and should not
fail the main process, be it building, training, or deploying. I suggest this
be temporarily disabled
The upgrade checker is implemented to run in a separate thread and should
not fail the main process, be it building, training, or deploying. I
suggest this be temporarily disabled until our Apache migration is complete
and stable.
On Fri, Jul 1, 2016 at 10:01 AM, Pat Ferrel wrote:
> Shouldn’t al
Shouldn’t all exceptions (well the vast majority) be caught in that code so no
error would cause a failure of a build?
On Jul 1, 2016, at 9:55 AM, Pat Ferrel wrote:
io.prediction.workflow.UpgradeCheckRunner.run(WorkflowUtils.scala:400)
Seems to be looking for "http://direct.prediction.i
io.prediction.workflow.UpgradeCheckRunner.run(WorkflowUtils.scala:400)
Seems to be looking for "http://direct.prediction.io/";
Two types of exceptions are caught, not sure what happens with any others. Does
this mean that if the site is wonky builds may fail? If so is anyone working on
th
+1
JIRA username: emergentorder
On Thu, Jun 30, 2016 at 5:42 PM, Andrew Purtell wrote:
> The PIO JIRA instance is ready.
>
> Please sign up for an Apache JIRA account at
> https://issues.apache.org/jira if you do not already have one.
>
> Send me your JIRA account info. I will need this information
My username is jamborta
Thanks
On Fri, 1 Jul 2016, 06:12 Chalenge Masekera,
wrote:
> My Jira username is "chalenge"
>
> thanks
>
> On Thu, Jun 30, 2016 at 4:42 PM, Andrew Purtell
> wrote:
>
>> The PIO JIRA instance is ready.
>>
>> Please sign up for an Apache JIRA account at
>> https://issues.
26 matches
Mail list logo
