|
| 1 | +Following this checklist to help us incorporate your |
| 2 | +contribution quickly and easily: |
| 3 | + |
| 4 | + - [ ] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MSOURCES) filed |
| 5 | + for the change (usually before you start working on it). Trivial changes like typos do not |
| 6 | + require a JIRA issue. Your pull request should address just this issue, without |
| 7 | + pulling in other changes. |
| 8 | + - [ ] Each commit in the pull request should have a meaningful subject line and body. |
| 9 | + - [ ] Format the pull request title like `[MSOURCES-XXX] - Fixes bug in ApproximateQuantiles`, |
| 10 | + where you replace `MSOURCES-XXX` with the appropriate JIRA issue. Best practice |
| 11 | + is to use the JIRA issue title in the pull request title and in the first line of the |
| 12 | + commit message. |
| 13 | + - [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. |
| 14 | + - [ ] Run `mvn clean verify -Prun-its` to make sure integration tests checks pass. A more thorough check will |
| 15 | + be performed on your pull request automatically. |
| 16 | + |
| 17 | +If your pull request is about ~20 lines of code you don't need to sign an |
| 18 | +[Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure |
| 19 | +please ask on the developers list. |
| 20 | + |
| 21 | +To make clear that you license your contribution under |
| 22 | +the [Apache License Version 2.0, January 2004](https://www.apache.org/licenses/LICENSE-2.0) |
| 23 | +you have to acknowledge this by using the following check-box. |
| 24 | + |
| 25 | + - [ ] I hereby declare this contribution to be licenced under the [Apache License Version 2.0, January 2004](https://www.apache.org/licenses/LICENSE-2.0) |
| 26 | + |
| 27 | + - [ ] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). |
0 commit comments