{{{#!wiki red/solid IMPORTANT NOTE: Apache has limited QA capabilities. It is extremely important that everyone avoids submitting patches to Jenkins for testing unless they are absolutely certain that all relevant tests will pass. HDFS unit tests, for example, will tie up a test slot for over two hours.
}}}
With over 900 patches not yet reviewed and approved for Apache Hadoop, it's time to make some strong progress on the bug list!
A number of Apache Hadoop committers and Hadoop-related tech companies are hosting an Apache Hadoop Community event on Friday, May 8th, after HBaseCon 2015. You are hereby invited for a fun, daylong event devoted to identifying and registering important patches and cleaning up the queue.
For this first event, we are primarily targeting individuals with some experience either working with Hadoop or working with large, open source projects. In order to hit the ground running on that day, it is recommended some pre-work be done first:
Test the patch locally using {{test-patch.sh}} \[See TestPatchTips for more!\] |
test-patch.sh
?Note that in some cases, the functionality in older patches may already exist. Please close these JIRA, preferably as a duplicate to the JIRA that added that functionality or as Invalid with a comment stating that you believe the issue is stale and already fixed.
There is also a possibility that the patch requires no further changes and is ready for the committer to review. In that case, just change the label.
The vast majority of Hadoop content, including almost all of the documentation is part of the source tree. However, there are multiple ways in which those who are unfamiliar with developer environments can contribute: