Re: PRs for documentation?

2018-06-20 Thread Jeff Zhang
Sorry, Alex, 0.8.0 RC5 is out today. I am afraid we could not get it into 0.8 if the voting pass, but I will merge it into next release. And thanks for the contribution. Alex Ott 于2018年6月20日周三 下午3:28写道: > Hello Jeff > > I know that problem with OSS projects - it's always not enough time :-( >

Re: PRs for documentation?

2018-06-20 Thread Alex Ott
Hello Jeff I know that problem with OSS projects - it's always not enough time :-( My changes are quite small, mostly formatting, and it would be nice to get them into 0.8 branch, as some documentation is really looks not accurate because of incorrect formatting. Regarding this one - should I

Re: PRs for documentation?

2018-06-19 Thread Jianfeng (Jeff) Zhang
It is not necessary to create ticket for document change if it is trivial change, otherwise you still need to create ticket. Regarding the review, I am sorry that there¹s no much bandwidth to review for committers, if there¹s no response in 3 days, please ping someone or send mail in dev mail

PRs for documentation?

2018-06-19 Thread Alex Ott
Hi all I have a question - should I file JIRA for documentation fixes/improvements? For example, I opened PR some time ago ( https://github.com/apache/zeppelin/pull/2997) that fixes multiple problems and improves documentation. But it still not merged... (conflict occur afterwards - I'll rebase