| James E. King III | fc6c15c | 2019-02-07 17:16:59 -0500 | [diff] [blame^] | 1 | <!-- Explain the changes in the pull request below: --> |
| 2 | |
| James E. King III | 4927179 | 2019-01-28 08:32:47 -0500 | [diff] [blame] | 3 | |
| James E. King III | 4927179 | 2019-01-28 08:32:47 -0500 | [diff] [blame] | 4 | |
| James E. King III | 91a4fd7 | 2019-01-30 10:24:33 -0500 | [diff] [blame] | 5 | <!-- We recommend you review the checklist before submitting a pull request. --> |
| James E. King III | 85db0fe | 2018-04-06 08:37:11 -0400 | [diff] [blame] | 6 | |
| James E. King III | 4927179 | 2019-01-28 08:32:47 -0500 | [diff] [blame] | 7 | - [ ] Did you squash your changes to a single commit? |
| 8 | |
| James E. King III | 91a4fd7 | 2019-01-30 10:24:33 -0500 | [diff] [blame] | 9 | - [ ] Do you need an [Apache Jira](https://issues.apache.org/jira/projects/THRIFT/issues/) ticket?<details><summary>Expand for guidance...</summary> |
| 10 | - `Yes` if your change requires a release note. |
| 11 | - `Yes` if your change is a breaking change. |
| 12 | - `No` if you change is trivial, such as fixing a typo. |
| 13 | </details> |
| 14 | |
| 15 | - [ ] Is this change worthy of a release note? <details><summary>Examples of Release Note-worthy examples...</summary> |
| 16 | - Breaking Changes |
| 17 | - New, Deprecated, or Removed Languages |
| 18 | - Security Fixes |
| 19 | - Significant Refactoring |
| 20 | - Changing how the product is built |
| 21 | </details> |
| James E. King III | 4927179 | 2019-01-28 08:32:47 -0500 | [diff] [blame] | 22 | |
| James E. King III | 91a4fd7 | 2019-01-30 10:24:33 -0500 | [diff] [blame] | 23 | - [ ] Breaking changes have additional requirements: <details><summary>Expand for instructions...</summary> |
| 24 | - Add or reference an existing Apache Jira THRIFT ticket. |
| 25 | - Add a `Breaking-Change` label to the Jira ticket. |
| 26 | - Add a note to the `lib/<language>/README.md` file. |
| 27 | - Add a line to the `CHANGES.md` file. |
| 28 | </details> |
| 29 | |
| 30 | - [ ] Does this change require a build? <details><summary>Expand for guidance...</summary> |
| 31 | - `Yes` for any code change |
| 32 | - `Yes` for any build script change |
| 33 | - `Yes` for any docker build environment change |
| 34 | - `Yes` for any change affecting the cross test suite |
| 35 | - `No` for documentation-only changes |
| 36 | - `No` for trivial changes, for example fixing a typo. |
| 37 | <br/> |
| 38 | If your change does not require a build, you can add [ci skip] to the end of your commit message.<br/> |
| 39 | This will avoid costly and unnecessary builds in both the pull request and once it is merged. |
| 40 | </details> |
| 41 | |
| James E. King III | fc6c15c | 2019-02-07 17:16:59 -0500 | [diff] [blame^] | 42 | <!-- |
| 43 | The Contributing Guide at: |
| 44 | https://github.com/apache/thrift/blob/master/CONTRIBUTING.md |
| 45 | has more details and tips for committing properly. |
| 46 | --> |