Versions Compared

Old Version 29

changes.mady.by.user Reynold Xin

Saved on

compared with

New Version 30

changes.mady.by.user Matei Zaharia

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Break your work into small, single-purpose patches if possible. It’s much harder to merge in a large change with a lot of disjoint features.
  2. Create a JIRA an issue for your patch on the Spark Project JIRA.
  3. If you are proposing a large change, attach a design document to your JIRA first (example) and email the dev mailing list to discuss it.

  4. Submit the patch as a GitHub pull request. For a tutorial, see the GitHub guides on forking a repo and sending a pull request. Name your pull request with the JIRA name and include the Spark module or WIP if relevant.

  5. Follow the Spark Code Style Guide. Before sending in your pull request, run ./dev/lint-scala andscala and ./dev/lint-python to python to validate the style.
  6. Make sure that your code passes the automated tests (see the Automated Testing section)
  7. Add new unit tests for your code. We use ScalaTest for testing. Just add a new Suite in core/src/test, or methods to an existing Suite.
  8. Update the documentation (in the docs folder) if you add a new feature or configuration parameter.

...