Skip to content

Latest commit

 

History

History
145 lines (101 loc) · 9.39 KB

annual-report-2022.md

File metadata and controls

145 lines (101 loc) · 9.39 KB

2022 Annual Report: SIG Release

Current initiatives

SIG Release has a roadmap that captures high level initiatives that the SIG is working toward, with specific information captured in our project board.

  1. What work did the SIG do this year that should be highlighted?

  2. What initiatives are you working on that aren't being tracked in KEPs?

  3. KEP work in 2022 (v1.24, v1.25, v1.26):

Project health

  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)

  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.

    In support of better understanding the diversity of the release team, 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.

  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?

  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?

    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 to improve the discoverability of these.

  5. Does the group have contributors from multiple companies/affiliations?

    • Yes. Based on the last year of data from dev stats we have had contributions from the following companies over the last year:
      • Red Hat Inc,
      • Chainguard Inc,
      • Intel Corporation
      • Liquid Reply
      • Kubermatic GmbH
      • Google LLC
      • Microsoft Corporation
      • Cisco
      • Amazon
      • VMware Inc
      • SUSE LLC
      • International Business Machines
      • Jetstack LTD
      • Mesosphere
      • Mastercard International Incorported
      • DaoCloud Network Technology Co. Ltd.
      • Oracle America Inc.
      • Rackspace
      • NEC Corporation

    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. 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.

  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?

    • 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.

Membership

The following stats are accurate as of March 15th, 2023. Numbers were pulled from Slack, the mailing list, and kubernetes/release, the primary repository for Release Engineering tooling.

  • Primary slack channel member count: 2980
  • Primary mailing list member count: 605
  • Primary meeting attendee count (estimated, if needed): 15 (SIG Release BiWeekly), 20 (Release Team)
  • Primary meeting participant count (estimated, if needed): 10 (SIG Release BiWeekly), 20 (Release Team)
  • Unique reviewers for SIG-owned packages: 11
  • Unique approvers for SIG-owned packages: 9

Subprojects

Retired in 2022:

  • kubernetes/repo-infra

Continuing:

  • Release Engineering
  • Release Team
  • SIG Release Process Documentation

Working groups

Continuing:

  • Reliability

Operational

Operational tasks in sig-governance.md: