[GitHub] zeppelin issue #1957: Branch 0.6 Groovy Interpreter

2017-02-26 Thread dlukyanov
Github user dlukyanov commented on the issue: https://github.com/apache/zeppelin/pull/1957 created a new pull request [#2068](https://github.com/apache/zeppelin/pull/2068) --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well.

[GitHub] zeppelin issue #1957: Branch 0.6 Groovy Interpreter

2017-02-04 Thread felixcheung
Github user felixcheung commented on the issue: https://github.com/apache/zeppelin/pull/1957 and please add interpreter documentation .md file and update license information as suggested in the PR template `Does the licenses files need update?` should be yes. --- If your project is

[GitHub] zeppelin issue #1957: Branch 0.6 Groovy Interpreter

2017-02-01 Thread jongyoul
Github user jongyoul commented on the issue: https://github.com/apache/zeppelin/pull/1957 If you contribute code based on master, we will review and merge it into master and branch-0.7 if necessary. --- If your project is set up for it, you can reply to this email and have your

[GitHub] zeppelin issue #1957: Branch 0.6 Groovy Interpreter

2017-01-30 Thread dlukyanov
Github user dlukyanov commented on the issue: https://github.com/apache/zeppelin/pull/1957 Hello Current - is it next to 0.7 ? 30 January 2017, 08:02:58, by Jongyoul Lee < notificati...@github.com >: Thanks for contributing new Groovy interpreter but we didn't

[GitHub] zeppelin issue #1957: Branch 0.6 Groovy Interpreter

2017-01-29 Thread jongyoul
Github user jongyoul commented on the issue: https://github.com/apache/zeppelin/pull/1957 Thanks for contributing new Groovy interpreter but we didn't manage the branch-0.6 anymore. Can you rebase your contribution onto current master? --- If your project is set up for it, you can