THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- 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.
- Review the criteria for inclusion of patches (below).
- Create an issue for your patch on the Spark Project JIRA.
- If you are proposing a larger change, attach a design document to your JIRA first (example) and email the dev mailing list to discuss it.
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.
- Follow the Spark Code Style Guide. Before sending in your pull request, you can run
./dev/lint-scala
and./dev/lint-python
to validate the style. - Make sure that your code passes the automated tests (see Automated Testing below)
- Add new tests for your code. We use ScalaTest for testing. Just add a new Suite in
core/src/test
, or methods to an existing Suite. - Update the documentation (in the
docs
folder) if you add a new feature or configuration parameter.
...