BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.com//txlf2026//talk//UMCX99
BEGIN:VTIMEZONE
TZID:US/Central
BEGIN:STANDARD
DTSTART:20251107T000000
TZNAME:CST
TZOFFSETFROM:-0600
TZOFFSETTO:-0600
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20260308T030000
RDATE:20270314T030000
TZNAME:CDT
TZOFFSETFROM:-0600
TZOFFSETTO:-0500
END:DAYLIGHT
BEGIN:STANDARD
DTSTART:20261101T020000
TZNAME:CST
TZOFFSETFROM:-0500
TZOFFSETTO:-0600
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
SUMMARY:Why isn't my distribution shipping the latest version yet? - Autum
 n Nash
DTSTART;TZID=US/Central:20261107T160000
DTEND;TZID=US/Central:20261107T165000
DTSTAMP:20260930T133615Z
UID:pretalx-txlf2026-UMCX99@pretalx.com
DESCRIPTION:It's a question almost every Linux user\, developer\, or platf
 orm engineer has asked. Behind that seemingly simple question lies one of 
 the most important\, and least understood\, engineering tradeoffs.\n\nEver
 y application\, container\, and cloud workload depends on software that ha
 s been packaged\, tested\, maintained\, and released by a Linux distributi
 on. Yet most engineers never see the work required to transform upstream s
 ource code into software that is stable enough to trust in production. Eve
 ry package update must balance security\, compatibility\, regression risk
 \, reproducibility\, dependency management\, architecture support\, releas
 e criteria\, and long-term maintenance. What appears to be "slow" is often
  deliberate engineering designed to reduce risk for millions of users.\n\n
 In this session\, we'll follow a package from its upstream release to its 
 arrival in a Linux distribution\, exposing the decisions\, tradeoffs\, and
  engineering practices that happen along the way. We'll explore why mainta
 iners backport fixes instead of always upgrading\, why regression preventi
 on often outweighs feature velocity\, and how release engineering quietly 
 protects the software ecosystem that nearly every modern application depen
 ds on.\n\nWhether you build applications\, manage infrastructure\, contrib
 ute to open source\, or operate production systems\, you'll leave with a p
 ractical mental model for understanding how Linux software reaches your sy
 stems\, and a deeper appreciation for the engineering judgment required to
  balance innovation\, stability\, and trust at scale.\n\nLinux distributio
 ns aren't slow. They're deliberate\, because reliability is built one engi
 neering decision at a time.
LOCATION:Balcones
URL:https://pretalx.com/txlf2026/talk/UMCX99/
END:VEVENT
END:VCALENDAR