Guide for Hive Committers

This page contains guidelines for committers of the Apache Hive project. (If you're currently a contributor, and are interested in how we add new committers, read BecomingACommitter)

...

1. Ensure that the patch has a +1 vote, and that 24 hours have elapsed since the first +1 vote was cast on JIRA. Note that this rule appears in the Hive Bylaws. Do not ignore it.
2. Include the Jira issue id in the commit message, along with a short description of the change and the name of the contributor if it is not you. Be sure to get the issue id right, as this causes Jira to link to the change in Subversion (use the issue's "All" tab to see these).
   
   1. if contributor is you then add the following suffix to commit message "(<you>, reviewed by <reviewer>)". Example: "HIVE-123. Add awesomesauce to the optimizer. (jvs, reviewed by Ashutosh Chauhan)"
   2. if contributor is not you then add the following suffix to commit message "(<contributor> via <you>)". Example: "HIVE-123. Add awesomesauce to the optimizer. (Mike Brakestoner via jvs)"
3. Don't forget to do 'svn add' on any new files, and 'svn delete' on any files that have been 'deleted' by the patch.
4. Resolve the issue as fixed, thanking the contributor. Always set the "Fix Version" at this point, but please only set a single fix version, the earliest release in which the change will appear.
5. Use the -E option to make sure that empty files are removed during the commit.

...

To commit changes to the website and re-publish them:

% svn co https://svn.apache.org/repos/asf/hive/site hive-site
% cd hive-site

# Make your changes in the author/src/documentation/content/xdocs subdirectory.
# Then run 'ant' to generate the new website. This will cause
# files to be updated/added in the publish/ subdirectory.
% ant

% svn status
M       author/src/documentation/content/xdocs/credits.xml
X       author/src/documentation/skins
M       publish/credits.html
M       publish/credits.pdf

# Inspect the modified/added files in the publish directory,
# and commit the changes once you are satisfied with them:

% svn commit -m "Add Bob to list of committers on credits page (cws)"

...

If a patch needs to be backported to previous branches, follow these steps.

1. Commit the changes to trunk and note down the revision number, say 4001. (Revision number is displayed as response to your svn commit command).
   2. Check out the desired branch and execute this command from the root directory.

   Code Block
   svn merge -r 4000:4001 https://svn.apache.org/repos/asf/hive/trunk . svn commit

...