Skip to end of metadata
Go to start of metadata


Merge develop in master

Straight up Git, no flow. Example with 1.4 branch.

# 1) Make sure develop is up to date, NEWS edited, version.m4 updated (append rc1 to version)
# 2) get latest master and develop commits
git fetch
git checkout origin/1.4/master
# 3) Merge and tag. --no-ff to force git to create a merge commit
git merge --no-ff origin/1.4/develop
git tag -a 1.4.8rc1
# 4) push! Make sure you are a release manager in the github repo settings
git push
git push --tags

Create and sign tarball

# 1) Make sure you have access to the corp and dist repository. 'svn update' if necessary.
svn co svn+ssh:// #read access
svn co svn+ssh:// #write access
# 2) Make sure we have a complete clean copy of master, new clone is effective
git clone ods-release1.4.8
cd ods-release1.4.8/
git checkout origin/1.4/master
# 3) Create tarball
make dist
# 4) Copy tarball to dist:
# use ~/odsdist/source/ for final release
cp opendnssec-1.4.8rc1.tar.gz ~/odsdist/source/testing/
# 5) Sign the tarball. The passphrase needs to be unlocked by Benno, Jakob or Yuri.
# See odscorp/development/pgp/README for (hardly any) details
cd ~/odscorp/development/pgp
sh ~/repo/odsdist/source/testing/opendnssec-1.4.8rc1.tar.gz
cd ~/odsdist/source/testing/
gpg --verify opendnssec-1.4.8rc1.tar.gz.sig opendnssec-1.4.8rc1.tar.gz
# 6) Add files to repository.
svn add opendnssec-1.4.8rc1.tar.gz*
svn ci -m "OpenDNSSEC 1.4.8rc1"

Announce rc1 on maintainers and announce list

Just do it.

Final Release

Repeat all steps but now don't include the rc1 postfix.

Put release on website:

(not so) terse description of release process

  • No labels