15:00:21 <adamw> #startmeeting Fedora QA meeting
15:00:22 <zodbot> Meeting started Mon May 23 15:00:21 2016 UTC.  The chair is adamw. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:22 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:00:22 <zodbot> The meeting name has been set to 'fedora_qa_meeting'
15:00:26 <adamw> #meetingname fedora-qa
15:00:27 <zodbot> The meeting name has been set to 'fedora-qa'
15:00:30 <adamw> #topic Roll call
15:00:34 * coremodule is here.
15:00:38 <adamw> randomuser: that's the next meeting. =)
15:00:39 * kparal is here
15:00:44 <adamw> ahoyhoy folks, who's around for qa funtimes?
15:00:44 * prakash is here
15:00:45 * omiday is here
15:00:57 <randomuser> good morning, adamw
15:01:00 * Sumantro is here
15:01:38 * c0mrad3 wow this meeting looks bigger than the commops one :)
15:01:41 * brunowolff is here
15:03:35 <adamw> good to see y'all
15:03:49 <adamw> so we're skipping previous meeting follow-up because we followed up on everything from the last meeting on-list, IIRC
15:03:54 <adamw> yell if I'm wrong
15:04:04 <Sumantro> Good to see you too Adamw!
15:05:21 <adamw> alrighty then
15:05:31 <adamw> #topic Fedora 24 status check
15:05:53 <adamw> so just figured it'd be good to check in on the major F24 points, make sure everyone knows what's going on and there are no big problems lurking
15:06:23 <adamw> we have final freeze coming up on 05-31 and go/no-go on 06-09, so we should be making sure we have full test coverage ATM
15:07:36 <omiday> for new folk can you expand on that?
15:07:40 <adamw> sure!
15:08:08 <adamw> 'freeze' is when we stop moving packages to 'stable' except for fixes for blocker and freeze exception bugs
15:08:26 <adamw> so packagers can still do new builds and send them to updates-testing, and people can test  them, but they will not go in the final release unless they fix an FE or blocker bug
15:08:30 <nb> .hello nb
15:08:31 <zodbot> nb: nb 'Nick Bebout' <nb@nb.zone>
15:08:35 * omiday is also happy  with a pointer to the docs just so he doesn't waste meeting time
15:08:43 <adamw> non-FE/blocker fixes eventually go out as '0-day updates' (they appear in the 'updates' repo on release day)
15:08:57 <adamw> 'go/no-go' is the meeting where we decide whether to go ahead with the release
15:09:35 <adamw> so basically if we don't have a fully-tested RC that passes the tests on that date, we say 'no-go' and delay the release
15:10:09 <adamw> so of course it's an important date for us =) the closer we get to it the more you'll probably see lots of chat between qa and releng and devel teams trying to get all the blocker bugs fixed.
15:10:48 <omiday> those would be the bugs you mentioned in the list right?
15:10:53 <adamw> it's important that we make sure to run any of the validation tests that haven't been run yet as soon as we can, so we can find any remaining blocker bugs as early as possible.
15:11:12 <adamw> omiday: yep, and you can always see them at http://qa.fedoraproject.org/blockerbugs/current
15:11:28 <adamw> alrighty, so
15:11:36 <adamw> the other thing i thought it'd be good to check in on is the big changes
15:12:01 <adamw> while i was on vacation it seems like we had the test day for graphical system upgrade and it went well, thanks a lot to sumantro for organizing and everyone for testing!
15:12:39 <adamw> #info graphical system upgrade Test Day went off well and found lots of bugs: https://fedoraproject.org/wiki/Test_Day:2016-05-16_Workstation_Graphical_Upgrade
15:13:08 <adamw> does anyone know if there was any planning for how it will be rolled out and communicated yet?
15:13:44 <Sumantro> Thanks a ton, Adam and the testers :)
15:14:03 <kparal> I think the last version is that they don't want to have it available on release day, but wait a while
15:14:10 <kparal> but I might be wrong
15:14:25 <kparal> plus, they now have a ton of bugs to fix
15:15:02 <adamw> okay
15:15:18 <kparal> you can see the major bugs here: https://bugzilla.redhat.com/showdependencytree.cgi?id=1308538&hide_resolved=1
15:15:25 <adamw> yep
15:15:53 <adamw> #info there are now many bugs to fix for graphical system upgrades and it may not be ready for release day
15:16:03 <kparal> also, according to the fesco ticket, it's not intended to be the official upgrade method, so our criteria don't apply
15:16:04 <adamw> anyone mind if i take a #action to sync with desktop team and fesco on that planning?
15:16:31 <omiday> go for it
15:16:40 <kparal> I can talk to them and ask what their plans are
15:16:54 <kparal> oh, "if I take"
15:16:57 <kparal> sure, go ahead :)
15:18:17 <adamw> #action adamw to sync with desktop team and FESCo on graphical upgrade feature release planning
15:18:23 <adamw> ok
15:18:38 <adamw> has anyone been tracking the status of the new liveusb-creator?
15:18:55 <kparal> is there something to track? it works quite well
15:19:06 <kparal> and it has been pushed stable to all releases
15:19:33 <kparal> the "primary deliverable" has been postponed to F25, if you mean that
15:19:53 <kparal> so we're still going to offer an .iso, and link to LUC in docs and wiki
15:20:04 <kparal> for F25, we might offer the .exe directly for Windows users
15:20:05 <adamw> just that it's working well enough
15:20:10 <kparal> and maybe even Mac
15:20:20 <kparal> adamw: it is
15:20:22 <adamw> even if it's not the 'primary deliverable' it's still one of the supported methods, so we need to be sure it's working ok
15:20:23 <adamw> awesome
15:20:37 <kparal> it passed my QA, it has to be OK :)
15:20:44 <coremodule> Good success on multiple live-media created with liveusb-creator here.
15:20:49 <adamw> =)
15:21:07 <adamw> great. so, can anyone think of any other major f24 changes we need to check in on?
15:21:17 <adamw> i feel like there's one other i'm forgetting but it could just be standard-issue paranoia
15:21:21 <Sumantro> I tested it with 1.6 beta and the latest nightly works good
15:21:51 <kparal> just a tiny remark, there are more and more reports that people can't install F24 with 1GB RAM or less. maybe we should make sure it gets reflected in the release notes or somewhere?
15:22:06 <adamw> well, i'd rather test it carefully first.
15:22:10 <adamw> there are quite a lot of variables involve.d
15:22:16 <kparal> it's probably very dependent on the setup
15:22:35 <kparal> but e.g. lbrabec can't run anaconda GUI on banana pi with 1GB RAM
15:22:38 <kparal> only text install
15:22:39 <adamw> it depends on the package set, the partitioning, the installer interface, and dvd vs. netinst vs. live
15:23:09 <kparal> but that's pxe, which uses more RAM
15:23:16 <kparal> ok, just mentioning
15:23:47 <adamw> i kinda want to have an openqa test that's 'informational'
15:24:14 <adamw> it would record installer ram usage, size of installed system, number of packages, load average at 'idle', all that kinda stuff
15:24:33 <adamw> then you could do analysis on the logs from an arbitrary series of those results...
15:24:38 <adamw> just never got around to it yet :/
15:24:52 <adamw> then we'd at least stand a chance of figuring out when that kind of thing really changed
15:25:31 <adamw> ok, so anything else for f24?
15:25:41 <brunowolff> spin-kickstarts moved to Pagure (as fedora-kickstarts). There was some sort of hiccup, and I'm not sure exactly where things stand. This affects getting changes applied during the next freeze.
15:25:49 <kparal> adamw: sounds great
15:27:44 <adamw> brunowolff: can you expand a bit on 'hiccup'?
15:30:03 <brunowolff> Kevin had to switch something back for a bit. I'll look through the maling list log and post a link shortly. I don't have the messages locally any more.
15:30:25 <adamw> okay...
15:30:32 <adamw> well, sounds like we'll just have to deal with that as it comes =)
15:30:47 <adamw> #info there may be issues with commits to spin-kickstarts due to the move to pagure, stay tuned
15:31:13 <adamw> think that's all for f24?
15:32:00 <adamw> #topic New member check-in
15:32:19 <adamw> so this was just an idea i had, but I thought it might be nice to check in with our newer members (RH and non-RH!) and see how they're finding things so far
15:32:26 <adamw> say, people who joined in the last 6 months or so
15:32:29 <adamw> so, who do we have? :)
15:32:33 <adamw> say hi, don't be shy
15:32:39 <kparal> hi
15:32:44 <prakash> Hi
15:32:48 <Vipul_> hello
15:32:58 <Sumantro> Hi vipul and Prakash!
15:33:09 <adamw> kparal: i'm pretty sure you joined longer ago =)
15:33:15 <omiday> hi
15:33:16 <prakash> Hello Sumantro
15:33:27 <Vipul_> hey Sumantro :)
15:33:28 <kparal> adamw: I don't even remember, might have been yesterday
15:33:43 * coremodule is new and coming up to speed, but enjoying it!
15:33:45 <brunowolff> https://lists.fedoraproject.org/archives/list/spins@lists.fedoraproject.org/thread/TIC3JXKQJD23ZAQRHALD2Y3FIKKZ6QZV/
15:33:51 <adamw> kparal: =)
15:34:04 <prakash> Hi Adam :)
15:34:12 <buvanesh_kumar> hi Adam :)
15:34:21 * omiday enjoying it
15:34:31 <adamw> so have you all been finding it possible/easy to get involved, so far? are there any things you've found difficult or not been able to figure out?
15:34:36 <buvanesh_kumar> Hi kparal
15:34:37 <Vipul_> Good to be here :)
15:34:38 <prakash> Hi kparal :)
15:34:53 <Vipul_> yes, it has been a great journey till now.
15:35:02 <buvanesh_kumar> yep
15:35:02 <tflink> is there anything that new folks would like help with?
15:35:13 <prakash> I'm a new comer and its been a great journey till now
15:35:13 <Vipul_> Sumantro is helping us a lot
15:35:15 <prakash> :)
15:35:24 <buvanesh_kumar> i am also new comer :)
15:35:41 <adamw> and do you have any ideas for making things better? :)
15:36:02 <omiday> tflink: I'm still burshing up on Python but could help anything system related
15:36:09 <prakash> I started off on graphical upgrade test day.... Sumantro is mentoring me since then
15:37:07 <tflink> omiday: I'm not sure I understand, is that something you'd like help with?
15:37:08 <Vipul_> Same here, learning everyday
15:37:25 <Sumantro> And all of you guys are doing great with update and release validation tests!
15:37:41 <adamw> yep, it's always great to see more names on the result tables
15:37:46 <omiday> tflink: I pick up whatever comes on mailing list - where else can I look for things to do?
15:37:49 <Vipul_> ThankYou Sumantro
15:38:02 <prakash> Thank you.... Sumantro :)
15:38:18 <Sumantro> I lov
15:38:26 <Sumantro> to mentor
15:38:28 <buvanesh_kumar> Thank you sumantro :)
15:38:29 <Vipul_> And the pleasure of getting in touch with Fedora community is ours Adam :)
15:38:33 <Sumantro> :)
15:39:20 <tflink> omiday: for testing, I think that adamw or kparal will have better answers than I would. I've had my head pretty deep in a test automation hole for a while now
15:39:54 <adamw> omiday: one thing you can always do is update testing, there are pretty much always updates which need karma
15:40:08 <Sumantro_> Tflink can I work on taskatron with you?
15:40:09 <kparal> omiday: you can look into https://qa.fedoraproject.org/blockerbugs/milestone/24/final/buglist to help us reproduce and debug blocker bugs
15:40:14 <buvanesh_kumar> yeah sure :)
15:40:19 <Vipul_> We are working on Update testing too
15:40:20 <adamw> and yep, that's a good one too
15:40:27 <tflink> Sumantro_: sure, there's always stuff to do :)
15:40:51 <omiday> tflink: okay, I'll ping you once I'm ready to start on coding - Adam provide all the info in reply to my self-intro message :)
15:41:07 <tflink> omiday: sounds good
15:41:22 <adamw> tflink: is phab sign-in working again yet?
15:41:24 <Sumantro_> Can i have a poc of taskatron? And I will drop you a mail!!
15:41:33 <tflink> adamw: no idea
15:41:53 <tflink> Sumantro_: poc of taskotron?
15:41:59 <Sumantro_> Also, I have been tweaking with disposable clients
15:42:05 <adamw> tflink: guess i'll try it and yell at you if not...
15:42:11 <tflink> sounds good
15:42:27 <omiday> kparal: I looked yesterday - did 1336810 - all others appears to be in the "need info"?
15:42:29 <tflink> I'm usually operating under the assumption that if something's broken, someone will let me know
15:42:45 * tflink needs to move over to oauth2 before long
15:42:54 <adamw> tflink: i thought you did know, somehow. no biggie
15:43:31 <tflink> adamw: yeah, i know it was kinda broken but then people stopped complaining and I was (naively) hoping that the problem had magically fixed itself
15:43:36 <adamw> =)
15:44:17 <Sumantro_> Yes something which gives a clear idea about the working, installation and setup as its very heavy to work with.. A documentation or walk through will be like really good.
15:44:17 <adamw> so overall, sounds like things are working out pretty well...great. please do send a mail any time you need help with anything or ideas for what to do!
15:44:42 <kparal> adamw: tflink: I think it's this ticket https://phab.qadevel.cloud.fedoraproject.org/T761
15:45:10 <tflink> yep, that fits my memory
15:45:28 <adamw> we've got blocker review in 15 mins, so let's move on to open floor then close things out so we have time to take a break
15:45:39 <adamw> #topic Open floor
15:46:33 <adamw> so, any other business that hasn't been covered yet?
15:47:02 <kparal> nothing here
15:47:06 <tflink> nothing here, either
15:48:54 <brunowolff> #info Discussion on spin-kickstarts move to pagure issue: https://lists.fedoraproject.org/archives/list/spins@lists.fedoraproject.org/thread/TIC3JXKQJD23ZAQRHALD2Y3FIKKZ6QZV/
15:48:56 <adamw> jeez, everyone's so boring
15:49:07 <adamw> :P
15:49:21 <adamw> alrighty then, let's take 10 mins before the blocker review meeting to get whisky
15:49:22 <adamw> i mean coffee
15:49:35 <omiday> coffed with rum
15:49:36 <kparal> or beer
15:49:52 <adamw> whisky with beer
15:49:55 <coremodule> lol
15:50:02 <kparal> adamw: you canadians...
15:50:05 <adamw> blocker review is in #fedora-blocker-review , for anyone who doesn't know - see you there in ten minutes!
15:50:06 <omiday> you go for it adamw :D
15:50:08 <adamw> thanks for coming out, everyone
15:50:14 <coremodule> See ya in a few!
15:50:16 <adamw> hey, today's a public holiday in canada
15:50:22 <omiday> yep
15:50:25 <adamw> <Clerks>i'm not even supposed to BE here today</Clerks>
15:50:32 <omiday> I'm actually on VT until end of month :)
15:51:00 <adamw> #endmeeting