aboutsummaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
-rw-r--r--Makefile.local1
-rw-r--r--RELEASING1
2 files changed, 2 insertions, 0 deletions
diff --git a/Makefile.local b/Makefile.local
index 4a6e3aeb..d78f6132 100644
--- a/Makefile.local
+++ b/Makefile.local
@@ -81,6 +81,7 @@ release: release-verify-newer $(TAR_FILE) $(SHA1_FILE) $(GPG_FILE)
mv $(TAR_FILE) $(SHA1_FILE) $(GPG_FILE) releases
ssh $(RELEASE_HOST) "rm -f $(RELEASE_DIR)/LATEST-$(PACKAGE)-[0-9]* && ln -s $(TAR_FILE) $(RELEASE_DIR)/LATEST-$(PACKAGE)-$(VERSION)"
git tag -s -m "$(PACKAGE) $(VERSION) release" $(VERSION)
+ git push origin $(VERSION)
.PHONY: release-verify-version
release-verify-version:
diff --git a/RELEASING b/RELEASING
index 3a1c6ddb..0ee39bd1 100644
--- a/RELEASING
+++ b/RELEASING
@@ -60,6 +60,7 @@ Here are the steps to follow to create a new notmuch release:
the tag with your GPG key (asks for your GPG password, and you
may need to set GIT_COMMITTER_NAME and GIT_COMMITTER_EMAIL to match
your public-key's setting or this fails.)
+ * Push that tag
* Provide some text for the release announcement (see below).
If for some reason you lost this message, "make release-publish-message"
prints it for you.