Page History

...

• Apache New Committer Guide
• Apache Committer FAQ

The first act of a new core committer is typically to add their name to the credits page. This requires changing the site source in https://github.com/apache/hadoop-site/blob/asf-site/src/who.md. Once done, update the Hadoop website as described here (TLDR; don't forget to regenerate the site with hugo, and commit the generated results, too).

...

1. Commit locally: Commit the change locally to the appropriate branch (should be trunk if it is not a feature branch) using git commit -a -m <commit-message>. The commit message should include the JIRA issue id, along with a short description of the change and the name of the contributor if it is not you. Note: Be sure to get the issue id right, as this causes JIRA to link to the change in git (use the issue's "All" tab to see these). Verify all the changes are included in the commit using git status. If there are any remaining changes (previously missed files), please commit them and squash these commits into one using git rebase -i.

2. 
   

   Wiki Markup
   *Pull latest changes from remote repo:* Pull in the latest changes from the remote branch using {{git pull \-\-rebase}} (--rebase is not required if you have setup git pull to always --rebase). Verify this didn't cause any merge commits using {{git log \[\-\-pretty=oneline\]}}

   
   

3. Push changes to remote repo: Build and run a test to ensure it is all still kosher. Push the changes to the remote (main) repo using git push <remote> <branch>.
4. Backporting to other branches: If the changes were to trunk, we might want to apply them to other appropriate branches.
   1. Cherry-pick the changes to other appropriate branches via git cherry-pick -x <commit-hash>. The -x option records the source commit, and reuses the original commit message. Resolve any conflicts.
   2. If the conflicts are major, it is preferable to produce a new patch for that branch, review it separately and commit it. When committing an edited patch to other branches, please follow the same steps and make sure to include the JIRA number and description of changes in the commit message.
   3. When backporting to branch-2.7 or older branches, we need to update CHANGES.txt.
5. Resolve the issue as fixed, thanking the contributor. Follow the rules specified at Apache Hadoop Release Versioning for how to set fix versions appropriately, it's important for tracking purposes with concurrent release lines.
6. Set the assignee if it is not set. If you cannot set the contributor to the assignee, you need to add the contributor into Contributors role in the project. Please see Adding Contributors role for the detail.

This How-to-commit video has guidance on the commit process, albeit using svn. Most of the process is still the same, except that we now use git instead.

...

1. End-user documentation, versioned with releases; and,
2. The website.

The end user documentation is maintained in the main repository (hadoop.git) and the results are committed to the hadoop-site during each release. The website itself is managed in the hadoop-site.git repository (both the source and the rendered form).

...

• Contributors who have Contributors role can become assignee of the issues in the project.
• Committers who have Committers role can set arbitrary roles in addition to Contributors role.
• Committers who have Administrators role can edit or delete all comments, or even delete issues in addition to Committers role.

How to set roles

1. Login to ASF JIRA
2. Go to the project page (e.g. https://issues.apache.org/jira/browse/HADOOP )
3. Hit "Administration" tab
4. Hit "Roles" tab in left side
5. Add Administrators/Committers/Contributors role

"Contributors 1" role was created by INFRA-12487 because we hit the upper limit of the Contributors role. If you cannot add a contributor to Contributors role, try "Contributors 1".

...