Hi everyone,
I don't have a problem putting my modified fork in the new gallery. As Pat
already mentioned, they only modify the "calls" on package namespace. If
there are no objections, I'll clean them up and them in the new gallery
with pio_min_version as 0.10. Once the donation grant is done, we
Chan:
Thanks but I think we agreed to hold the release until the template grant
meaning we merge your changes and publish the gallery linking to Apache hosted
templates.
All your work is still important and I’d publish them to your personal github
account in prep for a PR to Apache when the g
[
https://issues.apache.org/jira/browse/PIO-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pat Ferrel updated PIO-27:
--
Assignee: (was: Pat Ferrel)
> Check release artifacts for licenses and the LICENSE.txt file
> --
[
https://issues.apache.org/jira/browse/PIO-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429798#comment-15429798
]
Pat Ferrel commented on PIO-27:
---
Further @dev comments
It took Gearpump six release candidates
[
https://issues.apache.org/jira/browse/PIO-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429799#comment-15429799
]
Pat Ferrel commented on PIO-27:
---
I don't have time to do this and so this is unassigned.
> Chec
Hi Pat,
I must've misunderstood. I thought we were pushing for release before
template grant is approved. This sounds much better. Thanks.
On Sun, Aug 21, 2016 at 9:47 AM, Pat Ferrel wrote:
> Chan:
>
> Thanks but I think we agreed to hold the release until the template grant
> meaning we merge
[
https://issues.apache.org/jira/browse/PIO-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429859#comment-15429859
]
ASF GitHub Bot commented on PIO-26:
---
Github user dszeto commented on the issue:
https:/
[
https://issues.apache.org/jira/browse/PIO-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429860#comment-15429860
]
ASF GitHub Bot commented on PIO-26:
---
Github user asfgit closed the pull request at:
htt
[
https://issues.apache.org/jira/browse/PIO-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Szeto resolved PIO-26.
-
Resolution: Fixed
Fix Version/s: 0.10.0
> Integrate Apache RAT for license checking
> -
Yeah, the thread got long. To summarize, there is nothing wrong with converting
them and hosting them outside Apache, with or without the grant. However it
looks like the grant will come soon and adding them to Apache probably will not
delay a PIO release and everyone agrees (so far) that it’s t
[
https://issues.apache.org/jira/browse/PIO-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429866#comment-15429866
]
Donald Szeto commented on PIO-6:
Before this issue is resolved we can only perform manual pushe
[
https://issues.apache.org/jira/browse/PIO-5?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429867#comment-15429867
]
Donald Szeto commented on PIO-5:
Yes. Let me resolve this.
> Replace all *.prediction.io urls
[
https://issues.apache.org/jira/browse/PIO-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Szeto resolved PIO-6.
Resolution: Fixed
> Create doc site
> ---
>
> Key: PIO-6
> URL: https
[
https://issues.apache.org/jira/browse/PIO-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429866#comment-15429866
]
Donald Szeto edited comment on PIO-6 at 8/21/16 7:35 PM:
-
Before INFRA-
[
https://issues.apache.org/jira/browse/PIO-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Szeto resolved PIO-5.
Resolution: Fixed
> Replace all *.prediction.io urls
>
>
> Key:
I don’t have the time to do this. Jira PIO-27 covers this conversation and is
set to blocking.
Can anyone help?
On Aug 20, 2016, at 12:14 PM, Andrew Purtell wrote:
It took Gearpump six release candidates before their first release from
incubation passed the IPMC's checks on correct LICENSE a
Collectively this podling must accomplish these tasks in order to make a
release. This is what you signed up for with incubation.
> On Aug 21, 2016, at 12:59 PM, Pat Ferrel wrote:
>
> I don’t have the time to do this. Jira PIO-27 covers this conversation and is
> set to blocking.
>
> Can any
Github user dszeto commented on the issue:
https://github.com/apache/incubator-predictionio/pull/279
This is great! Thanks @chanlee514 !
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this f
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-predictionio/pull/279
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
Github user Christophy commented on the issue:
https://github.com/apache/incubator-predictionio/issues/276
Hello, XueSong, As you noticed from the post above , your engine was
deployed in the 'https' protocal. In my practice, install the JCE can solve
this "TLS_RSA_WITH_AES_256_CBC_SH
Github user birdspring commented on the issue:
https://github.com/apache/incubator-predictionio/issues/260
@Jimjipeng I've also met this problem, have you solved it?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If yo
Github user Christophy commented on the issue:
https://github.com/apache/incubator-predictionio/issues/275
Hi, XueSong, you may already figured out, despite the connection error,
your engine is trained and inserted successfully.
So maybe there is a request made after the training
22 matches
Mail list logo
