We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
1 parent a9cd3e5 commit 4048165Copy full SHA for 4048165
1 file changed
etc/notes/releasing.md
@@ -80,7 +80,7 @@ The MongoDB driver can now generate a cup of joe.
80
- This will kick off the action that reads the notes from each PR going into the release.
81
- Double check the result looks logically organized and complete
82
- As a rule of thumb, every `feat` and `fix` should have a corresponding release note
83
- - Cross-reference the list of tickets in the corresponding jira release for consistency
+ - Cross-reference the list of tickets in the corresponding JIRA release for consistency
84
- You may modify the release PR body directly for any quick edits or re-orderings.
85
- If there are any non-cosmetic changes, edit the original PRs and post a new `run release_notes` comment
86
1. Merge the release PR
0 commit comments