The general pattern we have adopted in the Drill community is to pattern the commit message like this:
DRILL-<jira number>: <Description of what was fixed> As long as you follow that pattern, I don't think there are really any other expectations for making the pull request. On Sat, Aug 22, 2015 at 11:24 AM, Edmon Begoli <ebeg...@gmail.com> wrote: > Sounds good. Two related questions: > > > 1. Are there any special procedures regarding the pull request, referencing > issue in a commit messages, etc.? > > 2. Once I figure out the new JIRA Python tool use, how do I submit the > updates for the Drill contribution and patching documentation? > Is web documentation also maintained under the repo? > > Thank you, > Edmon > > On Saturday, August 22, 2015, Hsuan-Yi Chu <hsua...@usc.edu> wrote: > > > Hi Edmon, > > Thanks for bringing this up. I just tried, and easy_install does not work > > on my laptop either. > > > > From my experience, for the purpose of requesting reviews/submitting > > patches, you could send pull request on github. That might be the most > > common way people are using now. > > > > For the documentation, I think update the correct information is good > idea > > too. > > > > On Sat, Aug 22, 2015 at 10:50 AM, Edmon Begoli <ebeg...@gmail.com > > <javascript:;>> wrote: > > > > > What is the suitable replacement for the JIRA Python tool > > > (jira-python) still specified on the contribution web site? > > > https://drill.apache.org/docs/drill-patch-review-tool/ > > > > > > For me, easy_install is not finding jira-python library. > > > > > > It looks like this is the right tool: > > > http://pythonhosted.org/jira/ > > > > > > Which is installed as just jira with pip, but it looks like the setup > for > > > patch submission might be slightly different. > > > > > > If I am seeing this right and the new tool is needed, we should > probably > > > update the documentation (I will be happy to do so). > > > > > > Thanks, > > > Edmon > > > > > >
