summaryrefslogtreecommitdiff
path: root/vendor/github.com/klauspost
diff options
context:
space:
mode:
authorMatthew Heon <mheon@redhat.com>2021-05-17 16:40:35 -0400
committerMatthew Heon <mheon@redhat.com>2021-05-17 16:40:35 -0400
commit8f3605e7d620192357b1ef4a0a57b92a3449d887 (patch)
treea30bfe9ddc22907b6b55446c2d761e7a29dcb471 /vendor/github.com/klauspost
parent93c3e03227bee7b3b6f58e8fe038965505bbfa69 (diff)
downloadpodman-8f3605e7d620192357b1ef4a0a57b92a3449d887.tar.gz
podman-8f3605e7d620192357b1ef4a0a57b92a3449d887.tar.bz2
podman-8f3605e7d620192357b1ef4a0a57b92a3449d887.zip
Add script for identifying commits in release branches
One of the worst parts of a Podman release is writing the release notes. It requires manually going through all merged commits since the last release, figuring out what was actually done, and writing a small blurb about what was fixed. The worst part of this is the difficulty in finding the commits that were actually included in previous releases - our extensive backports to prior releases mean that there are usually dozens of commits that were included in a prior release, but do not have a matching SHA (as the original author did not do the backport, and often the commit required massaging to cherry-pick in). This script automates the job of finding commits in one release branch that are not in another, with filtering to remove most cherry-picked commits. It makes my life a lot easier during releases, so I figured I'd include it in hack/ so anyone else stuck with the enjoyable task of writing release notes can have a slightly easier life. The script is written in absolutely terrible Ruby and its performance is absolutely terrible, but you only need to run it once per major release and a 30-second wait to generate the list of commits to include isn't bad. Signed-off-by: Matthew Heon <mheon@redhat.com>
Diffstat (limited to 'vendor/github.com/klauspost')
0 files changed, 0 insertions, 0 deletions