fixes: #2360
I've made a few update here: https://github.com/mikem23/koji-playground/commits/pagure/pr/2393
I'll probably have more tomorrow.
We may want to prune this down a bit. Not every pull request needs to get a release-notes entry. I generally try to filter out items that are trivial or purely internal. I tend to think of the release notes as a higher level curated summary, rather than just a more verbose changelog.
4 new commits added
misc relnotes updates
some migrations notes changes
fix kojira ref
fix broken links
1 new commit added
more break lines
Thanks! @mikem I've picked the changes here
rebased onto 6ae89f089259dea3d520012544a72a5aa7643d18
rebased onto 33fd8f90e44e12c81e76d4fa1b52ebc5226590fd
updated for recent changes
8 new commits added
more recent changes
add PR#2340
release notes - 1.22
rebased onto 1ba20b8329b5f46a81a64d779c9feee79250969b
2 new commits added
remove trival changes
fix typos
11 new commits added
remove trivial changes
add changelog - 1.22
I've added a few more updates. Same branch:
https://github.com/mikem23/koji-playground/commits/pagure/pr/2393
If those look ok to everyone, I think we can call the release notes done and move ahead.
12 new commits added
drop a few trivial entries
drop docs-only items from release notes and move "miscellaneous" changes elsewhere.
more relnotes updates
fix ref
updated
Commit 44bf6526 fixes this pull-request
Pull-Request has been merged by tkopecek
fixes: #2360