-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathrelease.sh
More file actions
executable file
·50 lines (41 loc) · 1.26 KB
/
release.sh
File metadata and controls
executable file
·50 lines (41 loc) · 1.26 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
#!/bin/bash
#
# This script automates some release steps.
#
# - Updates lists of configuration parameters and diagnostics in the manual.
#
# - Updates lists of funding sources in the manual
#
# - Updates PISM version in VERSION. This file is used to determine the PISM version
# reported by "pism -version" for PISM binaries built from a tarball (instead of a
# working copy obtained using "git clone") and in documentation.
#
# - Tags the new release.
#
# - Prints commands needed to complete the release.
#
# Run this script *after* merging new code into main.
set -u
set -e
set -x
version=${1:?Usage: \"$0 X.Y.Z\" where X.Y.Z is the new PISM version.}
# update VERSION
echo ${version} > VERSION
git add VERSION
# update the list of diagnostics and configuration parameters
make -C doc/sphinx
# update funding sources
make -C doc
git add doc/sphinx/funding.txt
# commit these changes
git commit -m "Update PISM version to ${version}"
# print changes made by this script
git --no-pager diff HEAD^
# tag this commit
git tag -a v${version} -m "The v${version} release. Please see CHANGES.rst for the list of changes."
set +x
echo "Now check if everything looks good and run:"
echo ""
echo "git push -u origin main v${version}"
echo ""
echo "Then create a release on GitHub."