Page History

Welcome contributors! We strive to include everyone's contributions. This page provides necessary guidelines on how to contribute effectively towards furthering the development and evolution of Sqoop. You should also read the guide on Setting up Development EnvironmentSqoop 1 where you will find details on how to checkout, build and test Sqoop.

...

• Test the change: It is very easy to test the change if you have the development environment setup. Run as many tests as you want with the patch. Manually test the change for functionality that you think is not fully covered via the associated tests. If you find a problem, report it.

...

• Submission checklist: Here is a checklist of things you should address before you post your patch for review:
  • Change should be clean, well-formatted, and readable. Please use two space indents, and space instead of tabs.
  • Make sure you have considered how to handle boundary condition cases and have sufficiently defensive code where necessary.
  • Add comments or java-docs where necessary.
  • Make sure that you have run checkstyle and findbugs and eliminated all warnings related to your change.
  • Is your change covered by any test case? If not, add a test case.
  • If your change affects a user interface, make sure you have updated the documentation accordingly.
  • If your change affects the development environment, make sure you update the COMPILING.txt and README files.

...