Releasing Krakens & Other Cephalopods Into the Wild
summary
Describes how Ceph backport releases are prepared and tested across its ~18‑month release cycle and two active release branches, detailing the process and testing steps used to produce downstream point releases. Covers how and where contributors can submit and track bug fixes to get them backported, and outlines expected future directions for the release process.
AI-written summary · about
chapters (8)
- 0:00Start
- 2:46Timeline of Major features
- 7:15Release Cadence: Past
- 10:08Release Type: Release Candidates
- 10:38Release Type: Stable Releases
- 12:14Upgrade Notes
- 15:54Bug Reports & Fixes
- 17:43Getting started
related talks
09mKeynote: Welcome & State of the Cephalopod Part I
27mMechanics of releasing a large project: Leadership learnings from Kubernetes releases
24mThe Ceph Community: A Driving Force for Project Evolution
06mParticipating In The Kubernetes Release Team
36mGuidelines for Achieving Project Release Maturity
29mCeph and the future of Open Source Storage
29mCeph's journey at SUSE
27mKEPs: Evolving Kubernetes at the Speed of Trust