16:03:11 <bcotton> #startmeeting Fedora 29 Release Retrospective
16:03:11 <zodbot> Meeting started Wed Nov 14 16:03:11 2018 UTC.
16:03:11 <zodbot> This meeting is logged and archived in a public location.
16:03:11 <zodbot> The chair is bcotton. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:03:11 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
16:03:11 <zodbot> The meeting name has been set to 'fedora_29_release_retrospective'
16:03:13 <bcotton> #chair bcotton mattdm
16:03:13 <zodbot> Current chairs: bcotton mattdm
16:03:19 <bcotton> #info Discussion is primarily on Jitsi. This room is mostly for note-taking. Please feel free to add your own notes to the minutes
16:03:21 <bcotton> #link https://meet.jit.si/GuiltyCherriesSearchLoyally
16:03:34 <bcotton> #topic Topic ideas
16:03:51 <bcotton> * Unannounced changes to core packages
16:03:53 <bcotton> * "Go" decision despite bugs with updates
16:03:58 <bcotton> * Cisco openh264 repo
16:03:59 <bcotton> * SELinux denials
16:04:30 <bcotton> * missing spins at release
16:05:14 <bcotton> mattdm are you on the call yet?
16:05:33 <bcotton> #topic Unannounced changes to core packages
16:08:50 <bcotton> #topic "Go" decision despite bugs with updates
16:11:42 <bcotton> #info 97% update bug couldn't be reproduced on a clean system because it was trigged by having some multilib packages installed
16:11:58 <mattdm> bcotton: no got pulled away. one minute
16:16:36 * nirik keeps dropping on and off, or otherwise not hearing audio
16:18:34 <bcotton> #action fzatlouk to propose adding multilib upgrade to release criteria
16:19:18 <bcotton> #topic missing spins at release
16:21:29 <nirik> I'm not wanting more blocking, just more notification
16:21:47 <nirik> ie, show more easily when they are failing so the people can fix them
16:22:11 <bcotton> #info The question is "how do we balance getting the release in a predictable manner versus letting spins ship when they're ready"
16:23:12 <bcotton> #info cloud ppc64le didn't ship because of an intermittent failure on the one compose that happened to end up being the RC
16:25:13 <nirik> perhaps we could make rc composes retry failed things... but that would make it take longer.
16:29:52 <bcotton> #info fzatlouk suggests someone from Spin SIG signs up for releng issues on Pagure so that they get an email with failed deliverables with each build
16:33:13 <dustymabe> jitsi not working well for me. i'll follow from here
16:34:44 * nirik can't hear whoever is talking now at all.
16:34:58 <bcotton> #agreed It would be nice to give Spins the ability to release after the main release if they need to
16:35:29 <bcotton> #info mattdm suggests giving each spin owner a "go" button that they have to push in order for the spin to be published
16:36:43 <bcotton> #action bcotton to discuss mattdm's suggestion with releng
16:38:12 <bcotton> #topic SELinux denials the first few days after install
16:38:52 <mboddu> jitsi is not working well for me
16:39:13 <bcotton> mboddu: it's not working well for anyone :/
16:39:30 <bcotton> #info SELinux denials violate release criteria
16:41:40 <bcotton> #info No SELinux notifications were not seeing during the last phase of testing
16:41:58 <bcotton> #info The SELinux troubleshooting applet is no longer on the default Workstation install
16:42:50 <jlanda> wops, little visit on my side, child are whining, afk
16:43:35 <bcotton> jlanda: no worries. can i #action you to propose changes to the criteria to address the current SELinux state?
16:43:56 <jlanda> yeah sure, and we can discuss about blocking on selinux fact
16:44:01 <jlanda> not the notification ;)
16:46:10 <bcotton> #action jlandato propose changes to the release criteria to reflect the fact that the SELinux troubleshooting applet is no longer in the default Workstation install. The criterion shoudl be dropped or modified to reflect reality
16:47:20 <bcotton> #topic Cisco openh264 repo
16:49:32 <mattdm> proposal: drop jitsi, switch to typing?
16:49:43 <bcotton> mattdm: seconded :/
16:49:44 <nirik> +1
16:49:53 <frantisekz> .hello2
16:49:54 <zodbot> frantisekz: frantisekz 'František Zatloukal' <fzatlouk@redhat.com>
16:50:26 <mboddu> mattdm: +1
16:50:36 <bcotton> okay, welcome to the platform that actually works
16:50:49 <frantisekz> yay :)
16:50:53 <mboddu> thanks bcotton :)
16:50:56 <bcotton> we're talking about the cisco openh264 repo not working correctly when we launched
16:51:12 <bcotton> specifically "We got email from Cisco saying that the binaries are up on their CDN, so we synced repodata on our end but the something went wrong on their end and we are getting 404 error while trying to access the newer binaries"
16:51:26 <bcotton> mboddu was working with Cisco to fix this. i assume it's been fixed by now?
16:51:44 <nirik> yeah, long since fixed.
16:51:51 <bcotton> awesome
16:51:53 <mboddu> bcotton: Yeah, its been fixed, but we cannot do anything on this as there was a delay on their end when I shipped them the rpms
16:52:11 <bcotton> #info mboddu worked with Cisco to get it fixed
16:52:16 <nirik> I guess we should add a step to check that the files are really there on there side before repodata updates
16:52:18 <bcotton> #info we cannot do anything on this as there was a delay on their end when I shipped them the rpms
16:52:35 <mboddu> nirik: +1 and I am planning to do it next time :)
16:52:48 <bcotton> the question is what do we do if they're not
16:53:18 <mboddu> bcotton: Well, people cannot get the latest rpms, but still be able to access older versions
16:53:30 <bcotton> #info A step has been added to verify that the files are really there before doing the repodata updates
16:53:37 <bcotton> oh, duh, yeah, because you haven't updated the repodata
16:53:47 <mboddu> Yup
16:53:56 <bcotton> cool. anything else on this one?
16:54:13 <x3mlinux> .hello x3mboy
16:54:14 <zodbot> x3mlinux: x3mboy 'Eduard Lucena' <eduardlucena@gmail.com>
16:54:21 <mboddu> Not from me
16:54:54 <bcotton> #topic Open floor
16:55:01 <bcotton> Okay, that's all the specific things people brought up
16:55:14 <bcotton> we have about 30 minutes left if there's anything else we want to cover about the F29 release
16:55:41 <bcotton> anything else that we want to address for f30? or anything we did particularly great that we want to make sure we do again?
16:55:47 <mboddu> bcotton: Nothing from me, but let me know when you are free and we can talk about the spins proposal
16:56:09 <mboddu> I was unable to hear the conversation on jitsi
16:56:22 <bcotton> mboddu: ack. it'll probably be later this week because i have some time-sensitive stuff to do this afternoon
16:56:31 <mboddu> bcotton: Sure, thanks
16:57:03 <mboddu> bcotton: And something to do again - We got the last two releases released on time without any delays, I want to see a hatrick :D
16:57:13 <mattdm> mboddu++
16:57:13 <zodbot> mattdm: Karma for mohanboddu changed to 6 (for the current release cycle):  https://badges.fedoraproject.org/tags/cookie/any
16:57:33 <bcotton> mboddu++
16:57:33 <zodbot> bcotton: Karma for mohanboddu changed to 7 (for the current release cycle):  https://badges.fedoraproject.org/tags/cookie/any
16:57:44 <bcotton> for f30, i want to release a week early :p
16:58:14 <x3mlinux> I know I'm being insistent with this, but TPs need some love from Spins
16:58:22 <x3mlinux> And mostly from KDE
16:58:51 <bcotton> #info Spins (particularly KDE) need to provide more input for the Talking Points
16:58:56 <x3mlinux> In my 3 releases working with Marketing, I haven't any TP from KDE Spin
16:59:26 <bcotton> x3mlinux: if you have any suggestions on how we can drag that out of them, i'm happy to hear :-)
17:00:02 <x3mlinux> Well, we try to make it a blocker, but a lot of people jumps out on fear and scream
17:00:06 <x3mlinux> xD
17:00:17 <bcotton> haha
17:00:25 <x3mlinux> Seriously, I don't know
17:00:45 <x3mlinux> I need more manpower in msrketing to be able to attend all SIGs meetings and ask them
17:01:04 <x3mlinux> Because even using pagure with issues didn't work
17:01:12 * mboddu got to run for another meeting
17:02:05 <mboddu> thanks bcotton and everyone
17:02:22 <bcotton> x3mlinux: yeah, we're definitely understaffed in marketing. we ask a lot of what's essentially a team of two. i think we need to try to recruit people to join specifically for that
17:02:27 <bcotton> thanks, mboddu!
17:02:58 <x3mlinux> Yeah, and the problem is how to make it
17:03:20 <x3mlinux> But we should discuss this on Marketing's channel
17:03:29 <bcotton> agreed
17:03:40 <bcotton> anything else for the F29 release or are we all retrospectived out?
17:03:41 <frantisekz> okay guys, sorry to interrupt you, I thought this was only for one hour and I need to leave now, I'll do the multilib criteria proposals, thanks bcotton for leading the meeting!
17:03:48 <bcotton> thanks frantisekz!
17:03:54 <x3mlinux> Thanks
17:04:23 <x3mlinux> The good thing about being in IRC is that I can take lunch during meeting
17:05:09 <bcotton> going once...
17:05:25 <bcotton> going twice...
17:05:58 <bcotton> okay, thanks everyone for your input and your patience with jitsi!
17:06:02 <bcotton> #endmeeting