From 77310cfb27c70e5de45cefa92fe90f5adfa9486d Mon Sep 17 00:00:00 2001 From: Stephen Augustus Date: Tue, 25 Jan 2022 15:43:22 -0500 Subject: sig-release/annual-2021: Add membership stats Signed-off-by: Stephen Augustus --- sig-release/annual-report-2021.md | 19 +++++++++++++------ 1 file changed, 13 insertions(+), 6 deletions(-) diff --git a/sig-release/annual-report-2021.md b/sig-release/annual-report-2021.md index 21e848ae..cd6f7e0e 100644 --- a/sig-release/annual-report-2021.md +++ b/sig-release/annual-report-2021.md @@ -71,12 +71,17 @@ In future, this will be generated from kubernetes/enhancements kep.yaml files ## Membership -- Primary slack channel member count: -- Primary mailing list member count: -- Primary meeting attendee count (estimated, if needed): -- Primary meeting participant count (estimated, if needed): -- Unique reviewers for SIG-owned packages: -- Unique approvers for SIG-owned packages: +Accurate of 2022-02-14. +Stats are primarily pulled from kubernetes/release, the primary repository for +Release Engineering tooling/work, which serves as a reasonable representation +of reviewers/approvers across SIG Release repositories. + +- Primary Slack channel member count: 2458 +- Primary mailing list member count: 501 +- Primary meeting attendee count (estimated, if needed): 20 +- Primary meeting participant count (estimated, if needed): 10 +- Unique reviewers for SIG-owned packages (from kubernetes/release): 24 +- Unique approvers for SIG-owned packages (from kubernetes/release): 7 Include any other ways you measure group membership @@ -140,4 +145,6 @@ Operational tasks in [sig-governance.md]: [sigs.yaml]: https://git.k8s.io/community/sigs.yaml [contributor guide]: https://git.k8s.io/community/contributors/guide/README.md [devel]: https://git.k8s.io/community/contributors/devel/README.md + + -- cgit v1.2.3 From a0f5cd644efe3e32480c4653b112b0351c9a67a1 Mon Sep 17 00:00:00 2001 From: Stephen Augustus Date: Mon, 14 Feb 2022 06:03:53 -0500 Subject: sig-release/annual-2021: Add contributor stats/docs Signed-off-by: Stephen Augustus --- sig-release/annual-report-2021.md | 23 +++++++++++++++++++++-- 1 file changed, 21 insertions(+), 2 deletions(-) diff --git a/sig-release/annual-report-2021.md b/sig-release/annual-report-2021.md index cd6f7e0e..89ab20dc 100644 --- a/sig-release/annual-report-2021.md +++ b/sig-release/annual-report-2021.md @@ -57,11 +57,30 @@ In future, this will be generated from kubernetes/enhancements kep.yaml files 4. If your group has special training, requirements for reviewers/approvers, or processes beyond the general [contributor guide], does your [CONTRIBUTING.md] document those to help **existing** contributors grow throughout the [contributor ladder]? - - + - [Release Team](https://github.com/kubernetes/sig-release/tree/master/release-team) + - [Release Engineering](https://github.com/kubernetes/sig-release/tree/master/release-engineering) 5. Does the group have contributors from multiple companies/affiliations? - - + - Yes, over the past two years, we've had contributors from the following companies (non-exhaustive, gathered from [here](https://k8s.devstats.cncf.io/d/55/company-prs-in-repository-groups?orgId=1&var-period_name=Last%202%20years&var-repogroups=SIG%20Release&var-repos=All&var-companies=All&var-countries=All)): + - Red Hat + - Cisco + - Chainguard + - Mattermost + - Apple + - SUSE + - VMware + - Upbound + - Google + - Jetstack + - Kubermatic + - IBM + - HashiCorp + - SAP + - HSBC + - Huawei + - Intel + - Autodesk 6. Are there ways end users/companies can contribute that they currently are not? If one of those ways is more full time support, what would they work on and why? -- cgit v1.2.3 From 89f072961ee80171a1cf9587eda53b167f06a572 Mon Sep 17 00:00:00 2001 From: Stephen Augustus Date: Mon, 14 Feb 2022 06:16:01 -0500 Subject: sig-release/annual-2021: Add subprojects/WGs and help-wanted areas Signed-off-by: Stephen Augustus --- sig-release/annual-report-2021.md | 49 +++++++++++++++++---------------------- 1 file changed, 21 insertions(+), 28 deletions(-) diff --git a/sig-release/annual-report-2021.md b/sig-release/annual-report-2021.md index 89ab20dc..7f3857da 100644 --- a/sig-release/annual-report-2021.md +++ b/sig-release/annual-report-2021.md @@ -39,9 +39,15 @@ In future, this will be generated from kubernetes/enhancements kep.yaml files 1. What areas and/or subprojects does your group need the most help with? Any areas with 2 or fewer OWNERs? (link to more details) - - - - - - + All of the following areas are reviewed by the Release Engineering + subproject, but we could always use more help here: + + - [kubernetes-sigs/bom](https://github.com/kubernetes-sigs/bom/blob/main/OWNERS) + - [kubernetes-sigs/downloadkubernetes](https://github.com/kubernetes-sigs/downloadkubernetes/blob/master/OWNERS) + - [kubernetes-sigs/mdtoc](https://github.com/kubernetes-sigs/mdtoc/blob/master/OWNERS) + - [kubernetes-sigs/release-notes](https://github.com/kubernetes-sigs/release-notes/blob/master/OWNERS) + - [kubernetes-sigs/zeitgeist](https://github.com/kubernetes-sigs/zeitgeist/blob/master/OWNERS) + - [kubernetes/repo-infra](https://github.com/kubernetes/repo-infra/blob/master/OWNERS) 2. What metrics/community health stats does your group care about and/or measure? @@ -106,41 +112,28 @@ Include any other ways you measure group membership ## Subprojects - - -New in $YYYY: -- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) -- +Retired in 2021: -Retired in $YYYY: -- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) -- +- [Licensing](https://git.k8s.io/community/sig-release#licensing) Continuing: -- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) -- + +- [Release Engineering](https://git.k8s.io/community/sig-release#release-engineering) +- [Release Team](https://git.k8s.io/community/sig-release#release-team) ## Working groups - +New in 2021: + +- [WG Reliability](https://git.k8s.io/community/wg-reliability/) ([2021 report](https://git.k8s.io/community/wg-reliability/annual-report-2021.md)) -New in $YYYY: -- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) -- +Retired in 2021: -Retired in $YYYY: -- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) -- +WG K8s Infra was converted into [SIG K8s Infra](https://git.k8s.io/community/sig-k8s-infra) in 2021. Continuing: -- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) -- + +- [WG Reliability](https://git.k8s.io/community/wg-reliability/) ([2021 report](https://git.k8s.io/community/wg-reliability/annual-report-2021.md)) ## Operational -- cgit v1.2.3 From d886594e2bbfbd0981d2b92bbeba16b534e8a2ac Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Adolfo=20Garc=C3=ADa=20Veytia=20=28Puerco=29?= Date: Mon, 14 Feb 2022 22:51:07 -0600 Subject: Add Release Engineering projects and link to KEPs MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit This commit adds to the document links to the release engineering subprojects KEPs, a description of the current efforts and a description of the auto fast forward project. Also, a link to the SIG Release kubecon talk is included. Signed-off-by: Adolfo García Veytia (Puerco) --- sig-release/annual-report-2021.md | 67 +++++++++++++++++++++++---------------- 1 file changed, 40 insertions(+), 27 deletions(-) diff --git a/sig-release/annual-report-2021.md b/sig-release/annual-report-2021.md index 7f3857da..bbec741d 100644 --- a/sig-release/annual-report-2021.md +++ b/sig-release/annual-report-2021.md @@ -2,19 +2,38 @@ ## Current initiatives -1. What work did the SIG do this year that should be highlighted? +### 1. What work did the SIG do this year that should be highlighted? - - - - - - +#### Release Engineering -2. What initiatives are you working on that aren't being tracked in KEPs? +After finalizing the rewrite of the release process from bash into golang, +the release engineering team has been focusing its efforts on two main +areas: - - - - - - + 1. Improving the release automation on two fronts: + 1. Adding new features, tests and checks to the release process which + were missing from the original anago (binary verification, CVE + disclosure, building from custom branches and repositories). + 1. Consolidating the codebases of new repositories which SIG Release + brought under its responsibility. The range of new repositories we + are consolidating go from critical projects (like the image promoter) + to less important repositories (like downloadkubernetes.com) + 1. Hardening the Kubernetes Supply Chain via key efforts: + 1. SBOM Generation + 1. SLSA 3 compliance + 1. Artifact signing + +#### Release Team -3. KEP work in 2021 (1.x, 1.y, 1.z): +### 2. What initiatives are you working on that aren't being tracked in KEPs? + +The most important change currently under development not tracked in a KEP is +the new automated branch forward. Tests are currently underway and we aim to +have automated forward of the release branch during code freeze by the 1.25 cycle. +[A recent announcement sent to the dev mailing list](https://groups.google.com/a/kubernetes.io/g/dev/c/qbHPJjUF3s8) +has more details about the plan. + +### 3. KEP work in 2021 (1.x, 1.y, 1.z): - - Stable - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable - - Beta - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta - Alpha - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha - - Pre-alpha - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) + - [KEP-2853 - Kubernetes repository branch rename](https://github.com/kubernetes/enhancements/blob/master/keps/sig-release/2853-k-core-branch-rename/README.md) - $milestone.stable + - [KEP-3027 - SLSA Level 3 Compliance in the Kubernetes Release Process](https://github.com/kubernetes/enhancements/blob/master/keps/sig-release/3027-slsa-compliance/README.md) - $milestone.stable + - [KEP-3031: Signing release artifacts](https://github.com/kubernetes/enhancements/blob/master/keps/sig-release/3031-signing-release-artifacts/README.mdhttps://git.k8s.io/community/$link/README.md) - $milestone.beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta ## Project health @@ -139,16 +152,16 @@ Continuing: Operational tasks in [sig-governance.md]: -- [ ] [README.md] reviewed for accuracy and updated if needed -- [ ] [CONTRIBUTING.md] reviewed for accuracy and updated if needed +- [x] [README.md] reviewed for accuracy and updated if needed +- [x] [CONTRIBUTING.md] reviewed for accuracy and updated if needed (or created if missing and your contributor steps and experience are different or more in-depth than the documentation listed in the general [contributor guide] and [devel] folder.) -- [ ] Subprojects list and linked OWNERS files in [sigs.yaml] reviewed for accuracy and updated if needed -- [ ] SIG leaders (chairs, tech leads, and subproject owners) in [sigs.yaml] are accurate and active, and updated if needed -- [ ] Meeting notes and recordings for 2021 are linked from [README.md] and updated/uploaded if needed -- [ ] Did you have community-wide updates in 2021 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: - - - - +- [x] Subprojects list and linked OWNERS files in [sigs.yaml] reviewed for accuracy and updated if needed +- [x] SIG leaders (chairs, tech leads, and subproject owners) in [sigs.yaml] are accurate and active, and updated if needed +- [x] Meeting notes and recordings for 2021 are linked from [README.md] and updated/uploaded if needed +- [x] Did you have community-wide updates in 2021 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: + + - [Hardening the Kubernetes Software Supply Chain Through Better Transparency](https://www.youtube.com/watch?v=W6hUXv66rRc) KubeCon + CloudNativeCon NA 2021 [CONTRIBUTING.md]: https://git.k8s.io/community/sig-release/CONTRIBUTING.md [contributor ladder]: https://git.k8s.io/community/community-membership.md -- cgit v1.2.3 From d6dcf4c1eb4c615d884e555a94faec3b0c3302ce Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Adolfo=20Garc=C3=ADa=20Veytia=20=28Puerco=29?= Date: Mon, 28 Mar 2022 19:32:33 -0600 Subject: Complete final sections MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Adolfo García Veytia (Puerco) --- sig-release/annual-report-2021.md | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/sig-release/annual-report-2021.md b/sig-release/annual-report-2021.md index bbec741d..f4cc6996 100644 --- a/sig-release/annual-report-2021.md +++ b/sig-release/annual-report-2021.md @@ -64,14 +64,13 @@ In future, this will be generated from kubernetes/enhancements kep.yaml files 2. What metrics/community health stats does your group care about and/or measure? - - - - - - + Some data tracking efforts that SIG Release performs include monitoring release team applications, + release manager activities and code commits to ensure timely release cuts in our repos. 3. Does your [CONTRIBUTING.md] help **new** contributors engage with your group specifically by pointing to activities or programs that provide useful context or allow easy participation? - - + - The `CONTRIBUTING.md` was recently revamped and includes a Getting Started section with links to mentoring opportunities. 4. If your group has special training, requirements for reviewers/approvers, or processes beyond the general [contributor guide], does your [CONTRIBUTING.md] document those to help **existing** contributors grow throughout the [contributor ladder]? @@ -104,8 +103,8 @@ In future, this will be generated from kubernetes/enhancements kep.yaml files 6. Are there ways end users/companies can contribute that they currently are not? If one of those ways is more full time support, what would they work on and why? - - - - + - We've been considering offering internships to help us round the rough edges + in some repositories such as the Kuebrnetes SBOM Tool. ## Membership -- cgit v1.2.3