This is the process I use to get issues that have been actually merged between CKAN releases.
This assumes that the release branch has been created.
-
Run the following to obtain an
issues_2.3.txt
file with the issue number of all issues that have been merged between releases:git log --pretty=format:%s --reverse --no-merges dev-v2.7...dev-v2.8 | grep -Po "^\[#\K[0-9]+(?=^\])?" | sort -u -n > issues_2.8.txt
-
Use
issues_github.py
to obtain anissues_2.3_title.txt
file with the actual issues title (You'll need to add a GitHub API token):python issues_github.py > issues_2.8_title.txt
-
Manually triage issues into the "Major", "Minor" and "Bug fixes" sections (or discard if not relevant enough) of the CHANGELOG file