From 8cd51d9adce2802d80b723536258adc07ee879d3 Mon Sep 17 00:00:00 2001 From: "Lubomir I. Ivanov" Date: Thu, 28 Jan 2021 23:50:52 +0200 Subject: [PATCH 1/2] update OWNERS file --- OWNERS | 20 ++++++++++++++------ 1 file changed, 14 insertions(+), 6 deletions(-) diff --git a/OWNERS b/OWNERS index 038c181..2b40b17 100644 --- a/OWNERS +++ b/OWNERS @@ -1,9 +1,17 @@ # See the OWNERS docs at https://go.k8s.io/owners approvers: - - luxas - - timothysc - - fabriziopandini - - neolit123 - - rosti - - ereslibre +- fabriziopandini +- neolit123 +- SataQiu +reviewers: +- KentaTada +- odinuge +emeritus_approvers: +- luxas +- timothysc +- rosti +- ereslibre +labels: +- sig/cluster-lifecycle +- sig/node From f748689b592232635d715fb1627610f106942830 Mon Sep 17 00:00:00 2001 From: "Lubomir I. Ivanov" Date: Fri, 29 Jan 2021 00:15:16 +0200 Subject: [PATCH 2/2] README.md: add section about creating releases --- README.md | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/README.md b/README.md index c47e75d..67a0200 100644 --- a/README.md +++ b/README.md @@ -2,6 +2,27 @@ A set of system-oriented validators for kubeadm preflight checks. +## Creating releases + +To prepare a release of this library please follow this guide: +- The main branch should always contain WIP commits planned for the upcoming release. +- Always create a new branch for MAJOR and MINOR releases. This allows backporting changes. +- Release branch names should be in the format `release-MAJOR.MINOR` (without a `v` prefix). +- Only non-breaking bug fixes can be done in a PATCH release. +- New features must not be added in PATCH releases. +- Breaking changes must be added in a MAJOR release. +- Pushing releases requires write access. To obtain that you must be part of +the [`system-validator-maintainers` team](http://git.k8s.io/org/config/kubernetes/sig-cluster-lifecycle/teams.yaml). + +For vendoring the new release in kubernetes/kubernetes you can use its `pin-dependency.sh` script. + +Example: +```bash +./hack/pin-dependency.sh k8s.io/system-validators +``` + +And then PR the changes. + ## Community, discussion, contribution, and support Learn how to engage with the Kubernetes community on the [community page](http://kubernetes.io/community/).