You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: sig-release/annual-report-2022.md
+67-44Lines changed: 67 additions & 44 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,76 +2,98 @@
2
2
3
3
## Current initiatives
4
4
5
-
1. What work did the SIG do this year that should be highlighted?
5
+
SIG Release has a [roadmap](https://git.k8s.io/sig-release/roadmap.md) that captures high level initiatives that the SIG is working toward.
6
6
7
-
-
8
-
-
9
-
-
7
+
1. What work did the SIG do this year that should be highlighted?
8
+
-[Migrated deb/rpm package building into release process to reduce Google Build Admin involvement in releases](https://github.com/kubernetes/release/issues/2737)
9
+
- Proof-of-concept of using OpenSUSE Build Service to build and publish packages using community infrastructure. Reflected in updates to [1731 - Publishing Kubernetes packages on community infrastructure](https://github.com/kubernetes/enhancements/tree/master/keps/sig-release/1731-publishing-packages). See [biweekly meeting from 18 October 2022](https://youtu.be/8l8X3vSAJAw?t=787) for a good overview.
10
+
- We released [Kubernetes 1.24](https://github.com/kubernetes/sig-release/tree/master/releases/release-1.24), [Kubernetes 1.25](https://github.com/kubernetes/sig-release/tree/master/releases/release-1.25), and [Kubernetes 1.26](https://github.com/kubernetes/sig-release/tree/master/releases/release-1.26) in 2022.
11
+
- We did extensive work on the image promotion tooling to support the k8s.gcr.io -> registry.k8s.io migration. This involved several tactical PRs to fix the tooling and adapt to the increased number of registries. We identified work for 2023 to further improve the image promotion tooling.
12
+
- Migrated enhancement tracking from Google Sheets to [Github Project board in 1.26 Release](https://github.com/orgs/kubernetes/projects/98).
10
13
11
14
2. What initiatives are you working on that aren't being tracked in KEPs?
12
15
13
-
-
14
-
-
15
-
-
16
-
17
-
16
+
-[Donation of a new project for SLSA Attestation](https://github.com/kubernetes-sigs/tejolote)
17
+
- We begun work on a new process for onboarding Release Manager Associates and a ladder for becoming a full Release Manager.
18
18
19
19
3. KEP work in 2022 (v1.24, v1.25, v1.26):
20
-
- alpha:
21
-
-[3000 - Artifact Distribution Policy](https://github.com/kubernetes/enhancements/tree/master/keps/sig-release/3000-artifact-distribution) - v1.24
1. What areas and/or subprojects does your group need the most help with?
29
-
Any areas with 2 or fewer OWNERs? (link to more details)
30
-
31
-
-
32
-
-
33
-
-
34
-
28
+
Both subprojects, Release Team and Release Engineering, have a pipeline of interested individuals. In the release engineering subproject, we are tracking a number of larger initiatives, detailed in the KEP section. These larger efforts are where we could use the most help. The easiest way to identify what areas need help would be to use the individual KEPs as tracking. We have also labeled some things as good first issues.
29
+
35
30
2. What metrics/community health stats does your group care about and/or measure?
36
31
37
-
-
38
-
-
39
-
-
32
+
Some data tracking efforts that SIG Release performs include monitoring release team applications,
33
+
release manager activities and code commits to ensure timely release cuts in our repos.
34
+
35
+
In support of better understanding the diversity of the release team, [kubernetes-sigs/release-team-shadow-stats](https://github.com/kubernetes-sigs/release-team-shadow-stats) was begun to provide better reporting and visibility on release team metrics. For our [KubeCon EU SIG update](https://www.youtube.com/watch?v=qhQYu077zZU), we also presented a historical breakdown of the location of release team members and the geographic distribution of the release teams.
40
36
41
37
3. Does your [CONTRIBUTING.md] help **new** contributors engage with your group specifically by pointing
42
38
to activities or programs that provide useful context or allow easy participation?
43
39
44
-
-
40
+
- The [sig-release CONTRIBUTING.md](https://github.com/kubernetes/sig-release/blob/master/CONTRIBUTING.md) could be updated to provivde more specific information regarding how to participate in both subprojects. An [issue](https://github.com/kubernetes/sig-release/issues/2200) was opened in [kuberentes/sig-release](https://github.com/kubernetes/sig-release) and an [issue](https://github.com/kubernetes/release/issues/2980) was created in [kuberentes/release](https://github.com/kubernetes/release) to update this to collect information and make it more discoverable.
45
41
46
42
4. If your group has special training, requirements for reviewers/approvers, or processes beyond the general [contributor guide],
47
43
does your [CONTRIBUTING.md] document those to help **existing** contributors grow throughout the [contributor ladder]?
48
44
49
-
-
45
+
We have a lot of information, including detailed role handbooks for both subprojects:
However, these are not linked directly from CONTRIBUTING.md. We will use the [issue above](https://github.com/kubernetes/sig-release/issues/2200) to improve the discoverability of these.
51
+
50
52
51
53
5. Does the group have contributors from multiple companies/affiliations?
52
54
53
-
-
55
+
- Yes. Based on the last year of data from [dev stats](https://k8s.devstats.cncf.io/d/55/company-prs-in-repository-groups?orgId=1&var-period_name=Last%20year&var-repogroups=SIG%20Release&var-repos=All&var-companies=All&var-countries=All) we have had contributions from the following companies over the last year:
56
+
- Red Hat Inc,
57
+
- Chainguard Inc,
58
+
- Intel Corporation
59
+
- Liquid Reply
60
+
- Kubermatic GmbH
61
+
- Google LLC
62
+
- Microsoft Corporation
63
+
- Cisco
64
+
- Amazon
65
+
- VMware Inc
66
+
- SUSE LLC
67
+
- International Business Machines
68
+
- Jetstack LTD
69
+
- Mesosphere
70
+
- Mastercard International Incorporated
71
+
- DaoCloud Network Technology Co. Ltd.
72
+
- Oracle America Inc.
73
+
- Rackspace
74
+
- NEC Corporation
75
+
76
+
This data reflects company information in terms of PRs. We also have had contributions from individuals that have no company affiliation and several individuals from the CNCF.
77
+
In addition to code contributions, the release teams during 2022 were staffed by individuals from a wide range of corporations, as well as students and other independent individuals. These contributions are not all reflected by the devstats query above, but are important to recognize.
54
78
55
79
6. Are there ways end users/companies can contribute that they currently are not?
56
80
If one of those ways is more full time support, what would they work on and why?
57
81
58
-
-
59
-
-
60
-
82
+
- The release tooling is currently supported by the core of the Release Engineering team. There are opportunities for end users and Kubernetes distributors to support the maintenance of the tooling within our repositories, including the `bom` tool. Contributing to these tools would also be a good way to grow in SIG Release and join the Release Manager Associate program.
83
+
61
84
## Membership
62
85
63
-
- Primary slack channel member count:
64
-
- Primary mailing list member count:
65
-
- Primary meeting attendee count (estimated, if needed):
66
-
- Primary meeting participant count (estimated, if needed):
67
-
- Unique reviewers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files -->
68
-
- Unique approvers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files -->
86
+
The following stats are accurate as of March 15th, 2023. Numbers were pulled from Slack, the mailing list, and [kubernetes/release](https://github.com/kubernetes/release), the primary repository for Release Engineering tooling.
69
87
70
-
Include any other ways you measure group membership
0 commit comments