Makefile: Make the "make release" target push the new tag.

Otherwise I'm sure I'll always forget to push it.
This commit is contained in:
Carl Worth 2010-04-05 15:56:23 -07:00
parent 322eaebabe
commit 1b0830b31c
2 changed files with 2 additions and 0 deletions

View file

@ -81,6 +81,7 @@ release: release-verify-newer $(TAR_FILE) $(SHA1_FILE) $(GPG_FILE)
mv $(TAR_FILE) $(SHA1_FILE) $(GPG_FILE) releases 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)" 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 tag -s -m "$(PACKAGE) $(VERSION) release" $(VERSION)
git push origin $(VERSION)
.PHONY: release-verify-version .PHONY: release-verify-version
release-verify-version: release-verify-version:

View file

@ -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 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 may need to set GIT_COMMITTER_NAME and GIT_COMMITTER_EMAIL to match
your public-key's setting or this fails.) your public-key's setting or this fails.)
* Push that tag
* Provide some text for the release announcement (see below). * Provide some text for the release announcement (see below).
If for some reason you lost this message, "make release-publish-message" If for some reason you lost this message, "make release-publish-message"
prints it for you. prints it for you.