17:00:07 #startmeeting F30 Beta Go/No-Go meeting 17:00:07 Meeting started Thu Mar 28 17:00:07 2019 UTC. 17:00:07 This meeting is logged and archived in a public location. 17:00:07 The chair is bcotton. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:07 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:00:07 The meeting name has been set to 'f30_beta_go/no-go_meeting' 17:00:08 #meetingname F30-Beta-Go_No_Go-meeting 17:00:08 The meeting name has been set to 'f30-beta-go_no_go-meeting' 17:00:14 #topic Roll Call 17:00:16 .hola mohanboddu 17:00:17 * sumantro is here 17:00:20 * pwhalen is here 17:00:25 * mboddu tried, but didn't work 17:00:27 * satellit listening 17:00:28 .hello mohanboddu 17:00:29 mboddu: mohanboddu 'Mohan Boddu' 17:00:30 .hello2 17:00:31 frantisekz: frantisekz 'František Zatloukal' 17:00:38 * coremodule is here 17:00:39 .hello2 17:00:44 coremodule: coremodule 'Geoffrey Marr' 17:00:47 * kparal lurks 17:00:58 .hello adamwill 17:00:59 adamw: adamwill 'Adam Williamson' 17:01:10 .hello2 17:01:13 jlanda: jlanda 'Julen Landa Alustiza' 17:01:15 .hello zlopez 17:01:17 mkonecny: zlopez 'Michal Konečný' 17:01:26 morning 17:01:35 * jlanda is on the road, so lurking too 17:01:44 morning nirik 17:01:52 hello, everyone! 17:02:05 morning/afternoon/ 17:02:07 .hello2 17:02:08 sgallagh: sgallagh 'Stephen Gallagher' 17:02:14 #topic Purpose of this meeting 17:02:15 #info Purpose of this meeting is to check whether or not F30 Beta is ready for shipment, according to the release criteria. 17:02:17 #info This is determined in a few ways: 17:02:21 #info 1. No remaining blocker bugs 17:02:22 #info 2. Release candidate compose is available 17:02:23 #info 3. Test matrices for Beta are fully completed 17:02:32 so.... let's do this! 17:02:57 #topic Current status — blockers 17:03:05 #info 1 Proposed Blockers 17:03:07 #info 1 Accepted Blockers 17:03:11 let's review 17:03:20 #topic (1692135) Possible regression: Spinner will not always terminate unless window titlebar grabbed and window moved 17:03:21 #link https://bugzilla.redhat.com/show_bug.cgi?id=1692135 17:03:22 #info Proposed Blocker, gnome-shell, NEW 17:03:32 -1 blocker, doesn't hit any beta critera. 17:03:33 -1b 17:03:38 folks seemed pretty -1 in the BZ 17:03:42 -1 B 17:03:44 -1 17:03:54 -1 17:04:01 -1 17:04:02 * mboddu didn't hit it while testing 17:04:03 -1 blocker 17:04:07 -1 17:04:14 I've seen this in rawhide sporadically... it's anoying, but not worth blocking beta for. 17:04:19 intermittent, doesn't really violate any criteria 17:04:22 in fact it's happening to me now. :) 17:04:25 * wa1em lurking and late 17:04:27 :) 17:04:27 I hit it, but everything still works. It's annoying but not blocker, no criteria violations. 17:04:50 I have tested for only few min, but didn't hit it 17:04:56 -1 beta blocker, -1 final blocker 17:04:59 proposed #agreed BZ1692135 is rejected as a beta blocker. It does not violate any criteria 17:05:06 ack 17:05:06 ack 17:05:07 ack 17:05:09 ack 17:05:10 ack 17:05:10 ack 17:05:13 ack 17:05:14 ack 17:05:20 #agreed BZ1692135 is rejected as a beta blocker. It does not violate any criteria 17:05:34 #topic (1692323) qemu crashes with virgl enabled on some GPUs 17:05:36 #link https://bugzilla.redhat.com/show_bug.cgi?id=1692323 17:05:37 #info Accepted Blocker, qemu, VERIFIED 17:05:56 I've verified that , fixed in 1.8 17:05:57 looks like this is fixed in -1.8? 17:05:59 awesome 17:06:04 yeah, fix is in beta-1.8 and verified 17:06:11 Yep 17:06:12 #info fix is in beta-1.8 and verified 17:06:23 anything else on blockers before we move on? 17:06:35 nope 17:06:37 for the record, we curate VERIFIED state very carefully for blockers, so any time you see it, it means 'we have verified that this is fixed in the current candidate 17:07:00 * nirik is glad it didnt hit the same libseccomp thing f29 did 17:07:11 #topic Current status — Release Candidate 17:07:22 nirik: yeah, not sure why not, but it definitely doesn't. i tested it specifically myself 17:07:28 #info Beta-1.8 is the release candidate 17:07:33 anything else we want to say on this? 17:07:42 ship it :) 17:07:45 :) 17:07:47 :) 17:07:47 is this where we do validation status? 17:07:52 or is there a separate topic for that? 17:08:28 adamw: we're about to move to test coverage if that's what you're after 17:09:12 U.S.S. Ship It 17:09:17 rogr 17:09:40 #topic Current status — Test coverage 17:10:05 #link https://fedoraproject.org/wiki/Category:Fedora_30_Beta_Test_Results 17:10:17 adamw and team, the floor is yours 17:10:57 adamw and his servants .... ehm :D 17:11:06 jsut a sec 17:11:13 ack 17:11:38 so, coverage is looking fine except for a few things on server 17:11:39 been largely absent this cycle but willing to help on any remaining testing for B or final 17:12:00 sgallagh: i thought you ran the AD tests at some point, but testcase_stats says no? 17:12:04 also remote logging has never been run 17:12:09 adamw, remote logging from my little testing the other night looked fine, although I forgot to update matrix 17:12:17 adamw: I ran the AD tests but didn't update the matrix. 17:12:19 We're good there. 17:12:20 wa1em: awesome, can you please do it now? :) 17:12:21 sgallagh: ditto 17:12:32 so with that info, i'd say coverage looks good 17:12:36 same here, I made the rsyslog thing on 1.7 but miss the matrix :D 17:12:46 #info Test coverage looks good 17:12:59 every test is covered between beta-1.4 and beta-1.8 except SAS as per the ancient traditions 17:13:24 one sec and I can for sure 17:13:25 great 17:13:53 * adamw should really put that remote logging test in openqa... 17:14:25 any other questions or comments on test coverage? 17:15:19 Updated. adamw I realized I didn't do the kickstart tests, but there really isn't a codepath there that isn't satisfied by the sssd, cockpit or FreeIPA tests 17:15:31 adamw, mind you I never got to the tcp optional on remote logging 17:15:31 yeah, it Should be okay ;) 17:15:46 wa1em: that's ok, 'optional' means optional :P 17:15:56 okay, well then I think we're ready to make a decision 17:15:57 if the other stuff works the requirement is satisfied 17:16:03 I usually get to them tho hence the mention 17:16:30 #topic Go/No-Go decision 17:16:31 I will poll each team. Please reply “go” or “no-go” 17:16:35 FESCo? 17:16:42 go go go 17:16:43 go 17:16:49 #info FESCo is GO 17:16:53 RelEng? 17:17:13 quick nirik, change hats 17:17:22 * nirik ducks into a phone booth 17:17:23 Go 17:17:23 go 17:17:25 #info RelEng is GO 17:17:27 QA? 17:17:40 go 17:17:42 GO 17:17:43 go 17:17:48 #info QA is GO 17:18:02 i think servants need their master to answer 17:18:08 nope. 17:18:11 haha 17:18:11 :D 17:18:13 #agreed Fedora 30 Beta RC-1.8 is GO 17:18:14 :D 17:18:14 #info Fedora 30 Beta will release on 2019-04-02 17:18:16 :D 17:18:25 #action bcotton to announce decision 17:18:32 cool. Another ontime release. ;) 17:18:32 #topic Open floor 17:18:34 Anything else we need to discuss before closing? 17:18:42 QA decision is made according to a policy: "QA approves the release if all validation tests appropriate to the release phase (Beta or Final) have been performed and there are no accepted blocker bugs that are unaddressed in the candidate compose, updates repository or previous releases updates repository. QA does not approve the release if there are any accepted blocker bugs that are unaddressed or if validation testing is incomplete. There is no 17:18:42 room for discretion in this determination" 17:18:48 \o/ 17:18:52 * wa1em goes to setup for populating for B release seeding 17:18:55 nirik: technically on time (tm) 17:18:56 There is a infra ticket about ppc64le repos on f30 17:19:03 adamw: the *best* kind of on-time 17:19:07 =) 17:19:12 oh, that's soon :) 17:19:18 We should fix that too ideally 17:19:20 sgallagh++ you beat me to it 17:19:20 bcotton: Karma for sgallagh changed to 13 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 17:19:20 nirik: I think only the final matters 17:19:25 adamw: can you please later halp me with the pycthon classroom lab? 17:19:37 mhroncok: let's talk in #fedora-qa ? 17:19:41 sure 17:19:45 jlanda: is it a problem? or just a thing? 17:19:52 Give me a sec 17:20:02 mhroncok, I'm game for helping that too 17:20:03 ppc64le is not blocking. ;) 17:20:16 but yes, we can fix it... 17:20:45 https://pagure.io/fedora-infrastructure/issue/7672 17:21:01 i just this morning started getting update-testing complaints on ppc64le 17:21:31 I'm not the best candidate to determinate if it's a big problem or not, but looks weird at least 17:21:52 but yeah, is not blockinh 17:21:59 So let go 17:22:14 #info URLs are wrong for F-30 updates/updates-testing on ppc64le 17:22:17 #link https://pagure.io/fedora-infrastructure/issue/7672 17:22:25 good to know about, at least 17:22:44 * nirik thinks we can fix them later today, so it shouldn't be a problem too much longer. ;) 17:22:58 #info nirik thinks we can fix them later today 17:22:59 nice nirik++ 17:23:14 nirik: I can help as well 17:23:16 anything else, or are we ready for me to send an email? 17:23:21 by the time ls -l completes in a ppc64le kvm, this will get fixed :D 17:23:26 mboddu: i was counting on it. ;) 17:23:34 ^on x86_64 17:23:35 Send send 17:23:58 nirik:Sure :) 17:24:47 okay! thanks everyone. we'll see you again in a few weeks when we do this for final :-) 17:24:56 #endmeeting