You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zeppelin.apache.org by Alex Ott <al...@gmail.com> on 2018/06/19 13:50:16 UTC

PRs for documentation?

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 soon)

-- 
With best wishes,                    Alex Ott
http://alexott.net/
Twitter: alexott_en (English), alexott (Russian)

Re: PRs for documentation?

Posted by Jeff Zhang <zj...@gmail.com>.
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 <al...@gmail.com>于2018年6月20日周三 下午3:28写道:

> 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 open a separate PR against 0.8 to make it
> into release?
>
>
> On Wed, Jun 20, 2018 at 1:32 AM, Jianfeng (Jeff) Zhang <
> jzhang@hortonworks.com> wrote:
>
> >
> > 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 list.
> >
> >
> >
> > Best Regard,
> > Jeff Zhang
> >
> >
> >
> >
> >
> > On 6/19/18, 9:50 PM, "Alex Ott" <al...@gmail.com> wrote:
> >
> > >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 soon)
> > >
> > >--
> > >With best wishes,                    Alex Ott
> > >http://alexott.net/
> > >Twitter: alexott_en (English), alexott (Russian)
> >
> >
>
>
> --
> With best wishes,                    Alex Ott
> http://alexott.net/
> Twitter: alexott_en (English), alexott (Russian)
>

Re: PRs for documentation?

Posted by Alex Ott <al...@gmail.com>.
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 open a separate PR against 0.8 to make it
into release?


On Wed, Jun 20, 2018 at 1:32 AM, Jianfeng (Jeff) Zhang <
jzhang@hortonworks.com> wrote:

>
> 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 list.
>
>
>
> Best Regard,
> Jeff Zhang
>
>
>
>
>
> On 6/19/18, 9:50 PM, "Alex Ott" <al...@gmail.com> wrote:
>
> >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 soon)
> >
> >--
> >With best wishes,                    Alex Ott
> >http://alexott.net/
> >Twitter: alexott_en (English), alexott (Russian)
>
>


-- 
With best wishes,                    Alex Ott
http://alexott.net/
Twitter: alexott_en (English), alexott (Russian)

Re: PRs for documentation?

Posted by "Jianfeng (Jeff) Zhang" <jz...@hortonworks.com>.
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 list.



Best Regard,
Jeff Zhang





On 6/19/18, 9:50 PM, "Alex Ott" <al...@gmail.com> wrote:

>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 soon)
>
>-- 
>With best wishes,                    Alex Ott
>http://alexott.net/
>Twitter: alexott_en (English), alexott (Russian)