diff options
| author | Carl Worth <cworth@cworth.org> | 2010-04-15 16:08:37 -0700 |
|---|---|---|
| committer | Carl Worth <cworth@cworth.org> | 2010-04-15 16:08:37 -0700 |
| commit | f3428823e5cfa8e524e3ea7be8b497020d0693ba (patch) | |
| tree | bbae2495ae7e7d44b60584e0c4d18838215594a3 | |
| parent | cddeaa59ab9c85ae4a09cae769b8677fd60141b8 (diff) | |
Makefile: Make "make release" run the test suite.
This drops one manual step from our release process, (helping
to ensure we don't forget anything during the release).
| -rw-r--r-- | Makefile.local | 4 | ||||
| -rw-r--r-- | RELEASING | 21 |
2 files changed, 9 insertions, 16 deletions
diff --git a/Makefile.local b/Makefile.local index fed32c0..3f8f1d5 100644 --- a/Makefile.local +++ b/Makefile.local @@ -70,7 +70,9 @@ dist: $(TAR_FILE) # We invoke make recursively only to force ordering of our phony # targets in the case of parallel invocation of make (-j). .PHONY: release -release: release-verify-newer +release: + $(MAKE) test + $(MAKE) release-verify-newer $(MAKE) release-upload @echo "Please send a release announcement as follows:" @echo "" @@ -10,18 +10,7 @@ Here are the steps to follow to create a new notmuch release: not mentioned there. If so, pleas add them, (and ask the authors of the commits to update NEWS in the future). -3) Verify that the notmuch test suite passes. - - Currently this is by running: - - ./test/notmuch-test - - And manually verifying that every test says PASS. We plan to - fix this to automatically check the results and even to - automatically run the test suite as part of a Makefile target - described below. - -4) Increment the libnotmuch library version in lib/Makefile.local +3) Increment the libnotmuch library version in lib/Makefile.local See the instructions there for how to increment it. The command below can be useful for inspecting header-file changes @@ -37,11 +26,13 @@ Here are the steps to follow to create a new notmuch release: Commit this change. -5) Run "make VERSION=X.Y release" which will perform the following steps: +4) Run "make VERSION=X.Y release" which will perform the following steps: For the X.Y version, we'll generally just increment Y. But for major milestones of usability we're increment X as well. + * Compile the current notmuch code (aborting release if it fails) + * Run the notmuch test suite (aborting release if it fails) * Check that the notmuch version consists of only two components * Check that no release exists with the current version * Verify that "make dist" completes successfully @@ -58,9 +49,9 @@ Here are the steps to follow to create a new notmuch release: * Push that tag * Provide some text for the release announcement (see below). -6) Increment the notmuch version by adding a .1 micro number, commit, and push. +5) Increment the notmuch version by adding a .1 micro number, commit, and push. -7) Send a message to notmuch@notmuchmail.org to announce the release. +6) Send a message to notmuch@notmuchmail.org to announce the release. Use the text provided from "make release" above, (if for some reason you lose this message, "make release-message" prints |