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
+69-40Lines changed: 69 additions & 40 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,77 +2,105 @@
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://github.com/kubernetes/sig-release/blob/master/roadmap.md) that captures high level initiatives that the SIG is working toward, with specific information captured in our [project board](https://github.com/orgs/kubernetes/projects/30).
6
6
7
-
-
8
-
-
9
-
-
7
+
1. What work did the SIG do this year that should be highlighted?
8
+
-[Migrated most of 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
+
-[Signing of Release Files](https://github.com/kubernetes/release/pull/2742).
10
11
11
12
2. What initiatives are you working on that aren't being tracked in KEPs?
12
13
13
-
-
14
-
-
15
-
-
16
-
17
-
14
+
-[Donation of a new project for SLSA Attestation](https://github.com/kubernetes-sigs/tejolote)
15
+
- We begun work on a new process for onboarding release manager associates and a ladder for becoming a full release manager.
18
16
19
17
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
2. What metrics/community health stats does your group care about and/or measure?
36
37
37
-
-
38
-
-
39
-
-
38
+
Some data tracking efforts that SIG Release performs include monitoring release team applications,
39
+
release manager activities and code commits to ensure timely release cuts in our repos.
40
+
41
+
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, we also presented a historical breakdown of the location of release team members and the geographic distribution of the release teams.
40
42
41
43
3. Does your [CONTRIBUTING.md] help **new** contributors engage with your group specifically by pointing
42
44
to activities or programs that provide useful context or allow easy participation?
43
45
44
-
-
46
+
- 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
47
46
48
4. If your group has special training, requirements for reviewers/approvers, or processes beyond the general [contributor guide],
47
49
does your [CONTRIBUTING.md] document those to help **existing** contributors grow throughout the [contributor ladder]?
48
50
51
+
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.
57
+
58
+
52
59
5. Does the group have contributors from multiple companies/affiliations?
53
60
54
-
-
61
+
- 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:
62
+
- Red Hat Inc,
63
+
- Chainguard Inc,
64
+
- Intel Corporation
65
+
- Liquid Reply
66
+
- Kubermatic GmbH
67
+
- Google LLC
68
+
- Microsoft Corporation
69
+
- Cisco
70
+
- Amazon
71
+
- VMware Inc
72
+
- SUSE LLC
73
+
- International Business Machines
74
+
- Jetstack LTD
75
+
- Mesosphere
76
+
- Mastercard International Incorported
77
+
- DaoCloud Network Technology Co. Ltd.
78
+
- Oracle America Inc.
79
+
- Rackspace
80
+
- NEC Corporation
81
+
82
+
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.
83
+
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 independant individuals. These contributions are not all reflected by the devstats query above, but are important to recognize.
55
84
56
85
6. Are there ways end users/companies can contribute that they currently are not?
57
86
If one of those ways is more full time support, what would they work on and why?
58
87
59
-
-
60
-
-
88
+
- 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 maintaince of the tooling within our repositories, including the `bom` tool. Additionally, vendor companies that build and distribute their own Kubernetes releases could provide more support to SIG Release, specifically Release Engineering, in order to grow contributors that could help with important tasks like Go verison updates.
89
+
61
90
62
91
## Membership
63
92
64
-
- Primary slack channel member count:
65
-
- Primary mailing list member count:
66
-
- Primary meeting attendee count (estimated, if needed):
67
-
- Primary meeting participant count (estimated, if needed):
68
-
- Unique reviewers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files -->
69
-
- Unique approvers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files -->
93
+
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.
70
94
71
-
Include any other ways you measure group membership
0 commit comments