Updated Release checklist (markdown)
parent
ceded3e0a3
commit
ec7a889149
|
@ -2,6 +2,7 @@ Note that some of these can be done concurrently.
|
|||
|
||||
1. Choose to merge or not merge pending changes
|
||||
- Ideally there would be a release candidate and rigorous testing, but there never seems to be enough time...
|
||||
1. Test Issues labelled "Patch pending"
|
||||
1. Write the changelog
|
||||
- You can use `git log --pretty='format:[%h %an] %s%n%b%n' 2.x..` (substitute the last release tag for "2.x") as a starting point.
|
||||
- After parsing through the commits to get a list of user-facing changes, group them as in the example below. Use past tense. You should include Issue numbers for bugs and feature requests, but not PRs.
|
||||
|
|
Loading…
Reference in New Issue