Checklist for Releasing a New Version of Crack
This is for use by Crack developers when releasing a distro.
-
Verify that all new features are documented in the manual.
-
Update ReleaseNotes with the salient changes in the release.
-
Update configure.in with the new version number (in both AC_INIT and AC_INIT_AUTOMAKE)
-
Update Makefile.am.in with new library versions for all libraries specifying --version-info (see
-
Update CMakeLists.txt with the new versions of LLVM, Crack and the shared library version numbers (CRACK_VERSION, LLVM_MIN_VERSION, LLVM_MIN_VERSION_TEXT, CRACKLANG_API_VERSION, NATRUN_API_VERSION, DEBUG_API_VERSION)
-
Update all references to the current crack version in the manual.
-
Update INSTALL with the new versions of LLVM and Crack
-
clone the repository and in the clone run:
./bootstrap; ./configure; make distcheck
-
check the size of the tarball to make sure there are no binaries.
-
tag the revision with the release branch:
git tag -a /release-number/
-
upload the tarball
-
add the manual and tarball to the website git repo
-
update the front page with links to the new download and manual
-
update the blog