From Fedora Project Wiki

< QA‎ | Meetings
Revision as of 06:03, 21 January 2012 by Adamwill (talk | contribs) (update page with the results of the meeting)

Attendees

  • adamw (171)
  • j_dulaney (57)
  • tflink (54)
  • kparal (37)
  • dgilmore (5)
  • zodbot (4)
  • robatino (4)
  • nirik (2)
  • brunowolff (1)
  • mkrizek (1)
  • cwickert (1)
  • pschindl (1)

Agenda

Previous meeting follow-up

  • Covered in AutoQA update section

FUDCon report / follow-up

  • ARM is clearly now a Big Important Thing
  • We will want to do some best-effort testing on it and try and work it into the validation process somehow for F17
  • It may well be going primary arch at F18, the way things look, so we'll want to be prepared for that
  • The new anaconda UI will not go into F17
  • Anaconda team will push new UI into Rawhide targeted for F18 as soon as it is capable of performing installs
  • Before that, they will start providing test images as soon as external testing will actually be of use to them, with instructions
  • Bugs that got hand-waved in F16 cycle will need to be fixed for F17
  • Bodhi 2.0 should be done REAL SOON NOW
  • In theory proventesters karma should now have special status, but that hasn't been implemented yet
  • pjones wants us to use a tool he wrote to test if images are bootable
  • bcl has a new live media creation tool he wants us to test

AutoQA update

  • Logo has been changed to avoid legal issues
  • kparal reported host of Bodhi/Autotest issues due to which some of our tests currently crashes
  • autoqa-results (again) contains only staging results, we will re-enable production results after we deploy 0.8
  • mkrizek found a probable cause why our koji/bodhi watchers get stuck endlessly from time to time
  • depcheck is no longer scheduled as noarch test in some circumstances. This will be fixed on production only after we deploy 0.8
  • hongqing finished rats_install test and asked for review
  • fudcon: we started looking at what kinds of interfaces and data would be needed to effectively isolate AutoQA for repeatable testing

Open floor

Action items

  • adamw to file trac ticket(s) for getting arm into the criteria / validation process somehow
  • adamw to co-ordinate with bcl on making sure all important old-UI bugs discovered in F16 validation get fixed in the old UI for F17
  • tflink to contact lmacken re co-ordination between bodhi 2.0 and autoqa
  • adamw to get a discussion going with pjones/kparal/hongqing/robatino to decide how we want to do that

IRC Log

