16:01:43 #startmeeting Fedora QA meeting 16:01:43 Meeting started Mon Nov 13 16:01:43 2017 UTC. The chair is adamw. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:01:43 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:01:43 The meeting name has been set to 'fedora_qa_meeting' 16:01:48 #meetingname fedora-qa 16:01:48 The meeting name has been set to 'fedora-qa' 16:01:52 #topic Roll Call 16:01:53 * pschindl is here 16:02:00 morning folks! 16:02:02 who's around? 16:02:03 Hi adamw 16:02:04 * coremodule present! 16:02:13 Hey adamw 16:02:28 morning 16:02:56 * sumantro is here 16:03:10 hi adamw :) 16:03:19 hi 16:03:29 * siddharthvipul1[ is here 16:05:16 how's everyone doing? 16:05:29 all good. how are you ? :D 16:06:07 not too bad 16:06:11 alrighty, let's get the show on the road... 16:06:12 Doing well here! 16:06:57 #topic Previous meeting follow-up 16:07:24 #info "adamw to create RC-1.6 validation event, investigate why automatic creation failed" - this is done, and the automatic creation failed because PDC didn't send out a fedmsg for the compose 16:08:17 relvalconsumer (the script that creates validation events) triggers off messages from PDC, because it needs to use info from PDC in deciding whether to create an event 16:08:33 so, that's that mystery. next item... 16:08:41 "sumantro to complete the module test cases, ask for help if needed" 16:08:46 i believe those are complete, awaiting review? 16:08:53 yes adamw 16:09:57 I need some review on it also sgallagh reviewed it and posted it to the @test list 16:10:03 great 16:10:17 #info "sumantro to complete the module test cases, ask for help if needed" - sumantro has completed a draft, it's up for review on test@ 16:10:23 any other follow up items? 16:11:23 nah! nothing from my side 16:11:45 oookey dokey 16:12:38 #topic Fedora 27 wrap-up 16:13:52 so, we signed off on fedora 27 final on thursday! 16:14:00 woot! 16:14:01 #info Fedora 27 was signed off on Thursday, will release tomorrow 16:14:18 adamw, can we bring back the retrospection page as I believe people might have a lot to tell this time? which will be valuable 16:14:37 #info Fedora Modular Server 27 Beta was signed off the same day and will release tomorrow as well; we are still working towards Final for Modular Server 16:14:40 sumantro: for sure 16:14:52 sumantro: do you want an action item to take care of that? 16:14:58 yes sure :) 16:16:28 #action sumantro to set up Retrospective page for Fedora 27, send out requests for feedback 16:18:42 other than that, we have the usual end-of-cycle things to do 16:19:04 so when is f25 phasing out? 16:19:08 in a month 16:19:19 well, i assume so - that's how it usually works 16:19:36 #action adamw and kparal to update common bugs page 16:19:44 #action adamw to create F29 blocker trackers 16:20:11 pagure should have another milestone for F28 test days too .. 16:20:21 oh, yeah. didn't we make you an admin in pagure? 16:20:34 nah :( 16:20:46 can I change /add milestone? 16:20:54 * sumantro tries 16:21:31 okay, how about this 16:21:50 #action adamw to grant sumantro necessary powers to create milestones in pagure 16:21:58 yee! :D 16:22:04 #action sumantro to create f28 milestones in pagure (and close old tickets/milestones as appropriate) 16:22:06 sound good? 16:22:14 yes! :D 16:23:44 so, i guess the issues of note for f27 are the whole 'split release' thing - be ready to explain to folks why Server isn't in the release - and maybe the number of gnome shell crasher bugs that came up... 16:25:28 sure! 16:25:29 for gnome shell crashers, btw, standard advice is 'try disabling extensions' and if it's still crashing, we can suggest switching to X instead of Wayland; under X shell will still crash, but when it does, the session doesn't die. 16:25:55 anyone got any other notes on f27 'regular' before we move on? 16:27:16 lets move on :) 16:28:31 roger 16:28:49 #topic Fedora Modular Server 27 GA test planning 16:28:59 so, as mentioned, Modular Server 27 is still being worked on 16:29:13 how exactly that works with regards to nightly composes and stuff i don't know, but fortunately that's not our problem! 16:29:38 sgallagh: around? do we have an approx. timeline for modular server Final phase? go/no-go date, etc? 16:30:08 Those things exist and should be on the official schedule 16:30:27 * adamw looks 16:30:51 I'm working this week on resyncing everything to match the set of packages that launched with F27 GA, with exceptions for modular-specific changes (such as DNF) 16:31:03 well, there's one date on https://fedoraproject.org/wiki/Releases/27/Schedule 16:31:08 "2018-01-09 Fedora Modular Server 27 Final Release (GA)" 16:31:26 ... I'm kind of hopeful we won't actually have to go out that far. 16:31:29 which would make the go/no-go 2018-01-04, i guess 16:32:10 Because our Beta worked out most of the major kinks, so I'm hoping we'll be able to piggy-back on the F27 GA bits and get 95% of the way there 16:32:35 But we'll see how badly this sync-up goes. :) 16:32:48 #info Modular Server GA is planned for 2018-01-09, but may move up 16:33:02 so does modular server GA essentially fork off of final GA? or how does that work? 16:35:30 oh well, not too important, i guess 16:36:03 #info the release validation process has been updated to create events for 27 modular composes, so we should get normal wiki validation pages for future composes 16:36:10 adamw: That's what I'm aiming for, yes 16:36:22 btw, at the moment it's all working correctly but not creating new events because the packages in current nightly composes aren't any different to what was in beta 16:36:25 So we don't have to duplicate all of their effort 16:36:30 okay 16:36:49 but i mean, you'll sync up with it but then conceivably put changes into some kinda modular server-only package stream? 16:36:52 Yeah, I figured. I'm working on that; should be new composes tonight or tomorrow night, depending on how quickly I get the modules updated 16:36:58 or any necessary package changes need to get sent out as updates? 16:37:16 adamw: Are you talking about pre-release, post-release, both, other? 16:37:41 sgallagh: both? 16:37:41 My plan is to get us to a working compose and then use Bodhi for the remainder of the process where needed. 16:38:45 okay. 16:38:51 Up to the point where we get that working compose, I may use the regular dist-git stream or create modular branches where necessary 16:39:00 it will depend on the package 16:39:07 (and package maintainer) 16:40:05 okay. so, bottom line folks, watch out for modular server validation event announcements, and help test it 16:40:34 Yes, please 16:40:38 openqa will test most of the server-specific requirements, but we definitely need humans helping fill out the installation results pages, poking at the modularity tools, and generally on the lookout for bugs the automated tests don't catch 16:40:50 sure! :) 16:41:16 Can do. 16:41:27 #topic Fedora 28 planning 16:41:36 of course, Fedora 28 is coming up too 16:42:37 so we'll want a new cycle of test days and all the usual stuff. 16:42:39 https://pagure.io/fedora-qa/issue/526 --> Kernel 4.14 Test Day on 2017-11-30 , I will go ahead and co-ordinate with jforbes 16:42:51 sumantro: awesome 16:42:58 this is the type of test day we were talking about at flock? 16:43:07 yes :) 16:43:27 cool 16:43:37 sumantro: are you OK co-ordinating the test days for f28 cycle? 16:43:43 yes :D 16:44:00 * sumantro will ping i18n and cloud team for regular test days 16:44:04 It is, and there will be another before F28 releases, I expect F28 will be on 4.15 at least 16:44:18 #action sumantro to act as co-ordinator for F28 test day cycle 16:44:37 * sumantro to send out call for test days tonight 16:44:46 #info Kernel 4.14 Test Day will be on 2017-11-30 , sumantro and jforbes are organizing, see https://pagure.io/fedora-qa/issue/526 16:44:49 thanks sumantro 16:45:07 np adamw :D 16:45:10 mattdm: are there any big blockbuster changes to how things are done for F28 that we need to be aware of? 16:45:38 dgilmore: sgallagh: mattdm: is there a plan to reconcile the compose process for modular server for f28? 16:46:23 adamw: I wouldn’t claim to have a *plan*, but it’s definitely a requirement. 16:46:31 heh 16:46:45 so the intent is to return to a single compose pipeline, with both modular and non-modular bits? 16:46:51 (I’m still too buried in the current process to have figured that out) 16:47:17 I’ll drag langdon into the conversation and sneak out the Blackfoot 16:47:34 Back door. Autocorrect... 16:47:46 I love technology... 16:48:02 * adamw notes the back door is under construction 16:48:08 it may be ready by next month...sorry ;) 16:48:32 okay, so there's an intent to Dooo Something but it's not all figured out yet. 16:48:49 #info there is some intent to reconcile the modular and non-modular compose processes for F28, but it is not yet done. 16:49:05 Yeah.. I need to write the change proposal 16:49:10 so i'll keep an eye on that going forward; we may need to keep having modular validation events for a while, though. 16:49:55 Would like to see a simpler "opt in" mechanism to work in to it.. So.. Around about server GA, I should be submitting iy 16:50:09 okay. 16:50:10 *it 16:51:05 I don't see any blockbuster Change proposals for F28 yet, so that's good. 16:51:26 note that we'll probably start gating Rawhide composes during the f28 cycle; almost all the bits for that are in place now. 16:52:09 #info Rawhide compose gating will likely start during the F28 cycle 16:52:47 just in case - 'gating' meaning that instead of every successful compose being synced out to the mirrors and thus 'becoming' the new state of Rawhide, only composes that pass a certain set of the automated tests will. 16:53:29 adamw, are we planning to have fedora modular tested with 4.14 kernel , cz if we are planning to merge the bits into a single release cycle later point in time, will that be helpful? 16:54:07 sumantro: i wouldn't expect that there would be much connection between the kernel and the modular server changes 16:54:15 i.e. i don't think it's necessary to test it specifically 16:55:13 sure 16:55:24 okay, any other thoughts on f28 so far? 16:56:16 sig to help out with test days ? that plan is in action .. I will relay the updates in the next meeting 16:56:55 okay 16:57:06 fedora qa onboarding call will happen sometime in December and Fedora 102 classroom session 16:57:18 awesome 16:57:18 awesome 16:57:30 #info next onboarding call and Fedora 102 classroom session planned for December 16:58:15 coremodule++ 16:58:15 sumantro: Karma for coremodule changed to 4 (for the f26 release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:58:21 #topic Open floor 16:58:57 any other business, quickly, folks? 16:59:05 * sumantro has nothing here 16:59:52 nope 17:00:29 oh, one thing 17:00:39 we need someone to do the Heroes of Fedora stuff for the f27 cycle 17:00:41 any volunteers? 17:01:02 adamw, I'll do it! 17:01:07 roger 17:01:17 #action coremodule to put together Heroes of Fedora posts for F27 cycle 17:01:52 coremodule: https://fedoraproject.org/wiki/QA:Recognition is the SOP for that, more or less 17:01:58 pull requests to improve the tools are welcome :P 17:02:25 adamw, for the scripts used to pull the data? 17:02:30 yeah 17:02:41 it could be a much smoother process 17:02:52 Ah, roger that! 17:03:21 having to run four different commands and hand edit the output and glue it all together gets old 17:03:29 okay, anything else? 17:05:41 then thanks a lot for coming, folks 17:06:17 thx. good day. 17:06:49 * adamw sets fuse 17:06:52 thanks adamw for hosting :) 17:08:08 #endmeeting