15:02:48 <adamw> #startmeeting Fedora QA Meeting
15:02:48 <zodbot> Meeting started Mon Sep 30 15:02:48 2019 UTC.
15:02:48 <zodbot> This meeting is logged and archived in a public location.
15:02:48 <zodbot> The chair is adamw. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:02:48 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:02:48 <zodbot> The meeting name has been set to 'fedora_qa_meeting'
15:02:52 <tablepc> Evening is good too
15:02:54 <adamw> #meetingname fedora-qa
15:02:54 <zodbot> The meeting name has been set to 'fedora-qa'
15:02:58 <adamw> #topic Roll call
15:03:07 <cmurf> .hello
15:03:08 <zodbot> cmurf: (hello <an alias, 1 argument>) -- Alias for "hellomynameis $1".
15:03:13 <adamw> $(TIMEOFDAYAPPROPRIATEGREETING) all
15:03:13 <cmurf> .hello chrismurphy
15:03:13 <zodbot> cmurf: chrismurphy 'Chris Murphy' <bugzilla@colorremedies.com>
15:03:14 <tablepc> .hello2
15:03:16 <zodbot> tablepc: tablepc 'Pat Kelly' <pmkellly@frontier.com>
15:03:29 * satellit_ listening
15:03:33 <bcotton> .hello2
15:03:34 <zodbot> bcotton: Something blew up, please try again
15:03:43 * bcotton explodes
15:03:52 <frantisekz> .hello2
15:03:54 <zodbot> frantisekz: frantisekz 'František Zatloukal' <fzatlouk@redhat.com>
15:04:09 <cmurf> zodbot blew me up earlier too
15:04:21 <adamw> well now there's bits of bcotton everywhere, jeez
15:04:29 <adamw> nothing's harder to get out of meeting room carpets
15:04:36 <tablepc> Mean old bot
15:05:16 <coremodule> .hello2
15:05:17 <zodbot> coremodule: coremodule 'Geoffrey Marr' <gmarr@redhat.com>
15:06:08 * sumantro is here
15:06:14 * kparal is here
15:06:19 <sumantrom> .hello2
15:06:20 <zodbot> sumantrom: sumantrom 'Sumantro Mukherjee' <sumukher@redhat.com>
15:06:24 <adamw> full house today huh
15:06:45 <adamw> let's get rolling!
15:06:45 <adamw> Previous meeting follow-up
15:06:49 <adamw> ...let's try that again
15:06:50 <adamw> #topic Previous meeting follow-up
15:07:23 <adamw> #info "adamw to create and fill out common bugs page" - that's done, https://fedoraproject.org/wiki/Common_F31_bugs
15:08:05 <adamw> #info "adamw to add a short note to each relevant wiki page (automatic blockers and 'last minute' blockers) to explain the relationship between them" - also done, see https://fedoraproject.org/w/index.php?title=QA:SOP_blocker_bug_process&diff=553726&oldid=551137
15:08:37 <adamw> #info "adamw to resolve all discontinuities" - also done, unfortunately there were some minor side effects like exploding bcottons
15:08:55 <adamw> any other follow-up on last time? :)
15:11:32 * kparal blinks
15:12:40 <adamw> kparal: was that all of the followup?
15:12:48 * coremodule coughs
15:12:56 <adamw> alright stop...doing things!
15:12:56 <kparal> wait, this wasn't a staring contest?
15:12:57 <adamw> #topic Fedora 31 status
15:13:07 <adamw> well, it sure is...31-y
15:14:14 <bcotton> fewer than 20 proposed and accepted blockers now, at least
15:14:39 <kparal> we're keeping it nice and small
15:15:15 <kparal> somebody could wake up gnome devs, though. half of the bugs are theirs
15:15:21 <tablepc> I must be testing the wrong things 0928 worked nice for me
15:15:55 <tablepc> Will except for that one bug, but not a blocker
15:16:38 <adamw> you just didn't breathe on the right thing
15:17:08 <adamw> #info there aren't any huge break-the-world bugs in F31 right now really, but there are *lots* of outstanding blockers, which worries us a bit
15:17:09 <tablepc> I must change my technique
15:17:41 <adamw> #action adamw to check with desktop team that they're confident about resolving all the outstanding GNOME-related blockers
15:19:10 <adamw> note, we didn't get a compose since Saturday because yesterday's compose is stuck, it seems. i'll get releng to kick something.
15:19:23 * satellit_ soas not building atm..."the gstreamer-plugins-espeak package was removed and then re-added"
15:19:33 <adamw> satellit_: propose the bug as an FE
15:19:42 <satellit_> k
15:21:35 <adamw> #info Final freeze is on October 8, so we have just over a week till then
15:21:45 <lruzicka> . hello2
15:21:46 <zodbot> lruzicka: Something blew up, please try again
15:21:57 <adamw> oh good lord i just got done cleaning up the chunks of bcotton too
15:22:18 <lruzicka> .hello2
15:22:19 <zodbot> lruzicka: lruzicka 'Lukáš Růžička' <lruzicka@redhat.com>
15:23:26 <adamw> alrighty then
15:23:34 <adamw> #topic Criteria proposals status
15:23:54 <adamw> so on my side the status is sort of 'on hold since now we're dealing with the f31 release grind'
15:24:19 <adamw> and good old johannbg would've told us how silly it is to change the release criteria at this point in the cycle...
15:25:40 <kparal> there are too few vikings around these days, aren't they?
15:26:28 <tablepc> Be nice my wife is a viking
15:26:29 <adamw> they're a dying breed
15:28:08 <adamw> so, on the ec2/cloud thing: let's say for Final even though we didn't nail down the criteria yet, we should make sure we *do* work on ec2
15:28:17 <adamw> so, folks who have ec2 accounts etc, please test the candidates there
15:29:13 <adamw> #info xen/ec2 proposal: on hold till f31 cycle is complete, but for F31 let's make sure we *do* work on ec2
15:30:13 <adamw> #info btrfs proposal: also on hold till f31 cycle is complete, fortunately we have no known btrfs install issues at present
15:30:51 <adamw> #info podman / container management proposal status: waiting on dustymabe to respond to all feedback
15:31:39 <adamw> #info proposal to move image size criterion from Beta to Final: dropped for now, may be revived if we still have problems with this in future
15:32:15 <adamw> #action adamw to go ahead and add the basic desktop background criterion to 'automatic blockers' as that proposal received no objections
15:32:24 <adamw> i think that covers all outstanding criteria stuff...any others?
15:32:38 <kparal> nothing here atm
15:33:11 * satellit_ is the f31 cinnamon background final?
15:33:59 <adamw> satellit_: i've no idea...
15:34:02 <adamw> is it wrong?
15:34:47 <satellit_> did everything netinstall of cinn  light blue background w/ design
15:35:00 <satellit_> no idea
15:35:28 <adamw> if it's not the official f31 background, file a bug on it and propose it as FE
15:35:30 <adamw> thanks :)
15:36:00 <satellit_> hoe do I tell if it is offical f31 background?
15:36:44 <adamw> is it the same as the one for KDE or GNOME
15:36:57 <satellit_> will look...
15:37:00 <adamw> usually you can check on https://fedoraproject.org/wiki/Wallpapers , but that hasn't been updated yet
15:37:58 <adamw> satellit_: https://openqa.fedoraproject.org/tests/460288#step/desktop_notifications/36
15:38:02 <adamw> that's the official one
15:38:34 <satellit_> ok that is same one on cinn   thanks
15:39:04 <adamw> ok, so it's good
15:39:16 <adamw> #topic Test Day / community event status, onboarding call planning
15:39:23 <adamw> sumantrom: over to you? :)
15:39:31 <adamw> #chair sumantrom
15:39:31 <zodbot> Current chairs: adamw sumantrom
15:39:57 <sumantrom> The kernel 5.3 Test week is going on
15:40:08 <sumantrom> https://fedoraproject.org/wiki/Test_Day:2019-09-30_Kernel_5.3_Test_Week
15:40:19 <tablepc> 5.3 passes here
15:40:19 <sumantrom> The IoT test day is on 2019-10-02
15:40:58 <sumantrom> http://testdays.fedorainfracloud.org/events/73
15:41:36 <sumantrom> https://bugzilla.redhat.com/show_bug.cgi?id=1752961 is causing kernel panic in a lot of systems
15:42:02 <adamw> that sounds bad
15:43:04 <frantisekz> hmm, kparal, lbrabec, you both have ThinkPad T480s which is mentioned as affected hw in that bug
15:43:06 <tablepc> Oh I tested 5.3.1
15:43:21 <linuxmodder> .me late
15:43:53 <tablepc> and different HW
15:44:38 <adamw> it's an intermittent bug it seems.
15:44:47 <adamw> (looks like it depends on the state of the TPM).
15:45:07 <kparal> I can test it with my laptop tomorrow
15:45:26 <adamw> #info kernel 5.3 test week is ongoing at https://fedoraproject.org/wiki/Test_Day:2019-09-30_Kernel_5.3_Test_Week
15:46:13 * nirik notes the two newest rawhide kernels don't boot at all... but they are untagged
15:46:34 <linuxmodder> I have a lenovo flex which has same tpm as the t480s I can test on tomorrow
15:46:53 <frantisekz> i don't see any issues with 5.3.x kernels on T470s
15:47:40 <tablepc> I tested on an M83 with i5 cpu
15:50:14 <adamw> ok, that's only one bug
15:50:20 <adamw> we can follow up on it outside of the meeting
15:50:26 <adamw> sumantro, how about...all other community events :)
15:50:53 <sumantrom> so alciregi coremodule and me met to fix up onboarding calls
15:51:16 <dustymabe> hmm. something waiting on my feedback?
15:51:40 <adamw> dustymabe: you proposed a podman criterion, there was quite a lot of feedback to the initial proposal, i didn't see an updated proposal
15:51:50 <sumantrom> we are currently searching timings which fit all the people
15:52:08 <sumantrom> we have a week long holiday in china and parts of india..
15:52:27 <sumantrom> I would suggest waiting for some more time before we run a call
15:52:34 <dustymabe> adamw: now I can't find the thread to respond to :)
15:52:38 <adamw> #info onboarding call scheduling is being worked out at present, please reply to https://forms.gle/DzP7q45Tfvv52BSz7 with your availability if you're interested in joining
15:52:54 <coremodule> I am going to send out another survey later today to find out what times work best for those who want to participate.
15:52:54 <adamw> dustymabe: you called it "Proposing new release criteria"
15:53:09 <adamw> dustymabe: next time i'd put 'podman' in there or something if i were you :P
15:53:30 <sumantrom> this is though there will a slight different, as there might be people who are not comfortable on calls, we want to run an IRC version of the same onboarding
15:54:07 <coremodule> Sorry, actually we will use the survey link adamw posted above with the info tag.
15:55:15 <adamw> #info this time we will try to run an IRC onboarding meeting alongside the call
15:55:22 <adamw> good luck with that :)
15:55:27 <sumantrom> :)
15:55:47 <adamw> maybe it'd be a good idea to have one person in charge of the call and one the irc side? it sounds like too much for one person to do simultaneously
15:56:14 <bcotton> +1 i've tried to do both at once and it's awful
15:56:20 <sumantrom> no both are separate events :)
15:56:30 <sumantrom> first the IRC then the call
15:56:57 <sumantrom> so all the doubts will kinda be streamed live with some hands on over a BJN
15:57:51 <adamw> ah i see
15:59:15 <dustymabe> adamw: responded to the list
15:59:19 <adamw> thanks
15:59:25 <adamw> #topic Open floor
15:59:28 <adamw> we're coming up on time, so...
15:59:35 <adamw> very quick open floor section :) any other concerns?
15:59:47 <adamw> #info blocker review meeting will start in 10 seconds in #fedora-blocker-review
16:00:31 <lruzicka> does anybody know an android app that would be able to keep the connection?
16:00:55 <lruzicka> anytime my screen darkens, its lost
16:01:19 <kparal> lruzicka: you can try web browser https://webchat.freenode.net
16:01:42 <lruzicka> kparal, will try, thanks
16:01:46 <kparal> lruzicka: also https://play.google.com/store/apps/details?id=com.nealc.unsleep&hl=en
16:01:55 <kparal> that's a simple solution to your problems :)
16:02:20 <adamw> i use revolution irc, i don't think it loses connection on screen darken
16:02:28 <adamw> (also see if you have some ultra battery saving mode turned on?)
16:03:27 <lruzicka> my revolution keeps logging out
16:03:43 <adamw> hum
16:03:46 <lruzicka> maybe, it is the bad company mode
16:03:53 <kparal> usually it's the vendor's power saving feature and you can toggle if off for a particular app somewhere in the system
16:03:55 <adamw> could be!
16:04:01 <adamw> yeah, that
16:04:08 <adamw> anyway, we're over time for Android Support Hour, i'm afraid :P
16:04:11 <adamw> thanks for coming everyone!
16:04:13 <adamw> #endmeeting