How we changed openSUSE developement
summary
Claim: openSUSE solves the rolling vs stable tradeoff by shipping two cooperating distributions, a fast tumbleweed rolling release and a conservative leap release based on sources from suse linux enterprise. Build and test automation actually makes it work: packages are built in the open build service (OBS), validated in staging with dependency rebuilds, and exercised by open QA before merging. Releases happen multiple times per week (typical: five releases, two kernels, ~300 packages), leap gets yearly service packs and multi‑year core support.
AI-written summary · about
chapters (11)
- 0:00Start
- 6:13Distribution for bleeding edge crazies
- 6:31History
- 8:02What makes Tumbleweed working
- 14:14How Factory used to work
- 15:54How Factory works now
- 20:30Forces at play after Tumbleweed
- 20:45Distribution for boring grandpas
- 22:29How can we help each other
- 22:52How it works
- 29:34Translations via weblate
related talks
10mWalking the Thin Line
38mopenSUSE on the Mainframe
41mBecause Security Matters: Securing Your Open Sourc...
21mCommunities, Enterprises and All the Rest
42mBeyond the Code: Evolving OpenSearch's Release Process for...
15mAfter 25 Years, Where Are We?
08mBroadening the Base: Increasing Options for Deploying Cloud Foundry - Troy Topnik, SUSE
33mDeveloping RHEL open source way