Merge pull request #11 from caseydavenport/fix-release

Fix release

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,34 @@
+<!--- Provide a general summary of the issue in the Title above -->
+
+## Expected Behavior
+<!--- If you're describing a bug, tell us what should happen -->
+<!--- If you're suggesting a change/improvement, tell us how it should work -->
+
+## Current Behavior
+<!--- If describing a bug, tell us what happens instead of the expected behavior -->
+<!--- If suggesting a change/improvement, explain the difference from current behavior -->
+
+## Possible Solution
+<!--- Not obligatory, but suggest a fix/reason for the bug, -->
+<!--- or ideas how to implement the addition or change -->
+
+## Steps to Reproduce (for bugs)
+<!--- Provide a link to a live example, or an unambiguous set of steps to -->
+<!--- reproduce this bug. Include code to reproduce, if relevant -->
+1.
+2.
+3.
+4.
+
+## Context
+<!--- How has this issue affected you? What are you trying to accomplish? -->
+<!--- Providing context helps us come up with a solution that is most useful in the real world -->
+
+## Your Environment
+<!--- Include as many relevant details about the environment you experienced the bug in -->
+* CNI plugin version (e.g. `/opt/cni/bin/calico --version`):
+* Orchestrator version (e.g. kubernetes, mesos, rkt):
+* CNI config:
+* Operating System and version:
+* Link to your project (optional):
+

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,28 @@
+## Description
+<!-- A few sentences describing the overall goals of the pull request's commits.
+Please include
+- the type of fix - (e.g. bug fix, new feature, documentation)
+- some details on _why_ this PR should be merged
+- the details of the testing you've done on it (both manual and automated)
+- which components are affected by this PR
+- links to issues that this PR addresses
+-->
+
+
+
+## Todos
+- [ ] Tests
+- [ ] Documentation
+- [ ] Release note
+
+## Release Note
+<!-- Writing a release note:
+- By default, no release note action is required.
+- If you're unsure whether or not your PR needs a note, ask your reviewer for guidance.
+- If this PR requires a release note, update the block below to include a concise note describing
+  the change and any important impacts this PR may have.
+-->
+
+```release-note
+None required
+```

Makefile

@@ -53,7 +53,6 @@ comma := ,
 prefix_linux = $(addprefix linux/,$(strip $1))
 join_platforms = $(subst $(space),$(comma),$(call prefix_linux,$(strip $1)))
 
-
 # list of arches *not* to build when doing *-all
 #    until s390x works correctly
 EXCLUDEARCH ?= s390x
@@ -312,7 +311,7 @@ release-publish: release-prereqs
 	git push origin $(VERSION)
 
 	# Push images.
-	$(MAKE) push-all IMAGETAG=$(VERSION)
+	$(MAKE) push-all push-manifests push-non-manifests IMAGETAG=$(VERSION)
 
 	@echo "Finalize the GitHub release based on the pushed tag."
 	@echo ""
@@ -327,7 +326,7 @@ release-publish: release-prereqs
 # run this target for alpha / beta / release candidate builds, or patches to earlier Calico versions.
 ## Pushes `latest` release images. WARNING: Only run this for latest stable releases.
 release-publish-latest: release-prereqs
-	$(MAKE) push-all IMAGETAG=latest
+	$(MAKE) push-all push-manifests push-non-manifests IMAGETAG=latest
 
 # release-prereqs checks that the environment is configured properly to create a release.
 release-prereqs: