BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//cfp.all-systems-go.io//all-systems-go-2024//SQLXTG
BEGIN:VTIMEZONE
TZID:CET
BEGIN:STANDARD
DTSTART:20001029T040000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000326T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-all-systems-go-2024-7APG3H@cfp.all-systems-go.io
DTSTART;TZID=CET:20240926T122000
DTEND;TZID=CET:20240926T130000
DESCRIPTION:How do you continually test and release new versions of systemd
  with confidence? Also\, once released\, how do you monitor PID 1 itself a
 nd your PID 1 usage across your server fleet? This talk dives into Meta’
 s way of answering these questions so we can minimize the risk of breaking
  changes and fun each systemd release brings us. Some of the technology in
  the talk is OSS\, so you too\, can join in on the fun knowing how your sy
 stemd usage is across your own infrastructure!
DTSTAMP:20260315T024651Z
LOCATION:Main Hall
SUMMARY:What's your PID 1 up to? - Cooper Ry Lees
URL:https://cfp.all-systems-go.io/all-systems-go-2024/talk/7APG3H/
END:VEVENT
END:VCALENDAR