Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/2375
Thanks @1ambda LGTM
---
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,
Github user soralee commented on the issue:
https://github.com/apache/zeppelin/pull/2381
Hi, finally I finished the above To-do list.
@1ambda @Leemoonsoo Could you confirm this, again?
For now, the quick links is connected with 0.8.0-SNAPSHOT documentation.
@Leemoonsoo cou
Github user tinkoff-dwh commented on the issue:
https://github.com/apache/zeppelin/pull/2309
Ready to review
---
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
Github user tinkoff-dwh commented on the issue:
https://github.com/apache/zeppelin/pull/2268
Ready to review
---
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
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/2343
LGTM. Will merge it now.
---
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 wis
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/2343
---
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 feature is e
It means we release with some interpreters and deploy all interpreters into
maven separately. We already had a install-interpreter script inside it. If
someone wants to install specific interpreter not included in default
release package, they can use that script to install specific one.
On Sun, J
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/2393
Ready to review. Please make sure it works with latest jupyter format with
major version of 4
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitH
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/2388
I'll merge 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 your project does not have this feature
enabled and wishes so, or
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/2369
LGTM
---
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 fe
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/2309
LGTM. @1ambda Can you verify 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 your project does not have this feature
enabled
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/2282
ping.
---
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 f
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/2388
Can you close it by yourself?
---
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 an
Sure - I think it will be important to discuss what criteria to use to decide
what is included vs what will be released separately.
_
From: Jongyoul Lee mailto:jongy...@gmail.com>>
Sent: Sunday, June 4, 2017 9:47 AM
Subject: Re: [DISCUSS] Reducing default interpreters
+1 too
On Sun, Jun 4, 2017 at 2:16 AM, Park Hoon <1am...@gmail.com> wrote:
> +1 for release 0.7.2 since 0.7.1 has few critical bugs.
>
>
> Thanks.
>
> On Sun, Jun 4, 2017 at 9:13 AM, Felix Cheung
> wrote:
>
> > +1
> >
> > From: moon soo Lee
> > Sent: Saturday,
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/2393
Yes, sure. I'll made another PR for adding docs
---
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
Jongyoul Lee created ZEPPELIN-2616:
--
Summary: Add docs to describe how to use this feature
Key: ZEPPELIN-2616
URL: https://issues.apache.org/jira/browse/ZEPPELIN-2616
Project: Zeppelin
Issue
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/2393
Made [ZEPPELIN-2616](https://issues.apache.org/jira/browse/ZEPPELIN-2616)
---
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 p
Following is last discussion related to release package size.
https://lists.apache.org/thread.html/69f606409790d7ba11422e8c6df941a75c5dfae0aca63eccf2f840bf@%3Cusers.zeppelin.apache.org%3E
at this time, we have discussed about having bin-all (every interpreters),
bin-min (selected interpreters), b
+1 for release 0.7.2
18637156...@163.com
From: moon soo Lee
Date: 2017-06-04 01:47
To: dev
Subject: [DISCUSS] Release 0.7.2
Hi,
Since 0.7.1 release, we have resolved 38 issues and that includes most of
critical issues in 0.7.2 umbrella issue [1].
Since 0.7.1 has major problems like ZEPPELI
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2356
This PR makes unnecessary margin above the Editor inside of Paragraph.
before

this part is different between #2371. Let me update to match it.
---
If you
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2381
splitting this PR into multiples
- might be painful for the author. but it would help to review easily.
- review process might be slower. so hope @AhyoungRyu would help review all
sepa
Github user soralee commented on the issue:
https://github.com/apache/zeppelin/pull/2381
Um.. So, for quickly review, I'll separate this PR to 2 PR.
1. updating navbar and main sections.
2. adding technologies and deployments
---
If your project is set up for it, you can rep
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2356
@Leemoonsoo Hi, Thanks for the feedback.
- it is actually intended. otherwise highlight color will override the
paragraph setting menus.
- let me find an another way (e.g applying `z-
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2356
Yeah, that was my guess. I think keeping layout unchanged is more important
than prevent overlapping paragraph control and text editor.
---
If your project is set up for it, you can reply to
Github user DrIgor commented on the issue:
https://github.com/apache/zeppelin/pull/2372
Any other questions?
---
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
GitHub user jongyoul reopened a pull request:
https://github.com/apache/zeppelin/pull/2393
[ZEPPELIN-2590] Convert jupyter's notebook to Zeppelin's note
### What is this PR for?
Converting jupyter's notebook to Zeppelin's note
### What type of PR is it?
[Feature]
Github user jongyoul closed the pull request at:
https://github.com/apache/zeppelin/pull/2393
---
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 feature is
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2372
I failed to test this feature since terminal i am using doesnt support that
option. others can help review. sorry for the late reply.
---
If your project is set up for it, you can reply to this em
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2369
Merge to master if no further comment.
---
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
Github user DrIgor commented on the issue:
https://github.com/apache/zeppelin/pull/2250
Please explain what issues I need to fix)
---
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
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/2250
I think we'd better take care of the comments left.
---
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 t
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2354
LGTM. Thanks @sohaibiftikhar for the contribution.
Merge to master if no further discussions here.
---
If your project is set up for it, you can reply to this email and have your
reply
GitHub user soralee opened a pull request:
https://github.com/apache/zeppelin/pull/2394
[gh-pages] [ZEPPELIN-2597] adding technologies and deployments (Main Page)
### What is this PR for?
This PR is for Improving more comfortable guidance for point of user view
in the main zeppe
Github user soralee commented on the issue:
https://github.com/apache/zeppelin/pull/2381
@1ambda, @Leemoonsoo, @AhyoungRyu, I created a PR regrading `Technologies
and Deployments`
#2394. Let me make a remainder PR.
---
If your project is set up for it, you can reply to this emai
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/2368
ping
---
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 fe
Github user soralee commented on the issue:
https://github.com/apache/zeppelin/pull/2394
@AhyoungRyu @1ambda @Leemoonsoo, please review again!
---
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
Github user sravan-s commented on the issue:
https://github.com/apache/zeppelin/pull/2394
I think it would be better if the font sizes inside top box(technologies)
and bottom(deployments) were of same size and had a uniform margin / padding
scheme. Also about **use now** and **learn m
58 matches
Mail list logo