Re: Component naming in the PR title

2016-11-13 Thread Hyukjin Kwon
I see. I was just curious as I find myself hesitating when I open a PR time to time. Thank you both for echoing! On 14 Nov 2016 5:02 a.m., "Sean Owen" wrote: > Yes they really correspond to, if anything, the categories at > spark-prs.appspot.com . They aren't that consistently used however and

Re: Component naming in the PR title

2016-11-13 Thread Sean Owen
Yes they really correspond to, if anything, the categories at spark-prs.appspot.com . They aren't that consistently used however and there isn't really a definite list. It is really mostly of use for the fact that it tags emails in a way people can filter semi-effectively. So I think we have left i

Re: Component naming in the PR title

2016-11-13 Thread Jacek Laskowski
Hi Hyukjin, What's worked for me so the Spark committers have accepted was to use the first group SQL, MLlib, Core, Python, Scheduler, Build, Docs, Streaming, Mesos, Web UI, YARN, GraphX, R with all the letters uppercase. It's less to remember so I'd vote for keeping it in use (or be acceptable

Component naming in the PR title

2016-11-12 Thread Hyukjin Kwon
Hi all, First of all, this might be minor but I just have been curious of different PR titles in particular component part. So, I looked through Spark wiki again and I found the description not quite the same with the PRs. It seems, it is said, Pull Request ... 1. The PR title should