hadoop-common-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Hadoop Wiki] Update of "HowToContribute" by DougCutting
Date Wed, 23 Jan 2008 18:43:31 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Hadoop Wiki" for change notification.

The following page has been changed by DougCutting:
http://wiki.apache.org/hadoop/HowToContribute

The comment on the change is:
Update for TLP move.

------------------------------------------------------------------------------
- = How to Contribute to Hadoop =
+ = How to Contribute to Hadoop Core =
  
- This page describes the mechanics of ''how'' to contribute software to Hadoop.  For ideas
about ''what'' you might contribute, please see the ProjectSuggestions page.
+ This page describes the mechanics of ''how'' to contribute software to Hadoop Core.  For
ideas about ''what'' you might contribute, please see the ProjectSuggestions page.
  
  === Getting the source code ===
  
@@ -11, +11 @@

  Get the source code on your local drive using [http://lucene.apache.org/hadoop/version_control.html
SVN].  Most development is done on the "trunk":
  
  {{{
- svn checkout http://svn.apache.org/repos/asf/lucene/hadoop/trunk/ hadoop-trunk
+ svn checkout http://svn.apache.org/repos/asf/hadoop/core/trunk/ hadoop-core-trunk
  }}}
  
  If you prefer to use Eclipse for development, there are instructions for setting up SVN
access from within Eclipse at EclipseEnvironment.
  
  === Making Changes ===
  
- Before you start, send a message to the [http://lucene.apache.org/hadoop/mailing_lists.html
Hadoop developer mailing list], or file a bug report in [http://issues.apache.org/jira/browse/HADOOP
Jira].  Describe your proposed changes and check that they fit in with what others are doing
and have planned for the project.  Be patient, it may take folks a while to understand your
requirements.
+ Before you start, send a message to the [http://hadoop.apache.org/core/mailing_lists.html
Hadoop developer mailing list], or file a bug report in [http://issues.apache.org/jira/browse/HADOOP
Jira].  Describe your proposed changes and check that they fit in with what others are doing
and have planned for the project.  Be patient, it may take folks a while to understand your
requirements.
  
  Modify the source code and add some (very) nice features using your favorite IDE.[[BR]]
  
@@ -119, +119 @@

  
  Finally, patches should be ''attached'' to a bug report in [http://issues.apache.org/jira/browse/HADOOP
Jira] via the '''Attach File''' link on the jira. Please add a comment that asks for a code
review following our [:CodeReviewChecklist: code review checklist]. Please note that the attachment
should be granted license to ASF for inclusion in ASF works (as per the [http://www.apache.org/licenses/LICENSE-2.0
Apache License] ยง5). 
  
- When you believe that your patch is ready to be committed, select the 'Submit Patch' link
from the 'Available Workflow Actions' section in Jira.  Submitted patches will be automatically
tested against "trunk" by [http://lucene.zones.apache.org:8080/hudson/ Hudson], the lucene
project's continuous integration engine.  Upon test completion, Hudson will add a success
("+1") message or failure ("-1") to your bug report in Jira.  If your issue contains multiple
patch versions, Hudson tests the last patch uploaded.
+ When you believe that your patch is ready to be committed, select the 'Submit Patch' link
from the 'Available Workflow Actions' section in Jira.  Submitted patches will be automatically
tested against "trunk" by [http://hudson.zones.apache.org/hudson/ Hudson], the project's continuous
integration engine.  Upon test completion, Hudson will add a success ("+1") message or failure
("-1") to your bug report in Jira.  If your issue contains multiple patch versions, Hudson
tests the last patch uploaded.
  
- Folks should run 'ant clean test javadoc checkstyle' before selecting 'Submit Patch'.  Tests
should all pass.  Javadoc should report no warnings or errors. Checkstyle's error count should
not exceed that listed at [http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Nightly/lastSuccessfulBuild/artifact/trunk/build/test/checkstyle-errors.html
Checkstyle Errors]  Hudson's tests should only double-check things, and not be used as a primary
patch tester, which would create too much noise on the mailing list and in Jira.  Submitting
patches that fail Hudson testing is frowned on, (unless the failure is not actually due to
the patch).
+ Folks should run 'ant clean test javadoc checkstyle' before selecting 'Submit Patch'.  Tests
should all pass.  Javadoc should report no warnings or errors. Checkstyle's error count should
not exceed that listed at [http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/lastSuccessfulBuild/artifact/trunk/build/test/checkstyle-errors.html
Checkstyle Errors]  Hudson's tests should only double-check things, and not be used as a primary
patch tester, which would create too much noise on the mailing list and in Jira.  Submitting
patches that fail Hudson testing is frowned on, (unless the failure is not actually due to
the patch).
  
  If your patch involves performance optimizations, they should be validated by benchmarks
that demonstrate an improvement.
  
@@ -141, +141 @@

  
  == Stay involved ==
  
- Contributors should join the [http://lucene.apache.org/hadoop/mailing_lists.html Hadoop
mailing lists].  In particular, the commit list (to see changes as they are made), the dev
list (to join discussions of changes) and the user list (to help others).
+ Contributors should join the [http://hadoop.apache.org/core/mailing_lists.html Hadoop mailing
lists].  In particular, the commit list (to see changes as they are made), the dev list (to
join discussions of changes) and the user list (to help others).
  
  == See Also ==
  

Mime
View raw message