|
| 1 | +## Jira task - PUT_JIRA_LINK_HERE |
| 2 | + |
| 3 | +## BREAKING CHANGE - remove this line if your code doesn't introduce a breaking change |
| 4 | + |
| 5 | +## Release Notes Description (public) |
| 6 | + |
| 7 | +<!--- DESCRIPTION USED IN THE RELEASE NOTES |
| 8 | +
|
| 9 | +Remove this comment and replace it with the description of your changes for an external audience. |
| 10 | +This description will be pulled into public release notes. |
| 11 | +
|
| 12 | +1. What changes are you introducing? Be clear and provide a detailed overview of your changes. |
| 13 | +2. Why are you introducing the changes? Make the intent of the changes clear. |
| 14 | + - What do those changes mean for our end users? |
| 15 | + - Why should they care? |
| 16 | + - What is the context of your changes? |
| 17 | +
|
| 18 | +Additionally: |
| 19 | +
|
| 20 | +- If your changes are breaking changes, provide information on how the change affects our customers and what is required from them to be updated. |
| 21 | + If you think a migration guide would be useful, let TWs know in advance. |
| 22 | +- If your changes deprecate an API, provide what is the alternative for our customers (if it exists). State clearly that an API became deprecated. |
| 23 | +--> |
| 24 | + |
| 25 | +## Implementation details (internal) |
| 26 | + |
| 27 | +<!--- Describe technical implementation details for peer reviewers --> |
| 28 | + |
| 29 | +## Information for QA |
| 30 | + |
| 31 | +<!-- [Place an '[X]' (no spaces) in all applicable fields.] --> |
| 32 | + |
| 33 | +- [ ] Is QA testing required? |
| 34 | +- [ ] Does PR contain unit tests? |
| 35 | +- [ ] Should QA create E2E tests for the change? |
| 36 | + |
| 37 | +## Additional QA Procedures (Optional) |
| 38 | + |
| 39 | +<!--- Describe what QA needs to do if needed --> |
| 40 | + |
| 41 | +## Screenshots (if appropriate): |
0 commit comments