adamw #startmeeting Fedora QA meeting 16:01
zodbot Meeting started Mon Jan 16 16:01:05 2012 UTC. The chair is adamw. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:01
zodbot Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:01
adamw #meetingname fedora-qa 16:01
zodbot The meeting name has been set to 'fedora-qa' 16:01
adamw #topic roll call 16:01
adamw morning folks, who's around? 16:01
* tflink is present 16:01
* mkrizek present 16:01
* pschindl is here 16:01
* j_dulaney is recovering from meeting adamw and tflink 16:01
* kparal 16:01
* tflink didn't realize that we were that overwhelming 16:02
adamw i recommend liquor 16:03
* j_dulaney has class this afternoon 16:03
adamw then it'll work for both! 16:03
adamw #topic previous meeting follow-up 16:03
adamw alrighty, we had just the one action item last week: 16:04
adamw "kparal to follow up with spot on the legal questions around the marvin logo" 16:04
adamw looks like you made a change there, kparal? 16:04
kparal I'll cover that in the AutoQA update section 16:04
adamw okay, fair enough 16:05
adamw then let's move right along to... 16:05
adamw #topic FUDCon report / follow-up 16:05
adamw looks like three out of four who were at fudcon are here, so i just thought we could do a quick brain dump on how it went and any cool stuff we picked up there 16:06
adamw I think j_dulaney wants to go first ;) 16:06
j_dulaney I do? 16:06
j_dulaney *dear in headlights look* 16:06
adamw i can go if you like, I was just kidding 16:07
j_dulaney Actually, my most pertinent thing would go in the AutoQA section 16:07
j_dulaney However, we do need to start thinking about release criteria for ARM 16:07
j_dulaney And start working on a test plan; if it goes primary it would be good to have it all ready to go 16:08
adamw yeah, ARM was a big focus of the event 16:08
adamw it seems like there's a general movement towards making ARM a primary arch 16:08
j_dulaney Obviously, most of our criteria should transfer over, but we should research what needs to be changed/added/removed 16:08
adamw so, jlaska was looking at secondary arch release criteria just before he was moved into the cloud, so we could go and pull what he had and start there 16:09
adamw indeed 16:09
adamw anyone interested in taking that, or should I? 16:09
* j_dulaney might could look into it 16:09
j_dulaney Since it looks like I'll be getting an ARM device to play with 16:10
adamw yeah, that was the other neat thing: the arm mafia were giving away very low-cost arm devices at their talk, and j_dulaney got one 16:10
adamw tflink and I should be be able to get them via RH channels, so we should have a decent base of devices for testing 16:11
* tflink also has a panda for armv7 testing 16:11
adamw for me the obvious possible differences for arm will be a) we may care less about desktop functionality (though it sounds like that should actually work okay anyway) and b) deployment is not via anaconda 16:11
j_dulaney tflink is lucky 16:11
j_dulaney adamw: Indeed 16:11
adamw so we'll need to figure how to adapt the validation process to arm deployment 16:11
j_dulaney For now, anyway 16:11
adamw yeah 16:11
adamw if that just means 'check images for platforms X, Y and Z exist and actually deploy correctly' then, hey, it's easier than anaconda testing! 16:12
j_dulaney Indeed 16:12
tflink another question might end up being HW platforms - are we ok with just armv6 and armv7 coverage or do we want to go into more deatail (beagle, panda, rasberry, pogo etc.) 16:13
j_dulaney Although we may want to include deployment instructions in specific test cases for common paltforms 16:13
tflink and at least make sure we have v5, v6 and v7 coverage (not sure how important that is, though) 16:13
adamw i think that's a good q to ask the team, how do they look at it 16:14
adamw what are their goals in that area 16:14
j_dulaney We might want to ask the ARM Sig what hardware is explicitly covered 16:14
tflink there is a list of supported platforms somewhere 16:14
* j_dulaney will liaise with the ARM folks 16:15
tflink I know that trimslice and a couple others aren't supported 16:15
adamw okay 16:15
tflink not yet, anyways 16:16
adamw so yeah, as a summary: arm is clearly now a Big Important Thing, we will want to do some best-effort testing on it and try and work it into the validation process somehow for F17, and it may well be going primary arch at F18, the way things look, so we'll want to be prepared for that. 16:16
j_dulaney Indeed 16:17
adamw j_dulaney: i tell you what, i'll file a ticket to set up a release criteria and validation test process for arm (somehow, no mechanism specified), and cc us all on it 16:17
j_dulaney Alright 16:18
adamw #action adamw to file trac ticket(s) for getting arm into the criteria / validation process somehow 16:18
adamw #info as a summary: arm is clearly now a Big Important Thing, we will want to do some best-effort testing on it and try and work it into the validation process somehow for F17, and it may well be going primary arch at F18, the way things look, so we'll want to be prepared for that. 16:18
adamw okay, aside from arm, who has cool stuff from fudcon to report? 16:18
tflink adamw: do we want to talk about anaconda plans? 16:18
adamw yes we do! 16:19
adamw that's a v. big one 16:19
* tflink has a huge todo list from fudcon 16:19
adamw it is now official that the new anaconda UI will *not* go into F17 16:19
* adamw cracks champagne 16:19
adamw you are all authorized to reduce your gin consumption by 50% 16:19
* j_dulaney is at school, and it's a dry campus 16:19
adamw heh 16:19
tflink adamw: not waiting until it's in fedora for the champagne? 16:19
adamw tflink: no, it not being in f17 is cause enough :) 16:20
adamw #info the new anaconda UI will not go into F17 16:20
tflink the plans haven't been 100% finalized, but the idea will be to start testing the UI w/ rawhide 16:20
adamw clumens says there simply is not enough time to get it done by f17 feature freeze 16:20
tflink hopefully, we'll figure out a way to have a somewhat-stable rawhide tree to build test install images from 16:20
adamw so the broad plan is for it to land in F18, and have it go into rawhide some time pretty early after the F17 branch - long before F17 is actually released 16:21
tflink after F17 branch, I mean 16:21
adamw thanks to no frozen rawhide, we will then have a good long time to test it before F18 goes out 16:21
adamw before the point where the new UI is actually deployable to rawhide, anaconda team are planning to provide test images 16:21
adamw we're a bit handwavy right now on where those will land and how they'll be announced, but they're going to exist. probably. 16:22
adamw at that point the new UI will be very incomplete and may not even be capable of performing an actual install, but the anaconda team will give us guidance on what bits of it should actually be testable, and what testing would be valuable to them. 16:22
adamw once it's vaguely capable of installing a system, it goes into rawhide, and we can test from rawhide just like we always can. 16:23
adamw #info broad plan is for anaconda team to push new UI into Rawhide targeted for F18 as soon as it is capable of performing installs (can be prior to F17 release thanks to NFR). prior to that point, they will start providing test images as soon as external testing will actually be of use to them, with instructions. 16:24
adamw does that about right, tflink / j_dulaney? did I miss anything? 16:24
adamw sound about right* 16:24
tflink that sounds about right to me 16:25
j_dulaney Looks good here 16:25
adamw cool 16:25
adamw any comments/questions/rotten vegetables, anyone else? 16:25
* j_dulaney throws a rotten tomato at adamw 16:26
tflink j_dulaney and I spent some time trying to work out some details on testing AutoQA 16:26
j_dulaney There's your poker payment 16:26
j_dulaney tflink: I was going to bring that up in the AutoQA section 16:26
tflink j_dulaney: k, I'll hold off 16:26
adamw i meant specifically on the anaconda stuff 16:27
adamw i still have a few other things to brain dump on fudcon in general 16:27
* adamw checks to see if the audience have dozed off 16:27
* j_dulaney is awake 16:27
tflink we need to make a list of the bugs that were dismissed as "will be fixed in new UI" for F17 16:27
adamw j_dulaney: oh, and I covered our gamblin' losses, never fear :) 16:28
tflink make a list for F17 for the bugs in F16, rather 16:28
adamw casey wound up ahead $18, ivan was up $2, and the rest of us were broke 16:28
adamw tflink: yup, that's a good one 16:28
j_dulaney LOL 16:28
adamw so we handwaved away a few moderately serious bugs in 16 with 'oh, new UI in 17 anyway' 16:28
tflink the other anaconda stuff I have is details around how we might handle new UI testing 16:28
adamw like bootloader UI stuff 16:29
adamw anaconda team understands we will need to fix those in old UI now it's staying in 17, but we should probably co-ordinate on tracking them all down and making sure none are missed 16:29
adamw i can probably do that since i was probably most involved in that stuff for 16 anyway 16:29
tflink it would be nice to formalize the text mode stuff, too 16:30
* tflink realizes that it won't change for F17 16:30
adamw #action adamw to co-ordinate with bcl on making sure all important old-UI bugs discovered in F16 validation get fixed in the old UI for F17 16:30
adamw tflink: we do have text UI test cases. we just process-hacked them away from being blockers for f16. 16:30
tflink adamw: I was thinking more along the lines of what should be fixed for F17 16:31
j_dulaney Def. the bootloader stuff 16:31
tflink I forgot to write down the exact issue, but there was one in particular that sounded as if it would be fixed 16:32
tflink would/should 16:32
adamw Sorry guys 16:33
adamw did you want to expand on 'how we might handle new UI testing'? 16:33
tflink eventually, yes but I don't think we need to right now 16:33
adamw okay 16:34
adamw sorry, i just dropped for a minute there, flipped the airplane mode switch on my laptop :) 16:34
adamw so, small things I had: lmacken tells us bodhi 2.0 is REALLY GOING TO GET DONE some time soon 16:34
kparal again? 16:34
j_dulaney LOL 16:35
adamw he's been pulled off it for a while, but he's pretty confident he and a new hire will be able to work on it more or less full-time in the near future 16:35
adamw yup, again :) 16:35
kparal do we have the name of the new hire? 16:35
adamw he told me, but I forgot. 16:35
kparal I need names so that I can bother them :) 16:35
adamw not a complete greenhorn, but someone who was already active, apparently 16:35
* tflink makes note to contact lmacken re: potential changes to the bodhi interface that could affect AutoQA 16:35
kparal great 16:35
adamw tflink: good one 16:36
adamw #info Bodhi 2.0 really should be coming Real Soon Now, according to lmacken 16:36
adamw #action tflink to contact lmacken re co-ordination between bodhi 2.0 and autoqa 16:36
* kparal notes: usual 6 months ahead 16:36
adamw i hope not :) 16:36
adamw so vaguely related to that, i got notting to clarify the exact current practical/theoretical status of proventesters 16:37
adamw the theoretical state is, as agreed back at a fesco meeting in november, pt karma should now count for no more than anyone else's: i.e updates require +1 from anyone pre-beta, +2 from anyone post-beta 16:37
adamw the practical state is, pt karma is still needed, as no-one changed bodhi 16:38
adamw fesco did file a ticket but it didn't actually get assigned to anyone, i suggested notting assign it directly to lmacken and then kick his ass 16:38
* nirik notes new hire is Ralph Bean / irc: threebean (unless I am totally mistaken... do confirm, etc, etc) 16:38
kparal nirik: thanks! 16:38
nirik adamw: lmacken said he would bang that change out in the next few days. ;) 16:39
adamw if you want to keep an eye on when the change is actually implemented, see https://fedorahosted.org/bodhi/ticket/653 16:39
adamw #info for proventesters, in theory pt karma should now be the same as anyone else's, but in practice it's still special: follow https://fedorahosted.org/bodhi/ticket/653 to see when it gets changed 16:39
adamw nirik: that sounds correct 16:39
adamw thanks! 16:39
adamw i did ask notting (as a proxy for fesco) to try and make sure that any messaging is 'proventesters is temporarily on hiatus while we figure out a way to use the system more efficiently', not 'proventesters is dead 16:40
adamw because i do think once we get bodhi 2.0, we can do something useful with pt status 16:40
adamw or at least try :) 16:40
j_dulaney Indeed 16:41
adamw let's see, what else... 16:41
adamw oh yeah, i was hoping andre would be here 16:41
adamw robatino: around? 16:41
robatino yes 16:41
adamw coolbeans 16:42
adamw so, this one sounded up your alley 16:42
adamw pjones has most of the bits available so we could write a test, as part of the whole 'release sanity' stuff, to check that built images are actually bootable 16:42
adamw he has a tool which just looks at the el torito stuff from an image and makes sure it ought to be both bios and efi bootable 16:43
adamw in a way it's almost not worth the trouble for TC/RC images, but it shouldn't hard to implement, and we could always use it on nightlies too 16:43
adamw sound like something you'd be interested in? 16:43
robatino not sure i'm qualified for that 16:44
adamw okay 16:44
adamw anyone else interested? 16:44
* j_dulaney has enough 16:45
j_dulaney To keep me busy, that is 16:45
adamw yep 16:45
tflink would it be worth putting in with rats_sanity or mediakit_sanity? 16:45
adamw in autoqa? 16:45
tflink yeah 16:45
adamw possibly? you'd maybe be more qualified to answer that than I :) 16:45
adamw okay, to keep the meeting shortish, let's start a big messy mail thread about it instead 16:46
* tflink passes the buck to kparal or hongqing 16:46
robatino if you have some links, i could take a look 16:46
adamw i'll start up a thread with everyone in it 16:46
kparal let's discuss in autoqa-devel 16:46
adamw #info pjones would like us to use a tool he wrote to automatically check if images are actually bootable 16:46
adamw #action adamw to get a discussion going with pjones/kparal/hongqing/robatino to decide how we want to do that 16:47
adamw it doesn't have to be autoqa necessarily - the sanity stuff we do on TCs/RCs at present isn't, right? robatino just fires off a script 16:47
robatino no, i do that manually, actually 16:47
adamw oh, okay. 16:48
adamw shows what I know! 16:48
adamw anyway, we'll figure it out. 16:48
adamw the other little thing I had, cwickert and red_alert noted it was kind of hard to find and navigate between validation results pages, so i filed a ticket for myself to look at improving that 16:49
adamw ticket is https://fedorahosted.org/fedora-qa/ticket/273 if anyone else wants to contribute ideas / fixes 16:50
cwickert adamw: thanks, I'll try to provide some feedback in the ticket later 16:50
adamw ooh yeah, and bcl has a new tool for building live images 16:51
adamw which i'd vaguely heard about but hadn't looked at very hard 16:51
tflink it's on my list of stuff to look into 16:51
adamw yeah, me too 16:51
tflink it isn't clear whether the official livecd build process will switch to the new tool or not, though 16:51
tflink s/if/when 16:51
adamw sounds like it will require some small changes to the kickstarts, but a potentially bigger thing is it builds the images in virt, not mock 16:52
tflink virt or native 16:52
adamw so you need a virt-capable host, and the koji integration may change 16:52
adamw right 16:52
tflink you don't need a virt-capable host 16:52
adamw well, okay. my impression is he kinda preferred the virt route, though 16:52
tflink true, the native implementation was a compromise 16:52
tflink but my understanding was that if the official liveimages were built with that tool, they would be native instead of virt 16:53
adamw it sounded to me like he wants people who actually build live images to start trying to use it, and that'll help him decide how soon it ought to be used as the default 16:53
adamw so he just wants us to poke it and see what falls off, really 16:53
adamw ahh, now i know why i kinda missed the initial announce and discussion of this 16:54
adamw it got filtered to anaconda-devel which i don't always read... 16:54
brunowolff I have been meaning to test it as well but haven't gotten to it. It is also getting very later to commit to this switch for F17. 16:55
adamw yeah, it kinda is. 16:55
adamw so you can find the initial thread about the tool at https://www.redhat.com/archives/anaconda-devel-list/2011-December/msg00117.html 16:55
adamw if you use livecd-creator at the moment to build live images, go read it and the linked info, and give livemedia-creator a shot, and poke bcl about how it's broken 16:55
adamw #info bcl has a new potential livecd-creator replacement in development, called livemedia-creator. announcement at https://www.redhat.com/archives/anaconda-devel-list/2011-December/msg00117.html . go use it and tell him how it's broken 16:56
dgilmore adamw: the new way is going to need major rewrite to use in koji, so is not likely for a few releases 16:56
adamw dgilmore: ok. 16:56
dgilmore adamw: and not all platforms really support virt 16:57
dgilmore so i hope that they come up with a non virt way to do it 16:57
adamw #info koji integration will be a major change so livemedia-creator will not be used to create the official images for a while 16:57
dgilmore as ive asked and pointed out to them many times 16:57
adamw heh 16:57
adamw well, as tflink noted, seems like native build is now possible or will be 16:57
adamw anyway, not necessary to discuss it now, i just wanted to flag up the tool 16:57
adamw anything else I'm missing? man, fudcon braindumps are hughe 16:58
adamw also huge 16:58
adamw oh, we gave a few talks, the 'get into qa' hackfest was kind of a bust probably as it was the morning after fudpub, and the anaconda / qa hackfest resulted in the outcomes discussed above 16:58
tflink I don't think you're missing anything huge but I'm still going through all my notes 16:59
adamw okay 16:59
adamw let's move on before we all drop dead, anything big we can always discuss next week / on the list 16:59
adamw splitsville! 16:59
adamw #topic autoqa update 17:00
adamw how're we doing on autoqa front? kparal, tflink, take it way 17:01
dgilmore adamw: i just tagged the mass rebuild into the buildroot 17:01
adamw #chair kparal tflink 17:01
zodbot Current chairs: adamw kparal tflink 17:01
adamw dgilmore: yay 17:01
kparal I have a few notes 17:01
kparal 1. New AutoQA logo (again). The Marvin logo had copyright issues, changed to Sherlock Holmes: 17:01
kparal #link https://fedoraproject.org/wiki/File:Autoqa_logo.png 17:01
adamw nice. 17:01
kparal spot said we really couldn't use Marvin because of copyright 17:01
adamw yeah, that's what i figured :) 17:02
adamw #info autoqa logo changed to a sherlock holmes-y image, to avoid legal issues with the first image proposed 17:02
kparal also citing spot 'as sad as it makes me to say it (I'm also a big HHGTTG fan), but Marvin would certainly agree that it was inevitable' 17:02
j_dulaney I asked him about it in person; his response was that it was a very bad idea 17:02
kparal current logo shouldn't pose a problem, holmes copyright expired in 2000 17:02
kparal says wikipedia 17:03
kparal anyway, if you have something better, just make yourself heard 17:03
kparal alright, more news 17:03
kparal 2. Reported host of Bodhi/Autotest issues due to which some of our tests currently crashes. I am devoted to pestering relevant people until they fix it (you can't hide from me, lmacken!) 17:03
kparal unfortunately currently a lot of our tests crashes 17:04
kparal due to incorrectly tagged updates, etc 17:04
j_dulaney We sort of discussed this a bit at FUDCon 17:04
kparal 3. autoqa-results (again) contains only staging results. I will re-enable production results after we deploy 0.8. 17:04
j_dulaney tflink more than me 17:04
kparal j_dulaney: tflink: some more details you want to share? 17:05
kparal about 2) 17:05
j_dulaney tflink: The topic is incorrect bodhi incorrect tagging discussed at FUDCon 17:05
j_dulaney You were more involved than I 17:05
* j_dulaney must go AFK for a minute 17:06
kparal I'll go on and we can come back to it 17:06
kparal 4. mkrizek found a probable cause why our koji/bodhi watchers get stuck endlessly from time to time. The patch should be on its way. 17:06
kparal koji library apparently uses infinite timeout on network sockets 17:06
kparal and sometimes the server just doesn't respond 17:07
kparal it seems 17:07
kparal 5. depcheck is no longer scheduled as noarch test in some circumstances. This will be fixed on production only after we deploy 0.8. 17:07
tflink j_dulaney: incorrect tagging? I don't remember that discussion 17:07
kparal that was just a minor bugfix, but you can see that sometimes in Bodhi in the comments section 17:07
kparal 6. hongqing finished rats_install test and asked for review. I'm currently trying to get an extra bare metal machine to test it out. 17:07
kparal that's all from me 17:08
kparal did I forget something? 17:08
kparal or do you have comments to some of that? 17:08
* kparal supposes the loud silence means 'no' 17:09
j_dulaney tflink: I thought you were talking to lmacken about it 17:09
j_dulaney Maybe it was me, and my memory is exceptionally fuzzy 17:09
* tflink is still organizing thoughts and action items from FUDCon, haven't been thinking as much about AutoQA explicitly the last several days 17:10
tflink j_dulaney: I talked to him a little about some other stuff but not tagging 17:10
adamw kparal: sounds like good fixin' 17:11
j_dulaney tflink: Maybe it was *me* and I can't remember? Anyway, I can't remember what was said 17:11
adamw so, we were gonna put fudcon autoqa stuff in here too? 17:11
j_dulaney adamw: Indeed 17:11
j_dulaney tflink, can you kick this off, since I am now not sure of my sanity 17:11
tflink j_dulaney and I spent some time to figure out what would be needed for an initial self-test setup for AutoQA 17:12
adamw j_dulaney: welcome to where the rest of us have been for months ;) 17:13
tflink we started looking at what kinds of interfaces and data would be needed to effectively isolate AutoQA for repeatable testing 17:13
tflink most of it was pretty high level but we have a start 17:13
* j_dulaney has a list that will be pushed to the ml later this day, once it's sorted out and made presentable 17:13
tflink I think that the next step will be to go through and implement something 17:14
* j_dulaney also has audio of the whole discussion, including tflink's chalkboard scrapings 17:14
adamw mmm....chalk 17:14
tflink iirc, we were going to start with the scheduler and add more once we get that hammered out 17:14
tflink the idea will be to generate pseudo-rpms with rpmfluff and metadata to fill out the bodhi and koji interfaces 17:14
tflink we want to minimize the amount of data we need to configure, so part of this will be determining some sort of configuration format and test specification 17:15
tflink oh, there was a request to change the name of mock_fedorainfra and I'll be doing that before too long 17:16
tflink it needs some refactoring and bugfixes, anywyas 17:16
j_dulaney Essentially, we've got an exceptionally rough idea where to start 17:17
adamw so it's almost done! 17:17
tflink adamw: you have an odd definition of "almost done" 17:17
j_dulaney We've figured out what the hardest bit will be, and sort of figured out how to do it 17:18
adamw tflink: :P 17:18
j_dulaney Anyway, that about covers it 17:18
adamw coolbeans. 17:19
adamw anything else on autoqa? 17:19
tflink nothing concrete 17:19
tflink had some interesting conversations with lmr about autotest features and openqa but that would likely be better to summarize elsewhere 17:20
adamw alright 17:20
adamw #topic open floor 17:21
adamw anything for open floor? anything come up while we were away playing poker^H^H^H^H^H^H^H^H^H^H^H working hard? 17:21
j_dulaney Suger testing 17:23
adamw what about it? 17:24
j_dulaney Somehow, I missed the automated email trac gave out, but probinson poked me about a bunch of changes coming up in Sugar 17:24
j_dulaney A test day has been requested; I haven't had the chance to drop it in the schedule 17:24
adamw ah, okay 17:24
adamw yeah, you should have quite a bundle of test day requests pending 17:24
j_dulaney https://fedorahosted.org/fedora-qa/ticket/270 17:25
j_dulaney But, also: 17:25
j_dulaney http://wiki.sugarlabs.org/go/0.96/Roadmap 17:25
adamw #info there will be some significant sugar changes this cycle 17:25
j_dulaney They're migrating to GTK3 17:25
adamw #info sugar is migrating to GTK+ 3, details and roadmap at http://wiki.sugarlabs.org/go/0.96/Roadmap 17:25
j_dulaney As a result, there is significant rewrites of much of the activities for this cycle; core rewrites will wait for next cycle 17:26
adamw cool. 17:26
j_dulaney That's it for now; I'll ping the ML once I have more info 17:27
adamw thanks 17:27
adamw anything else before we all escape meeting hell? :) 17:27
tflink don't think so 17:28
kparal quick, propose something 17:28
* j_dulaney proposes we adjourn 17:28
* adamw sets fuse quickly 17:28
adamw seconded with feeling! 17:28
adamw thanks for coming to the Great FUDCon Braindump, all 17:28
adamw #endmeeting 17:29

Generated by irclog2html.py 2.8 by Marius Gedminas - find it at mg.pov.lt!

Retrieved from "https://fedoraproject.org/w/index.php?title=QA/Meetings/20120116&oldid=268161"