Skip to content
Commits on Source (2)
......@@ -22,6 +22,9 @@ ifdex-ignores::
packaging.txt::
Guidance for binary package builders.
release::
Script for shipping a release.
TODO::
List of items the NTPsec developers are working on.
......
......@@ -490,7 +490,8 @@ should be able to use "git stash" to get around that.
== Release Checklist ==
This is the release checklist to be used by the project manager to cut each 0.9.X release.
This is the release checklist to be used by the project manager to cut
each 0.9.X release.
. Decide that it's time to cut a release. This can be driven by landing
a significant new feature, landing a critical fix, or just that enough
......@@ -513,41 +514,6 @@ This is the release checklist to be used by the project manager to cut each 0.9.
. Modify the .../NEWS file, changing the "Repository head".
to the current date and the version string.
. Add GPG signed git tag.
git tag -u 477C7528 -m "version 0.9.1" NTPsec_0_9_1
. Commit those modifications to the repository.
git commit -Ssecurity@ntpsec.org -s -m "version 0.9.1"
. Push the repository upstream.
Don't forget to use the --tags option to push the new tag as well.
git push --tags
. Generate release tarball.
git archive --format=tar.gz -v -o ../ntpsec-0.9.1.tar.gz NTPsec_0_9_1
. Generate GPG detached signature of the release tarball.
gpg -u 477C7528 --output ntpsec-0.9.1.tar.gz.sig --detach-sig ntpsec-0.9.1.tar.gz
. Generate sha256sum file for the release tarball.
shasum -a 256 -p ntpsec-0.9.1.tar.gz >ntpsec-0.9.1.tar.gz.sum
. GPG sign that sha256sum file.
gpg -u 477C7528 -a --output ntpsec-0.9.1.tar.gz.sum.asc ntpsec-0.9.1.tar.gz.sum
. Copy the release tarball, GPG detached signature of the release
tarball, and the signed sha256sum file to the ftp artifact server.
scp ntpsec-0.9.1.tar* releasemanager@hostname.ntpsec.org:ftp
. Email the release message to the devel list. The release message
should include the sha256sum value, and should be GPG signed.
. Run the "release" script in this directory.
//end
#!/bin/sh
# Cut an ntpsec release. VERSION must contain the correct release number.
#
# Run with no arguments to dry-run this.
# Check that we really mean it.
if [ "$1" = "go" ]
then
do=""
else
do="echo"
fi
V=`cat ../VERSION`
UV=`cat ../VERSION | tr '.' '_'`
K=477C7528 # Release manager's GPG key ID
do=echo
# Tag the version
$do git tag -u ${K} -m "version ${V}" NTPsec_${UV}
# Commit those modifications to the repository.
$do git commit -Ssecurity@ntpsec.org -s -m "version ${V}"
# Push the repository upstream.
$do git push
$do git push --tags
# Generate release tarball.
$do git archive --format=tar.gz -v -o ../ntpsec-${V}.tar.gz NTPsec_${UV}
# Generate GPG detached signature of the release tarball.
$do gpg -u ${K} --output ntpsec-${V}.tar.gz.sig --detach-sig ntpsec-${V}.tar.gz
# Generate sha256sum file for the release tarball.
$do shasum -a 256 -p ntpsec-${V}.tar.gz >ntpsec-${V}.tar.gz.sum
# GPG sign that sha256sum file.
$do gpg -u ${K} -a --output ntpsec-${V}.tar.gz.sum.asc ntpsec-${V}.tar.gz.sum
# Copy the release tarball, GPG detached signature of the release
# tarball, and the signed sha256sum file to the ftp artifact server.
$do scp ntpsec-${V}.tar* releasemanager@hostname.ntpsec.org:ftp
# end