~/talk

SIG Release Deep Dive

links:none on file
links:none on file
slides:none on file

SIG Release explains how the project keeps a “covenant of trust” by running a disciplined release pipeline: quarterly three-month cadence releases, a defined release lead/branch manager rotation, and a heavy push to automation. Builds move from Onaga into cloud-based GCB_MGR (Google Container Builder Manager) and CI runs on prow/testgrid; 117 people coordinate triage, docs, and cut binaries. The last month gets intense (daily meetings, ~5–10 hours/week for leads); many manual steps still remain despite the tooling.

AI-written summary · about

  1. 0:00Start
  2. 0:33Overview
  3. 3:01Provide Opportunities for New Contributors
  4. 3:26Release Policy
  5. 5:02Summary of the Release Process
  6. 16:04Google Container Builder Manager
  7. 22:59Branch Diff
  8. 25:00What Is the Time Commitment for a Release Lead
  9. 27:19Dashboards
  10. 34:41What Are the Things That Software Engineers Could Do To Improve this Process
  11. 35:28Scalability Testing
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.