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·
summary
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
chapters (9)
- 0:00Start
- 2:02What is a release?
- 3:09Stages of a Release
- 15:11Preparing the release
- 17:46Building the release
- 18:23What about security releases?
- 19:57Preparing a security release
- 21:13Who works on the security fixes?
- 24:28How do security patches work on a public code base?
related talks
33mNode.js Versions - How Do They Work?
29mNode.js: The New and the Experimental
41mHow the npm CLI Team Manages (Almost) 100 Open Source Projects
40mResponsible Use of Node.js & Open Source Software Utilizing Best Practices at an...
27mNode.js Core Support for The Enterprise
26mThe State of Node.js Core
29mThe State of Node.js Core
29mHow Did We Get Here
