From c160eb836d45a517073d0a9db8c0dc456f9ef077 Mon Sep 17 00:00:00 2001 From: Matthew Mosesohn Date: Mon, 23 Jan 2017 17:44:46 +0300 Subject: [PATCH] Add release process document Change-Id: I12ca5fb7503a36be68a5e7db64b186ab321cb648 --- RELEASE.rst | 40 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 RELEASE.rst diff --git a/RELEASE.rst b/RELEASE.rst new file mode 100644 index 0000000..9ec0df0 --- /dev/null +++ b/RELEASE.rst @@ -0,0 +1,40 @@ +Fuel CCP Installer release process +---------------------------------- + +In order to tag a release of MCP Installer, the following items must be set: +* Pinned Fuel-devops version +* Pinned Kargo commit +* Pinned Docker version +* Pinned Calico version +* Pinned Kubernetes hyperkube image +* Pinned etcd version +* Pinned Ansible version + +List of items to check off before tagging release: +* CI passes (pep8, pytest, docs, and functional test) +* HA destructive test: + * disable first master, restart kubelet on all nodes, check kubectl get nodes, + restart first master, check kubectl get nodes +* QA signoff +* fuel-devops version +* test coverage is green +* CCP team signoff +* Fuel-ccp deployment succeeds and contains no blocker bugs + +Estimated timeline: 3 days to propose release and obtain signoff. + +Technical Details +^^^^^^^^^^^^^^^^^ + +Master branch of fuel-ccp-installer will principally point to “master” commit +of Kargo, except during release time. + +Release manager will create a commit to fuel-ccp-installer, pinning +KARGO_COMMIT to either a tagged release of Kargo or a specific commit. + +After all signoffs are obtained, the commit will be merged. + +Release manager will create a tag in Gerrit for the new release. + +Release manager creates another commit to un-pin KARGO_COMMIT back to “master” +gitref.