From 2d796ffbc2688062f47cbc51537838c93d63a819 Mon Sep 17 00:00:00 2001 From: maelk Date: Wed, 13 May 2020 15:02:21 +0300 Subject: [PATCH] Update release guidelines --- Makefile | 4 ++-- VERSIONING.md | 4 ---- docs/releasing.md | 5 +++-- 3 files changed, 5 insertions(+), 8 deletions(-) diff --git a/Makefile b/Makefile index dcad1780..fdd1fe22 100644 --- a/Makefile +++ b/Makefile @@ -51,7 +51,7 @@ RELEASE_NOTES := $(TOOLS_DIR)/$(RELEASE_NOTES_BIN) REGISTRY ?= quay.io/metal3-io STAGING_REGISTRY := quay.io/metal3-io PROD_REGISTRY := quay.io/metal3-io -IMAGE_NAME ?= ipam +IMAGE_NAME ?= ip-address-manager CONTROLLER_IMG ?= $(REGISTRY)/$(IMAGE_NAME) TAG ?= v1alpha1 ARCH ?= amd64 @@ -305,7 +305,7 @@ release: clean-release ## Builds and push container images using the latest git .PHONY: release-manifests release-manifests: $(RELEASE_DIR) ## Builds the manifests to publish with a release - kustomize build config > $(RELEASE_DIR)/infrastructure-components.yaml + kustomize build config > $(RELEASE_DIR)/ipam-components.yaml .PHONY: release-binaries release-binaries: ## Builds the binaries to publish with a release diff --git a/VERSIONING.md b/VERSIONING.md index 1faad20b..6822a8f5 100644 --- a/VERSIONING.md +++ b/VERSIONING.md @@ -9,10 +9,6 @@ as we try to follow closely the release process - We follow [Semantic Versioning (semver)](https://semver.org/). -- We try to follow Cluster API release cadence -- The cadence is subject to change if necessary, refer to the - [Milestones](https://github.com/kubernetes-sigs/cluster-api/milestones) page - for up-to-date information. - The _master_ branch is where development happens, this might include breaking changes. - The _release-X_ branches contain stable, backward compatible code. A new diff --git a/docs/releasing.md b/docs/releasing.md index 48f7cd91..2fe1c544 100644 --- a/docs/releasing.md +++ b/docs/releasing.md @@ -23,13 +23,14 @@ You must have docker installed. ### Expected artifacts -1. A container image of the shared cluster-api-provider-metal3 manager +1. A container image of the ip-address-manager manager 1. A git tag +1. A deployment file : ipam-components.yaml ### Artifact locations 1. The container image is found in the registry `quay.io/metal3-io` with an image - name of `ipam` and a tag that matches the release + name of `ip-address-manager` and a tag that matches the release version. The image is automatically built once the release has been created. ## Creating a release for IPAM