15:01:51 <adamw> #startmeeting Fedora QA Meeting
15:01:51 <zodbot> Meeting started Mon May 25 15:01:51 2020 UTC.
15:01:51 <zodbot> This meeting is logged and archived in a public location.
15:01:51 <zodbot> The chair is adamw. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:01:51 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:01:51 <zodbot> The meeting name has been set to 'fedora_qa_meeting'
15:01:53 <adamw> #meetingname fedora-qa
15:01:53 <zodbot> The meeting name has been set to 'fedora-qa'
15:01:55 <adamw> #topic Roll call
15:02:17 * kparal is here
15:02:23 <adamw> ahoyhoy folks, who's around for fun?
15:02:33 <adamw> whoever is around for fun, please leave immediately
15:03:05 * kparal quits
15:03:10 <adamw> =)
15:03:11 * cmurf is there
15:03:34 * kparal pokes lruzicka and lbrabec
15:04:05 <frantisekz> .hello2
15:04:05 <zodbot> frantisekz: frantisekz 'František Zatloukal' <fzatlouk@redhat.com>
15:04:14 <lruzicka> .hello2
15:04:15 <zodbot> lruzicka: lruzicka 'Lukáš Růžička' <lruzicka@redhat.com>
15:04:24 * kparal pokes coremodule
15:04:36 * adamw pokes kparal
15:04:57 * kparal pokes kparal
15:05:23 <lruzicka> interesting that kparal did not poke frantisekz at the same time he did poke me and lbrabec
15:05:35 <kparal> frantisekz wasn't here
15:05:43 <adamw> it's dangerous, poking frantisekz
15:05:49 <adamw> you never know what'll happen to your finger
15:05:55 <frantisekz> :D
15:06:16 <kparal> can't unsee!
15:06:43 <lruzicka> heh, don't want to image
15:06:44 <kparal> anyway, I poked him on #fedora-qa anyway
15:06:46 <lruzicka> imaginge
15:07:02 <adamw> alrighty, let's get going
15:07:04 <adamw> light agenda today anyhow
15:07:08 <adamw> #topic Previous meeting follow-up
15:07:23 * sumantro is here
15:07:54 <adamw> #info "adamw to check test plans and schedules for significant-looking Changes" - i did that, and sent a few emails to change owners and stuff where i think we could improve the test plans a bit, but there wasn't anything huge
15:08:16 <adamw> i'd like to run openQA tests over a compose done with Python 3.9 before we land it, i'm going to trry and arrange that with miro
15:09:24 <adamw> coremodule, next one's for you:
15:09:27 <adamw> "coremodule to implement the service manipulation test case change using chronyd"
15:10:51 <kparal> he's probably afk
15:11:22 <adamw> let's take a walk down the wiki history wormhole!
15:11:24 <kparal> but I saw the testcase changed
15:11:48 <adamw> right
15:12:02 <adamw> #info "coremodule to implement the service manipulation test case change using chronyd" - this has been done: https://fedoraproject.org/w/index.php?title=QA:Testcase_base_service_manipulation&diff=576102&oldid=393532
15:12:10 <adamw> alright, any other follow-up from last time?
15:13:29 <lruzicka> why was it necessary to change it to chronyd? Is sshd not available somewhere?
15:14:16 <adamw> lruzicka: it's explained in the thread
15:14:39 <adamw> "In many of the testing scenarios that this testcase is used, the tester is
15:14:39 <adamw> logged into and testing the machine remotely via ssh. As the testcase
15:14:39 <adamw> stands now, the default service that is listed to test with is sshd. Since
15:14:39 <adamw> this test requires the tester to continually enable/disable/start/stop the
15:14:41 <adamw> sshd service, doing so on a machine that is remotely logged into will cause
15:14:41 <adamw> problems with ssh and could leave the tester stuck out of their system."
15:14:49 <adamw> (i'd replace "many" with "some" there, but that was basically it)
15:14:51 <kparal> lruzicka: are you saying you don't read test list and qa meeting logs?!
15:15:19 <cmurf> lruzicka: don't answer that
15:15:43 * adamw 's finger hovers over the fire button
15:16:00 <adamw> #topic Fedora 33 status and Changes
15:16:01 <lruzicka> I thought better of our testers.
15:16:20 <adamw> so, right now status is pretty boring, it's pretty much working
15:16:29 <kparal> booo
15:17:02 <adamw> #info Rawhide is currently working quite well, no major fires
15:17:12 <adamw> don't worry, plenty of time for people to break stuff!
15:17:38 <adamw> #info KDE 5.18.90 hit a snag part way through being built so we untagged all 5.18.90 builds until KDE team can resolve that
15:18:26 <adamw> #info major potentially-disruptive feature Changes I can see coming up are:
15:18:47 <adamw> #info systemd-resolved: https://pagure.io/fesco/issue/2381
15:19:23 <adamw> #info OpenSSL 3.0: https://pagure.io/fesco/issue/2373
15:19:47 <adamw> #info strong crypto settings phase 2: https://pagure.io/fesco/issue/2362
15:20:06 <adamw> #info Python 3.9: https://pagure.io/fesco/issue/2299
15:20:23 <adamw> i don't see any action required on those right now, though, just things to be aware of as they come up
15:21:15 <adamw> #info we now have validation events for IoT composes running alongside validation events for the main composes
15:21:42 <kparal> \o/
15:21:42 <adamw> still waiting to hear if IoT will be release-blocking for f33 and if we'll be changing this compose approach at all, but at least we're covered now
15:21:58 <adamw> if we *do* decide to make IoT release blocking and keep the separate compose stream, we can handle it
15:23:35 <adamw> alrighty then
15:23:42 <adamw> #topic Test Day / community event status
15:23:46 <adamw> sumantro, are you around?
15:23:59 <sumantro> adamw,  yes!
15:24:07 <adamw> alrighty, hit us
15:24:10 <adamw> #chair sumantro
15:24:10 <zodbot> Current chairs: adamw sumantro
15:24:48 <sumantro> so the update is, we have a Fedora Core OS test day .. more like validate docs, test things which cant be tested by their automation day coming up
15:24:58 <sumantro> dustymabe, has been very helpful
15:25:15 <sumantro> and Kamil is spearheading a lot of those efforts
15:25:52 <sumantro> Although the dates are not decided yet, but then we might have something by coming Wednesday
15:26:04 <adamw> sounds good
15:26:20 <adamw> #info a Fedora CoreOS Test Day is upcoming, look out for an announcement soon
15:26:36 <sumantro> https://pagure.io/fedora-qa/issue/616
15:26:42 <sumantro> this tracks the progress
15:28:00 <sumantro> thats all, the onboarding call will be happening starting next month , I will pick a date soon
15:28:17 <sumantro> the voting period is still on
15:28:41 <adamw> alrighty
15:28:43 <adamw> thanks sumantro
15:28:49 <adamw> #topic Open floor
15:28:54 <adamw> so that was an easy one, any other business, folks?
15:29:01 <sumantro> adamw np :)
15:32:15 <adamw> i guess not!
15:32:24 <adamw> let's all wait for the next thing to catch on fire
15:32:29 <adamw> thanks for coming, folks
15:32:37 <lruzicka> no problem
15:32:46 <adamw> #endmeeting