[Hadoop Wiki] Update of 2015MayBugBash by SomeOtherAccount
Dear Wiki user,
You have subscribed to a wiki page or wiki category on Hadoop Wiki for change
notification.
The 2015MayBugBash page has been changed by SomeOtherAccount:
https://wiki.apache.org/hadoop/2015MayBugBash?action=diffrev1=5rev2=6
1. Name the patch file (something).patch
1. Verify the patch applies cleanly
1. Fix any pre-existing comments
- 1. Test the patch locally using {{{test-patch.sh}}}
+ 1. Test the patch locally using {{{test-patch.sh}}} [See TestPatchTips for
more!]
1. '''Before uploading''', did you run {{{test-patch.sh}}}?
1. Upload the reworked patch back into JIRA.
1. Set the label to '''BB2015-05-RFC'''.
[Hadoop Wiki] Update of 2015MayBugBash by SomeOtherAccount
Dear Wiki user,
You have subscribed to a wiki page or wiki category on Hadoop Wiki for change
notification.
The 2015MayBugBash page has been changed by SomeOtherAccount:
https://wiki.apache.org/hadoop/2015MayBugBash?action=diffrev1=3rev2=4
TableOfContents(4)
+
+ {{{#!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'''.
+ }}}
+
== Information ==
-
- With over 900 patches not yet reviewed and approved for Apache Hadoop, it's
time to make some strong progress on the bug list!
+ 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.
@@ -18, +22 @@
1. Hang out on the #hadoop channel on irc.freenode.net .
== Procedures for that day ==
-
=== Source Code Contributions ===
-
Non-committers
-
1. Read through the
[[https://issues.apache.org/jira/issues/?filter=12331694|To Be Reviewed queue]].
1. Find a JIRA to work on.
1. Remove the '''BB2015-05-TBR''' label from that JIRA so that it leaves the
queue.
- 1. Work through the issues in that JIRA. Work make sure the patch applies
cleanly, test pasts locally by running against test-patch.sh, any pre-existing
committer comments are covered, etc.
- 1. When you think it is ready, set the label to '''BB2015-05-RFC'''.
+ 1. Work through the issues in that JIRA:
+ 1. Make sure the patch applies cleanly
+ 1. Fix any pre-existing comments
+ 1. '''Before uploading''', test the patch locally using {{{test-patch.sh}}}
to prevent overloading the QA servers.
+ 1. Upload the reworked patch back into JIRA.
+ 1. Set the label to '''BB2015-05-RFC'''.
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.
Committers
-
1. Read through the
[[https://issues.apache.org/jira/issues/?filter=12331695|Ready For Committer
queue]].
1. Find a JIRA to work on.
1. Remove the '''BB2015-05-RFC''' label from that JIRA so that it leaves the
queue.
1. Review the patch. If it needs more work, add a comment and add the'''
BB2015-05-TBR''' label so that it goes back into the non-committer queue.
1. Commit the patch as per usual if it is ready to go.
-
=== Non-source Code Contributions ===
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:
[Hadoop Wiki] Update of 2015MayBugBash by SomeOtherAccount
Dear Wiki user,
You have subscribed to a wiki page or wiki category on Hadoop Wiki for change
notification.
The 2015MayBugBash page has been changed by SomeOtherAccount:
https://wiki.apache.org/hadoop/2015MayBugBash?action=diffrev1=4rev2=5
1. Find a JIRA to work on.
1. Remove the '''BB2015-05-TBR''' label from that JIRA so that it leaves the
queue.
1. Work through the issues in that JIRA:
+ 1. Name the patch file (something).patch
- 1. Make sure the patch applies cleanly
+ 1. Verify the patch applies cleanly
1. Fix any pre-existing comments
- 1. '''Before uploading''', test the patch locally using {{{test-patch.sh}}}
to prevent overloading the QA servers.
+ 1. Test the patch locally using {{{test-patch.sh}}}
+ 1. '''Before uploading''', did you run {{{test-patch.sh}}}?
1. Upload the reworked patch back into JIRA.
1. Set the label to '''BB2015-05-RFC'''.
[Hadoop Wiki] Update of 2015MayBugBash by SomeOtherAccount
Dear Wiki user, You have subscribed to a wiki page or wiki category on Hadoop Wiki for change notification. The 2015MayBugBash page has been changed by SomeOtherAccount: https://wiki.apache.org/hadoop/2015MayBugBash New page: == Information == 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 a n 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. Bring your own computing power. We hope to see you there! == How to Get Involved == 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: 1. Have or create an account on [[https://issues.apache.org/jira/|Apache JIRA]]. 1. Be familiar with the instructions on HowToContribute. 1. Have a working development and test environment. See [[https://git-wip-us.apache.org/repos/asf?p=hadoop.git;a=blob;f=BUILDING.txt|BUILDING.txt]] for requirements as well as how to execute a script to create a Docker image that has all of the components. 1. Register with https://www.eventbrite.com/e/apache-hadoop-global-bug-bash-tickets-16507188445 1. Hang out on the #hadoop channel on irc.freenode.net . == Procedures for that day == === Non-source Code Contributions === The vast majority of Hadoop content, including almost all of the documentation is part of the source tree. There are multiple ways in which those who are unfamiliar with developer environments can contribute: 1. Go through the open JIRA list and verify whether functionality already exists or bug fixed. 1. [[https://wiki.apache.org/hadoop/FrontPage?action=newaccount|Create a wiki account]] and update the documentation here. 1. Collaborate with another person in testing, documentation, and other non-source related tasks that almost all patches require. === Source Code Contributions === Non-committers: 1. Read through the [[https://issues.apache.org/jira/issues/?filter=12331694|To Be Reviewed queue]]. 1. Find a JIRA to work on. 1. Remove the '''BB2015-05-TBR''' label from that JIRA so that it leaves the queue. 1. Work through the issues in that JIRA. Work make sure the patch applies cleanly, test pasts locally by running against test-patch.sh, any pre-existing committer comments are covered, etc. 1. When you think it is ready, set the label to '''BB2015-05-RFC'''. 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. Committers: 1. Read through the [[https://issues.apache.org/jira/issues/?filter=12331695|Ready For Committer queue]] 1. Find a JIRA to work on 1. Remove the '''BB2015-05-RFC''' label from that JIRA so that it leaves the queue. 1. Review the patch. If it needs more work, add a comment and add the''' BB2015-05-TBR''' label so that it goes back into the non-committer queue. 1. Commit the patch as per usual if it is ready to go.
[Hadoop Wiki] Update of 2015MayBugBash by SomeOtherAccount
Dear Wiki user, You have subscribed to a wiki page or wiki category on Hadoop Wiki for change notification. The 2015MayBugBash page has been changed by SomeOtherAccount: https://wiki.apache.org/hadoop/2015MayBugBash?action=diffrev1=1rev2=2 + TableOfContents(4) + == Information == - 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 a n 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. Bring your own computing power. We hope to see you there! + + 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. == How to Get Involved == 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: @@ -13, +18 @@ 1. Hang out on the #hadoop channel on irc.freenode.net . == Procedures for that day == - === Non-source Code Contributions === - The vast majority of Hadoop content, including almost all of the documentation is part of the source tree. There are multiple ways in which those who are unfamiliar with developer environments can contribute: - - 1. Go through the open JIRA list and verify whether functionality already exists or bug fixed. - 1. [[https://wiki.apache.org/hadoop/FrontPage?action=newaccount|Create a wiki account]] and update the documentation here. - 1. Collaborate with another person in testing, documentation, and other non-source related tasks that almost all patches require. === Source Code Contributions === - Non-committers: + + Non-committers 1. Read through the [[https://issues.apache.org/jira/issues/?filter=12331694|To Be Reviewed queue]]. 1. Find a JIRA to work on. @@ -31, +31 @@ 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. - Committers: + Committers 1. Read through the [[https://issues.apache.org/jira/issues/?filter=12331695|Ready For Committer queue]] 1. Find a JIRA to work on @@ -39, +39 @@ 1. Review the patch. If it needs more work, add a comment and add the''' BB2015-05-TBR''' label so that it goes back into the non-committer queue. 1. Commit the patch as per usual if it is ready to go. + + === Non-source Code Contributions === + 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: + + 1. Go through the open JIRA list and verify whether functionality already exists or bug fixed. + 1. [[https://wiki.apache.org/hadoop/FrontPage?action=newaccount|Create a wiki account]] and update the documentation here. + 1. Collaborate with another person in testing, documentation, and other non-source related tasks that almost all patches require. +
[Hadoop Wiki] Update of 2015MayBugBash by SomeOtherAccount
Dear Wiki user, You have subscribed to a wiki page or wiki category on Hadoop Wiki for change notification. The 2015MayBugBash page has been changed by SomeOtherAccount: https://wiki.apache.org/hadoop/2015MayBugBash?action=diffrev1=2rev2=3 Committers - 1. Read through the [[https://issues.apache.org/jira/issues/?filter=12331695|Ready For Committer queue]] + 1. Read through the [[https://issues.apache.org/jira/issues/?filter=12331695|Ready For Committer queue]]. - 1. Find a JIRA to work on + 1. Find a JIRA to work on. 1. Remove the '''BB2015-05-RFC''' label from that JIRA so that it leaves the queue. 1. Review the patch. If it needs more work, add a comment and add the''' BB2015-05-TBR''' label so that it goes back into the non-committer queue. 1. Commit the patch as per usual if it is ready to go. @@ -43, +43 @@ === Non-source Code Contributions === 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: - 1. Go through the open JIRA list and verify whether functionality already exists or bug fixed. + 1. Go through the [[https://issues.apache.org/jira/issues/?filter=12327844|open JIRA list]] and verify whether it is functionality that already exists, a bug that has already been fixed, or is still a valid issue. 1. [[https://wiki.apache.org/hadoop/FrontPage?action=newaccount|Create a wiki account]] and update the documentation here. 1. Collaborate with another person in testing, documentation, and other non-source related tasks that almost all patches require.
