13:00:21 <bcotton_> #startmeeting FPgM office hours
13:00:22 <zodbot> Meeting started Wed Apr 28 13:00:21 2021 UTC.
13:00:22 <zodbot> This meeting is logged and archived in a public location.
13:00:22 <zodbot> The chair is bcotton_. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:00:22 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
13:00:22 <zodbot> The meeting name has been set to 'fpgm_office_hours'
13:00:23 <bcotton_> #info This is an open floor meeting to discuss anything program management related (elections, changes, schedule, etc)
13:00:29 <bcotton_> #topic Announcements
13:00:36 <bcotton_> #info The Fedora Social Hour is tomorrow: https://element.io/app/#/room/#fedora-social-hour:matrix.org
13:00:43 <bcotton_> #info Fedora Linux 34 was released yesterday
13:00:44 <bcotton_> #info Fedora Linux 32 will reach end of life on Tuesday 25 May.
13:00:47 <bcotton_> #info Join us at the Fedora Linux 34 Release Party Friday and Saturday: https://hopin.com/events/fedora-linux-34-release-party
13:00:53 <bcotton_> #help The Fedora Podcast needs your help: https://communityblog.fedoraproject.org/the-fedora-podcast-is-back-but-it-needs-your-help/
13:01:20 <bcotton_> #info F34 election nominations are open through 12 May https://communityblog.fedoraproject.org/f34-elections-nominations-now-open/
13:01:24 <bcotton_> #topic Open floor
13:02:26 <Southern_Gentlem> bcotton_, i am hearing people complaining about the amount of zero day updates with f34
13:02:40 <Southern_Gentlem> i know there is not much we can do about it
13:02:54 <bcotton_> that's true :-)
13:04:04 <bcotton_> other than getting people to fix all their bugs before the freeze
13:04:21 <Southern_Gentlem> but 534M (25%+ 2G iso) of updates is pushing things a bit
13:06:30 <Southern_Gentlem> just and i know most of the maintainers are volunteer
13:10:08 <bcotton_> it's a hard problem
13:11:18 <bcotton_> i'm not sure how we'd solve it without either sacrificing QA or artificially spreading out updates across a few days
13:25:46 <bcotton_> Southern_Gentlem: do you happen to have historical data for the volume of 0-day updates? it would be interesting to track that over time and see what it looks like, but i'm not aware we keep that officially anywhere, and i don't we can simulate it
13:25:57 <bcotton_> (e.g. by installing an old iso)
13:44:49 <Southern_Gentlem> bcotton it has been steadily growing over the years
13:46:14 <Southern_Gentlem> started out at 50M then went to 150, then for years it was 200-350, last couple of releases it has grown to 500+
13:46:29 <Southern_Gentlem> all that is from memory
13:46:54 <Southern_Gentlem> never documented it
13:47:30 <Southern_Gentlem> thats is size in MB not the # of updates
13:47:37 <bcotton_> right
13:48:24 <Southern_Gentlem> used to be i wouldnt think about creating respins until we got to 350MB of updates for the release isos
13:48:41 <Southern_Gentlem> which worked out to be aoruns 1 month after the release
13:48:48 <Southern_Gentlem> around
13:49:43 <bcotton_> i suppose it's worth a thread on the devel list if you're interested. although i'm not sure how much will come of the discussion
13:49:56 <Southern_Gentlem> just something to keep in mind
13:50:47 <Southern_Gentlem> would be interesting to start seeing if there are certain packages that happen each release
13:55:11 <bcotton_> for sure. the only bummer is it'll take a few years to start seeing patterns
13:55:23 <bcotton_> but the sooner we start, the sooner we have it
13:55:34 <bcotton_> i'll see if i can come up a good way to track it
13:55:36 <Southern_Gentlem> https://paste.centos.org/view/raw/8b3d652d
13:55:49 <bcotton_> thanks!
13:56:25 <Southern_Gentlem> well i see the Big one there is libreoffice
13:58:06 <Southern_Gentlem> maybe we need to grant certain programs like libreoffice and firefox freeze exception so we can pull them in to the release isos
13:58:51 <bcotton_> yeah. that might help. so long as it's not too long before so that QA has time to validate the release blockign behavior of both of those
13:58:56 <bcotton_> but i have to run to my next meeting
13:58:59 <bcotton_> thanks for brining this up!
13:59:44 <bcotton_> #endmeeting