~/talk

The Life and Times of a Node.js Release

Talkat Open Source in Finance Forum New York 2022 · on Thursday, 2022-12-08· at 11:15· HALL 1, New York, NY, USA· [nodejs]
slides:none on file

Node.js maintains four supported release lines and does about 50 releases a year, with routine releases every six months and typical builds of ~100 commits but occasional 600–700 commits major rollups. Releases use a workflow that pulls labeled PRs via a CLI called Branch diff, cherry-picks to a staging branch, runs local builds and cross‑platform CI, bisects failures with git bisect, backports problematic changes, and for security patches runs a closed process led by a designated steward funded by Project Alpha Omega.

AI-written summary · about

  1. 0:00Start
  2. 2:02What is a release?
  3. 3:09Stages of a Release
  4. 15:11Preparing the release
  5. 17:46Building the release
  6. 18:23What about security releases?
  7. 19:57Preparing a security release
  8. 21:13Who works on the security fixes?
  9. 24:28How do security patches work on a public code base?
~/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.