aboutsummaryrefslogtreecommitdiff
path: root/bzip2.1
diff options
context:
space:
mode:
authorMark Wielaard <mark@klomp.org>2019-06-25 19:22:37 +0200
committerMark Wielaard <mark@klomp.org>2019-06-25 19:30:27 +0200
commitf1e937776c5f331e24cc63a9d8e7ae9445a76761 (patch)
treed67b152eb7a70bc63146a1f0edba0e8126314669 /bzip2.1
parentff986850159a1ea0c75617ffa792d1bb2069856e (diff)
downloadbzip2-f1e937776c5f331e24cc63a9d8e7ae9445a76761.tar.gz
bzip2-f1e937776c5f331e24cc63a9d8e7ae9445a76761.tar.bz2
bzip2-f1e937776c5f331e24cc63a9d8e7ae9445a76761.zip
Add prepare-release.sh script.
Script to run to prepare a new release. It will update the release number and tell you to update the CHANGES file and to double check everything looks before doing the release commit and tagging. Afterwards you probably want to run release-update.sh to upload the release and update the website at https://sourceware.org/bzip2/ There are embedded version strings and dates in a couple of places. To keep the script simple remove some that aren't absolutely necessary. README now just points to CHANGES. README.COMPILATION.PROBLEMS only mentions the version once at the top. bzip2.c only mentions the version once when doing --version. manual.xml now doesn't have any embedded versions, just uses &bz-version; everywhere.
Diffstat (limited to 'bzip2.1')
0 files changed, 0 insertions, 0 deletions