[ https://issues.apache.org/jira/browse/HBASE-15892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15307105#comment-15307105 ]
stack commented on HBASE-15892: ------------------------------- [~appy] This patch won't go into branch-1. There is no dev-support/python-requirements.txt Want to make a new branch-1 patch? > submit-patch.py: Single command line to make patch, upload it to jira, and > update review board > ---------------------------------------------------------------------------------------------- > > Key: HBASE-15892 > URL: https://issues.apache.org/jira/browse/HBASE-15892 > Project: HBase > Issue Type: New Feature > Reporter: Appy > Assignee: Appy > Priority: Trivial > Fix For: 2.0.0 > > Attachments: HBASE-15892_master_v1.patch, > HBASE-15892_master_v2.patch, HBASE-15892_master_v3.patch > > > Adds dev-support/submit-patch.py > The script builds a new patch (using specified branch/tracking branch as base > branch), uploads it to jira, and updates diff of the review on ReviewBoard. > Remote links in the jira are used to figure out if a review request already > exists. If no review request is present, then creates a new one and populates > all required fields using jira summary, patch description, etc. > *Authentication* > Since attaching patches & changes links on JIRA and creating/changing review > request on ReviewBoard requires a logged in user, the script will prompt you > for username and password. To avoid the hassle every time, I'd suggest > setting up ~/.apache-creds with the login details and encrypt it as explained > in scripts help message footer. > *Python dependencies* > To install required python dependencies, execute {{pip install -r > dev-support/python-requirements.txt}} -- This message was sent by Atlassian JIRA (v6.3.4#6332)