1# Objective
2
3Describe the objective or issue this PR addresses.
4
5If you're fixing a specific issue, say "Fixes #X" and the linked issue will automatically be closed when this PR is merged.
6Under each bullet point, describe how this change addressed those objectives if it is not obvious.
7
8**Changes that will affect external library users must update RELEASES.md before they will be merged.**
9
10## Context
11
12Discuss any context that may be needed for a user with only passing acquaintance with this library to understand the changes you've made.
13This may include related issues, previous discussion, or relevant bits of how the library works).
14
15## Feedback wanted
16
17> This section is optional. If there are no particularly tricky or controversial changes, you can delete this section.
18
19Which parts of this PR were you unsure about? Which parts were particularly tricky?
20
21If you're stuck on part of the changes or want feedback early, open a draft PR and list the items that need to be completed here using a [checklist](https://github.blog/2014-04-28-task-lists-in-all-markdown-documents/).
22
23## Migration Guide
24
25> This section is optional. If there are no breaking changes, you can delete this section.
26
27- If this PR is a breaking change (relative to the last release of this library), describe how a user might need to migrate their code to support these changes
28- Simply adding new functionality is not a breaking change.
29- Fixing behavior that was definitely a bug, rather than a questionable design choice, is not a breaking change.