--- Log opened Wed Feb 25 11:05:01 2009 | ||
wwoods | WOO IT IS TIME FOR A MEETING | 11:05 |
---|---|---|
* jlaska | 11:05 | |
adamw | boo | 11:05 |
* f13 | 11:05 | |
wwoods | let us all don our meeting hats | 11:05 |
wwoods | and taste the excitement | 11:05 |
daumas | my excitement tastes a little stale | 11:06 |
wwoods | anyone else here for the QA meeting? say something for the log | 11:06 |
* adamw gets confused and tastes his hat | 11:06 | |
jwb | hey so... ppc should actually install today | 11:06 |
adamw | mmm...citrus | 11:06 |
wwoods | jwb: wat?! | 11:06 |
jwb | yeah! | 11:06 |
-!- nicubunu [n=nicubunu@mail.apsro.com] has quit ["Fading into sunset"] | 11:06 | |
wwoods | who let that happen | 11:06 |
wwoods | I thought our PPC policy was "ignore it until it goes away" | 11:07 |
jwb | mostly a combination of me beating the kernel to death, jakub fixing gcc, and kylem (aka jkkm) fixing module builds | 11:07 |
* wwoods is kidding, of course | 11:07 | |
jlaska | jwb: that issue is now fixed? | 11:07 |
jwb | X is still buggered, but ajax is fixing that | 11:07 |
* jlaska queues up a cobbler ppc install | 11:07 | |
wwoods | well, let's segue into a pre-Beta blocker discussion | 11:08 |
jwb | jlaska, should be. i at least have a fairly recent rawhide kernel booting on the G5 | 11:08 |
-!- wwoods changed the topic of #fedora-meeting to: Fedora QA | Beta coming | 11:08 | |
jwb | wwoods, yeah, sorry | 11:08 |
wwoods | so when's the beta freeze? | 11:08 |
jwb | 3/3 | 11:08 |
jwb | or somethign like that | 11:08 |
f13 | feature freeze is next Tuesday | 11:08 |
wwoods | and we are currently in the midst of the Mass Rebuild | 11:08 |
f13 | all features should be in a testable point, the week between feature freeze and beta freeze is for fixing last minute feature issues and integration issues | 11:09 |
f13 | as opposed to waiting until the last minute to crash land features. | 11:09 |
jlaska | for the logs ... the full schedule is available at http://fedoraproject.org/wiki/Releases/11/Schedule | 11:10 |
wwoods | Okay! So this is also a good time (and I should have pinged the BugZappers about this) to start putting bugs onto the F11Beta blocker | 11:10 |
f13 | yes yes indeed | 11:11 |
wwoods | and/or pruning bugs from it | 11:11 |
wwoods | https://bugzilla.redhat.com/show_bug.cgi?id=F11Beta | 11:11 |
buggbot | Bug 476774: medium, low, ---, notting@redhat.com, ASSIGNED, Fedora 11 Beta tracker | 11:11 |
wwoods | note that we also have a tracking bug for Intel KMS: https://bugzilla.redhat.com/show_bug.cgi?id=F11IntelKMS | 11:11 |
buggbot | Bug 487202: medium, low, ---, krh@redhat.com, ASSIGNED, F11 Intel Kernel Modesetting driver tracking bug | 11:11 |
wwoods | I don't *think* there's anything else on the radar currently big enough to need its own tracking bug | 11:12 |
jlaska | fyi ... the anaconda storage rewrite change is due for landing next week ... that's likely going going to be disruptive | 11:12 |
wwoods | jwb: so, bug 485067 (which is on the Beta list) should be fixed? | 11:12 |
buggbot | Bug https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=485067 medium, low, ---, jakub@redhat.com, ASSIGNED, rawhide kernel.ppc64 fails to boot on ppc | 11:12 |
adamw | wwoods: possibly nouveau. but that, er, ought to work. | 11:13 |
jwb | wwoods, yes | 11:13 |
jlaska | we've got a custom compose lined up (thanks f13) to get some smoke testing on before it lands in rawhide ... that combined with next weeks test day topic should help reduce the disruption | 11:13 |
wwoods | jlaska: next week's test day will be for the storage rewrite? | 11:13 |
wwoods | should we schedule a video test day for nouveau and intel kms? | 11:13 |
adamw | i was planning on doing an nvidia test day | 11:14 |
adamw | or at least asking ben if he wants to | 11:14 |
jlaska | wwoods: no objections here ... there are test day slots available if we have enough developer and test interest | 11:14 |
adamw | i'm not sure a combined nvidia / intel one is a good idea, it would get noisy | 11:14 |
adamw | since they're different drivers for different hardware maintained by different developers... | 11:14 |
jlaska | for the logs (again) ... the test day schedule is at https://fedoraproject.org/wiki/QA/Test_Days/F11 | 11:14 |
wwoods | fair 'nuff, let's keep those split | 11:14 |
jlaska | adamw: the hardware-based test events (ala bootchart) seemed very successful | 11:15 |
adamw | fwiw i have seen quite a few "i updated rawhide and my graphics broke" posts, and i haven't been looking very hard...so intel does look a bit dodgy. | 11:15 |
adamw | jlaska: yep, seemed to go off well. | 11:16 |
wwoods | yeah, the first pass of KMS kernels was a bit dicey, but yesterday's kernel brought up X on my test machines | 11:16 |
wwoods | so that's shaping up well | 11:16 |
adamw | yeah, the beta should give us a good impression of how it's going | 11:16 |
wwoods | right, the question is whether we want to schedule a test day ASAP and have fixes in *before* Beta | 11:17 |
wwoods | or if it's good enough for Beta as-is | 11:17 |
adamw | hmm. don't really know. maybe we should ask the devs what they think | 11:17 |
f13 | I should note, that fesco needs to make the go / nogo vote on features next week | 11:18 |
-!- EvilBob [n=EvilBob@fedora/bobjensen] has quit [No route to host] | 11:18 | |
-!- themayor [n=jack@dsl081-200-011.nyc2.dsl.speakeasy.net] has quit ["bye bye"] | 11:18 | |
f13 | QA should weigh in soon if things aren't looking good for a feature. | 11:18 |
wwoods | true. we should talk features in a sec | 11:18 |
wwoods | we're kind of drifting around here | 11:18 |
adamw | someone link the feature list? | 11:19 |
adamw | fine, i'll do it | 11:19 |
adamw | https://fedoraproject.org/wiki/Releases/11/FeatureList | 11:19 |
wwoods | last week we reserved time for talking features, discussing "QA group activities + goals discussion", and nitrate | 11:19 |
* jlaska trying to find minutes from last week | 11:20 | |
wwoods | that's http://wwoods.fedorapeople.org/fedora-qa/fedora-qa-20090218.log.html | 11:20 |
wwoods | specifically http://wwoods.fedorapeople.org/fedora-qa/fedora-qa-20090218.log.html#t12:24 | 11:20 |
jlaska | thx | 11:21 |
-!- themayor [n=jack@dsl081-200-011.nyc2.dsl.speakeasy.net] has joined #fedora-meeting | 11:21 | |
wwoods | f13 is definitely right about Features needing attention but that's a big topic so let's put it aside for the moment. It might need its own meeting or something. | 11:21 |
-!- wwoods changed the topic of #fedora-meeting to: Fedora QA | autoqa update | 11:21 | |
wwoods | autoqa update: uh, no real changes in the past week | 11:22 |
wwoods | I've been working on DebuginfoFS (https://fedoraproject.org/wiki/Features/DebuginfoFS) | 11:22 |
wwoods | and pre-Beta testing stuff | 11:22 |
jlaska | wwoods: btw ... would tomorrows Test Day be a time to make use of DebuginfoFS? | 11:22 |
jlaska | </off_topic> | 11:22 |
wwoods | maybe, but we don't have a public debuginfo server | 11:23 |
f13 | well we do have the new mailing list for autoqa results | 11:23 |
f13 | we need to switch qa1 to mail to that list | 11:23 |
wwoods | f13: right - what's the link for the mailman page? | 11:23 |
f13 | and then I can put the post-repo-update watcher in a cron job so that we get regular reports | 11:23 |
f13 | https://fedorahosted.org/mailman/listinfo/autoqa-results | 11:24 |
wwoods | and the plan is to wire up verifytree next, so we at least get *some* early warning for really obviously bogus rawhide trees | 11:24 |
wwoods | like "no boot images" or "no metadata" | 11:24 |
f13 | yep | 11:24 |
f13 | I've got a good start on that | 11:24 |
wwoods | cool! | 11:25 |
wwoods | let me know when you've got it running (or if you need help) | 11:25 |
-!- rbiba [n=radek@nat/redhat/x-7db94c7fe17fcde3] has joined #fedora-meeting | 11:25 | |
wwoods | anything else there? | 11:25 |
f13 | I've been distracted this week (you know, building 8K packages) but yeah. | 11:25 |
-!- laubersm is now known as laubersm_afk | 11:26 | |
-!- mkoci_koca [n=mkoci@nat/redhat/x-b28f1ff124952678] has joined #fedora-meeting | 11:26 | |
f13 | I think we're going to quickly need to refine some of our results output | 11:26 |
f13 | perhaps turning the post-repo-update into something more like spam-o-matic output (like the rawhide reports) where every arch is in one report | 11:26 |
f13 | also the subject of the mails should have some clue about the test params. | 11:26 |
jlaska | are there any next steps for autoqa for next weeks meeting? | 11:26 |
-!- zprikryl [n=zdeny@nat/redhat/x-f17950a1764d33c0] has joined #fedora-meeting | 11:27 | |
zprikryl | hi | 11:27 |
f13 | jlaska: I'd like to have a working example of post-tree-compose | 11:27 |
f13 | at least a watcher that calls autoqa | 11:27 |
jlaska | you've got a ton of work already, how's just the watcher functionality sound? | 11:27 |
f13 | sure | 11:27 |
wwoods | yeah, if the watcher is working, wiring up verifytree is pretty easy | 11:28 |
jlaska | wwoods: anything on your end for autoqa as far as next steps ... or blockers? | 11:28 |
-!- dkovalsk [n=dkovalsk@nat/redhat/x-b055a0020b8751b7] has joined #fedora-meeting | 11:28 | |
wwoods | mostly -ENOTIME | 11:28 |
wwoods | but we'll work on post-tree-compose as time allows | 11:29 |
wwoods | cross your fingers and let's hope for a working verifytree by.. beta release? | 11:29 |
wwoods | should be doable | 11:30 |
wwoods | that's March 24, by the way. | 11:30 |
wwoods | 4 weeks. shouldn't be a problem. | 11:30 |
-!- wwoods changed the topic of #fedora-meeting to: Fedora QA | test case management (nitrate) update | 11:30 | |
wwoods | jlaska: anything to report on nitrate? | 11:31 |
jlaska | sure ... | 11:31 |
-!- spoleeba [n=one@fedora/Jef] has joined #fedora-meeting | 11:31 | |
jlaska | the nitrate development team is focused on meeting some internal deliverable ... so I'm trying to negotiate how we can assist in popping the cork on open-sourcing their process | 11:31 |
adamw | jlaska is being very diplomatic | 11:32 |
jlaska | it's rough getting a project going that wasn't started on fedorahosted (as we probably all know). | 11:32 |
jlaska | I'd like to invest some time+energy into opening up this effort ... but at some point we'll have to go to plan b | 11:33 |
jlaska | (or d) | 11:33 |
-!- DemonJester [n=DemonJes@fedora/DemonJester] has joined #fedora-meeting | 11:33 | |
jlaska | I'm always open to ideas or suggestions on how we can help them transition ... so feel free to hit me up with concerns/ideas | 11:33 |
-!- warren [n=warren@66.187.234.199] has joined #fedora-meeting | 11:34 | |
jlaska | once transitioned, we can start talking about packaging, a demo instance and hosting etc... but my focus for now is the transition | 11:34 |
wwoods | should we shelve that and start moving forward with trying to set up a mediawiki instance with the semantic-mediawiki plugin | 11:35 |
jlaska | sure, we can investigate that in parallel | 11:35 |
jlaska | btw ... semantic mediawiki notes (https://www.redhat.com/archives/fedora-test-list/2009-February/msg00756.html) | 11:35 |
wwoods | I don't think we have the manpower to do those things in parallel | 11:35 |
f13 | jlaska: well, I can put some pressure up my management chain, that might help. | 11:35 |
jlaska | wwoods: let me take an action item to revisit with fcami to ensure the semantic meets his needs. I'd like to find out what we'd need to do from the infrastructure folks to make it work | 11:36 |
adamw | wasn't someone supposed to be doing that last week? | 11:37 |
wwoods | okay then | 11:37 |
adamw | i'm fairly sure that was on the meeting wrap-up | 11:37 |
jlaska | adamw: yes, I took that one ... but didn't follow through :( | 11:37 |
adamw | jlaska: well, if you find you don't have the time this week either, let me know and i'll do it | 11:38 |
jlaska | adamw: okay, I've prioritized that for today ... and we can chat tomorrow | 11:38 |
jlaska | so that's all I have for nitrate update ... unless any other questions/concerns? | 11:39 |
wwoods | none here, let's move on | 11:39 |
-!- wwoods changed the topic of #fedora-meeting to: Fedora QA | "QA group activities + goals discussion" | 11:39 | |
wwoods | jlaska, you wanted to talk about this | 11:40 |
wwoods | there's also the fedora-test-list thread: | 11:40 |
wwoods | https://www.redhat.com/archives/fedora-test-list/2009-February/msg00707.html | 11:40 |
jlaska | thx ... was going to grab that thread | 11:40 |
jlaska | adamw's mail sums it up better than I could ... | 11:41 |
jlaska | I'd like to spend some time outlining some high level objectives for the fedora qa team | 11:41 |
jlaska | the current draft of goals for the team is available at https://fedoraproject.org/wiki/QA/Goals | 11:41 |
jlaska | I don't want to get too fluffy (pie in the sky) with the goals, but certainly want to provide direction on where we'll be focusing the majority of our energy | 11:42 |
jlaska | there's about a million things we {sh,c}ould be doing ... there is only so much time+resource ... so this is meant to capture what the team feels is the most vital to Fedora | 11:43 |
adamw | Making Shit Work | 11:43 |
jlaska | aka M.S.W. | 11:43 |
jlaska | so please feel free to add thoughts/concern/ideas to adamw's thread | 11:44 |
f13 | well, we should be finding broken shit, and poking the maintainer to make it work | 11:44 |
jlaska | I though markmc very constructive comments around the "Increase participation in Rawhide " | 11:44 |
f13 | otherwise we'll find something broken, spend a lot of time fixing it, and not notice the rest of the broken stuff | 11:44 |
wwoods | right, markmc's point, in short, was that keeping around a RawhideBlocker bug is a pretty good idea | 11:45 |
wwoods | (assuming you have a good definition for what qualifies as a Rawhide Blocker) | 11:45 |
jlaska | right on | 11:45 |
adamw | should note that mark mailed me in private to say i just jfdi with regards to evangelizing wider rawhide use, but i'm still not comfortable with that yet. the toe dips i've made into the -devel list are already hairy enough. :) | 11:46 |
jlaska | okay ... that's it from me ... adamw, anypoints I missed? | 11:46 |
f13 | I agree with mark | 11:46 |
adamw | nope, not really. i was quite happy with the responses, tbh | 11:46 |
-!- tibbs [n=tibbs@fedora/tibbs] has quit [Remote closed the connection] | 11:47 | |
jlaska | I gather this (https://fedoraproject.org/wiki/QA/Goals) will be a living document ... but I like to at least have something that gives us direction/guidance | 11:47 |
jlaska | wwoods: that's it for me | 11:47 |
wwoods | the main thing that came out of that discussion that we should be working on is: post-compose checks for rawhide (for serious) | 11:47 |
wwoods | https://fedoraproject.org/wiki/JohnPoelstra/ImproveRawhideF10#Defining_GOOD is a good list of things to check | 11:48 |
adamw | yes, i do think that should be a priority area | 11:48 |
adamw | basically what i like about rawhide is it's the low level | 11:48 |
adamw | it's where everything else comes from | 11:48 |
adamw | fixing stuff in rawhide benefits all releases, spinoffs, rhel, the lot | 11:48 |
adamw | if we're catching brokenness at the point where stuff hits rawhide it will ultimately have a knock-on effect on the quality of stuff that hits everything else | 11:49 |
wwoods | absolutely. it's unquestionably worthwhile. | 11:49 |
jlaska | I should note that if something isn't excplicitly listed as a focus area/goal ... we're likely not going to invest a lot of time there right now | 11:50 |
wwoods | but first we have to get ready for this Feature freeze - including a full distro rebuild, checking features for testability, and landing a couple of features of our own | 11:50 |
wwoods | is there anything else we need to discuss from that thread, or should we start talking about Feature Freeze | 11:51 |
-!- sdziallas [n=sebastia@p57A2BDB7.dip.t-dialin.net] has joined #fedora-meeting | 11:51 | |
jlaska | nothing from me | 11:52 |
wwoods | okay, here we go. | 11:52 |
-!- wwoods changed the topic of #fedora-meeting to: Fedora QA | F11 Features | 11:52 | |
wwoods | http://fedoraproject.org/wiki/Releases/11/FeatureList | 11:52 |
wwoods | there is a *lot* of stuff here. | 11:52 |
wwoods | all of it needs to be testable and have a usable test plan by.. feature freeze? | 11:53 |
wwoods | or beta freeze? | 11:53 |
wwoods | either way, in the next 2 weeks, either they're testable or they get deferred to F12 | 11:53 |
-!- hanthana [n=hanthana@124.43.146.101] has quit ["Leaving"] | 11:53 | |
-!- fab [n=bellet@monkey.creatis.insa-lyon.fr] has quit ["Leaving"] | 11:54 | |
wwoods | (or, in some cases, they'll get extensions, meaning they're allowed to land a bit late) | 11:54 |
jlaska | wwoods: is testable a gut feel, or is there some basic checklist we can apply? | 11:54 |
wwoods | it's a checklist with one item: "can you test this" | 11:54 |
f13 | wwoods: QA should be happy with the state of the feature page by Feature freeze | 11:54 |
f13 | wwoods: if it's in after feature freeze, it's in. It can be bounced any time prior to feature freeze | 11:55 |
wwoods | jlaska: heh, sorry. that wasn't a useful answer. | 11:55 |
wwoods | but it's pretty simple: the "How To Test" section should contain instructions that you (or I or anyone) can follow to confirm that the feature is working as described in the Scope section | 11:56 |
wwoods | if that's not the case, edit the Talk page | 11:56 |
* mkoci_koca bbl | 11:56 | |
jlaska | wwoods: should we use mediawiki categories to list which features have been reviewed | 11:56 |
wwoods | jlaska: indeed we should! | 11:57 |
wwoods | I believe I created a couple | 11:57 |
-!- itamarjp [n=itamar@189-015-176-147.xd-dynamic.ctbcnetsuper.com.br] has joined #fedora-meeting | 11:57 | |
* jlaska wondering if we can put out a call for community QA review ... and use your categories to track | 11:57 | |
adamw | the ones i'd be most iffy about are http://fedoraproject.org/wiki/Features/ControlGroups , http://fedoraproject.org/wiki/Features/AutoFontsAndMimeInstaller and possibly http://fedoraproject.org/wiki/Features/NouveauAsDefault | 11:57 |
wwoods | there isn't even a feature page for Intel KMS | 11:57 |
wwoods | we might need to make one | 11:57 |
adamw | though 1 and 3 are at least easily revertable, they're more or less single-liners to enable / disable | 11:58 |
jlaska | adamw: do these seem like reasonable test day focus areas? | 11:58 |
adamw | the last two, yeah, i'd like to run test days on those. i am iffy about the first because it seems like a big thing that i'd never heard of before and have never seen any discussion of yet either ;) | 11:59 |
-!- inode0 [n=inode0@fedora/inode0] has quit ["Leaving."] | 11:59 | |
adamw | are any of you familiar with it? | 11:59 |
wwoods | aha! https://fedoraproject.org/wiki/Category:QA_approved_feature_pages | 11:59 |
wwoods | also Category:Features_with_incomplete_scope | 11:59 |
jlaska | wwoods: thx | 11:59 |
jlaska | adamw: I'm conceptually familiar with ControlGroups | 11:59 |
adamw | what's the skinny? | 11:59 |
wwoods | We probably need a Category:Features_with_incomplete_test_plan | 12:00 |
jlaska | I can reach out to lwang to see if that's worthy of a test day ... or some alternative focus | 12:00 |
-!- hpachas-PE [n=hpachas@200.37.120.18] has joined #fedora-meeting | 12:00 | |
adamw | jlaska: is it something that would be pretty much harmless if you didn't actually actively use it? | 12:01 |
jlaska | should be | 12:02 |
adamw | if that's the case i'd be less worried about it. | 12:02 |
-!- RodrigoPadula [n=Rodrigo@189.106.145.113] has joined #fedora-meeting | 12:03 | |
adamw | i'll talk to ben about running a nouveau test day | 12:03 |
jlaska | any takers for the AutoFontsAndMime? | 12:04 |
jlaska | or ideas who might be interested in helping organize+drive that | 12:04 |
wwoods | Category:Features_with_incomplete_test_plans created. | 12:05 |
adamw | jlaska: one of the devs posted a vague 'please test this' mail to test-list a few days back | 12:06 |
adamw | jlaska: regarding the autofonts stuff | 12:06 |
jlaska | yeah, mclasen I think | 12:06 |
adamw | jlaska: we could reach out to him to organize an event | 12:06 |
-!- itamarjp [n=itamar@189-015-176-147.xd-dynamic.ctbcnetsuper.com.br] has quit [Remote closed the connection] | 12:07 | |
jlaska | yeah ... that seems best | 12:07 |
-!- tibbs [n=tibbs@fedora/tibbs] has joined #fedora-meeting | 12:07 | |
jlaska | adamw: do you have cycles to send something to mclasen, or should we leave this up for grabs | 12:07 |
adamw | i can do it | 12:07 |
wwoods | yeah, mclasen was reaching out for help on fedora-test-list: https://www.redhat.com/archives/fedora-test-list/2009-February/msg01020.html | 12:07 |
-!- itamarjp [n=itamar@189-015-176-147.xd-dynamic.ctbcnetsuper.com.br] has joined #fedora-meeting | 12:07 | |
adamw | i already did the 'mail ben' bit actually | 12:07 |
adamw | doesn't take long :P | 12:07 |
wwoods | and Fearless Leader mentioned that he's been name-dropping this in interviews and such | 12:08 |
jlaska | adamw: you're too fast :) | 12:08 |
wwoods | so it should be considered as a Big Ticket Item | 12:08 |
adamw | wwoods: yeah, i read that. | 12:08 |
adamw | and again it's something that doesn't require specialist skills or knowledge to test | 12:08 |
jlaska | cool, what else we got looming on the feature front? | 12:08 |
adamw | OK, so i'll poke mclasen and see what we can arrange | 12:09 |
wwoods | ext4 hasn't been scary thus far | 12:10 |
-!- abadger1999 [n=abadger1@65.78.187.8] has quit [No route to host] | 12:10 | |
jwb | it even works on ppc | 12:10 |
wwoods | but we'll see what happens when the LiveCD starts using it | 12:10 |
wwoods | my ppc machine is, uh, actually running btrfs | 12:10 |
jwb | well, that makes one of you | 12:10 |
jwb | :) | 12:10 |
wwoods | because I like to mix and match my crazy-as-hell | 12:10 |
-!- ggruener [n=Gregor@pD9574D2F.dip.t-dialin.net] has joined #fedora-meeting | 12:11 | |
wwoods | gcc 4.4 is getting a nice workout thanks to the Mass Rebuild Of Doom | 12:11 |
wwoods | oh, iBus is new and interesting | 12:11 |
adamw | OK, consider mclasen poked | 12:11 |
-!- abadger1999 [n=abadger1@65.78.187.8] has joined #fedora-meeting | 12:11 | |
* adamw hates input method stuff | 12:11 | |
wwoods | since we change input method frameworks every six months anyway | 12:12 |
wwoods | we should be used to this | 12:12 |
adamw | for mdv i had one japanese guy and one chinese guy and when it broke I just shovelled it off onto them | 12:12 |
-!- Parafeed [n=clive@abbey1.objectsoft-systems.ltd.uk] has quit [Remote closed the connection] | 12:13 | |
wwoods | the Feature List is too big to go through in this meeting, and we don't have an overview page that shows which pages need QA approval/revisit | 12:13 |
jlaska | do we need to think about getting help from fedora-test-list@ for reviewing? | 12:14 |
wwoods | we have a way to mark pages after we look at them but no way to find unmarked pages | 12:14 |
wwoods | that's a prereq for asking for community hel | 12:14 |
wwoods | help | 12:14 |
adamw | more categories? | 12:14 |
jlaska | can always just say ... look at the feature, if it's not in one of the 3 QA review categories ... review it? | 12:14 |
wwoods | Category:Feature_needing_QA_approval? | 12:14 |
* jlaska wonders if mediawiki fuse plugin works | 12:15 | |
wwoods | we've got 37 features in the list | 12:15 |
wwoods | I don't really want to go opening them at random to see which ones need review | 12:15 |
jlaska | would we also want to add [[Category:Feature_needing_QA_approval]] to the feature template for all future features? | 12:16 |
wwoods | Unless there's a better idea I'm just going to put all of them into a new Category:Feature_needing_QA_approval, and.. exactly | 12:16 |
wwoods | in the future features will start in that category | 12:16 |
wwoods | so we shouldn't need to do this again | 12:16 |
wwoods | should probably see what poelcat thinks of this plan | 12:16 |
wwoods | but that seems like the simplest solution for right now | 12:17 |
-!- adrianr [n=adrian@rhlx01.hs-esslingen.de] has joined #fedora-meeting | 12:17 | |
adamw | i heartily endorse this feature and/or lolcat | 12:17 |
jlaska | agreed | 12:18 |
wwoods | okay then! | 12:18 |
wwoods | I'll put all the features in Category:Feature_needing_QA_approval | 12:18 |
wwoods | (well, first I'll create that page) | 12:18 |
wwoods | and then send mail to fedora-test-list asking people to review features in that category | 12:19 |
wwoods | please check https://fedoraproject.org/wiki/Category:Features_with_incomplete_scope | 12:19 |
wwoods | and https://fedoraproject.org/wiki/Category:Features_with_incomplete_test_plans | 12:19 |
wwoods | and make sure the guidelines there are OK | 12:20 |
-!- inode0 [n=inode0@fedora/inode0] has joined #fedora-meeting | 12:20 | |
wwoods | and anyone who's particularly keen to see a feature dropped / updated / accepted should go to the next FESCo meeting to talk about the status of the feature page | 12:20 |
* jlaska back ... laptop just hung | 12:21 | |
jlaska | wwoods: thanks | 12:21 |
-!- tibbs_ [n=tibbs@fedora/tibbs] has joined #fedora-meeting | 12:21 | |
wwoods | this may lead to us needing to discuss better guidelines for QA Review of Feature Pages (tm) | 12:22 |
wwoods | but hopefully it should be pretty obvious | 12:22 |
-!- neverho0d [n=psv@vpn-pool-78-139-211-158.tomtel.ru] has quit [Read error: 113 (No route to host)] | 12:22 | |
wwoods | okay. anything else about F11 Features? | 12:22 |
daumas | there's not enough of them? | 12:23 |
-!- wwoods changed the topic of #fedora-meeting to: Fedora QA | misc. | 12:23 | |
wwoods | there's 37! | 12:23 |
wwoods | that's plenty! | 12:23 |
daumas | :P | 12:23 |
jlaska | wwoods: I agree, going through the motions will help identify any guidelines/doc gaps | 12:24 |
wwoods | anything else we need to discuss that I may have forgotten about?\ | 12:24 |
adamw | test day tomorrow? | 12:24 |
adamw | is everyone happy with the arrangements? | 12:24 |
adamw | well, except that we don't have a working package from the developers yet | 12:24 |
f13 | what's tomorrow's test day? | 12:25 |
jlaska | adamw: rbiba zprikryl ... any thoughts there? | 12:25 |
jlaska | f13: CrashCatcher | 12:25 |
f13 | ah | 12:25 |
jlaska | another for the logs ... https://fedoraproject.org/wiki/QA/Test_Days/2009-02-26 | 12:25 |
-!- jmoskovc` [n=Mozkum@nat/redhat/x-008bc2f54ac5df59] has joined #fedora-meeting | 12:25 | |
-!- tk009 [n=tk009@adsl-074-166-251-205.sip.bct.bellsouth.net] has joined #fedora-meeting | 12:26 | |
jlaska | jmoskovc` too | 12:26 |
jmoskovc` | jlaska: i'm here :) | 12:26 |
jlaska | talking about preparations for tomorrows crash catcher test day. How are you guys making out with having packages available for test? | 12:26 |
wwoods | (interesting! debuginfo data for F10+rawhide, i386+x86_64 ~= 110GB) | 12:26 |
wwoods | (maybe we can have a public debuginfo server after all..) | 12:27 |
jlaska | wwoods: were you expecting worse? | 12:27 |
jmoskovc` | jlaska: working on it :) | 12:27 |
wwoods | jlaska: yes - we were expecting ~350-500GB | 12:27 |
jlaska | wwoods: ouch | 12:27 |
adamw | jmoskovc`: are you guys happy with my re-arrangement of the test day page? | 12:28 |
jmoskovc` | adamw: dunno haven;t seen it yet :) | 12:28 |
adamw | ah. :) well, really i just turned 'how to test' into a proper test case and linked to it | 12:29 |
adamw | there's also a placeholder link for the package in the text | 12:29 |
zprikryl | adamw: thanks :-) | 12:29 |
adamw | so you just need to stick the URL into that once it's available | 12:29 |
wwoods | unfortunately wdfs is a crappy fuse-webdav implementation for this purpose - AFAICT it downloads the entire data file rather than seek()ing into it, and then it doesn't cache the downloaded data | 12:29 |
jlaska | we've got a table to collect app-specific results if desired | 12:29 |
adamw | is it likely that crashcatcher's behaviour will be significantly different for different apps? | 12:29 |
-!- tibbs [n=tibbs@fedora/tibbs] has quit [Remote closed the connection] | 12:30 | |
adamw | i.e. is it realistically likely that it'll work with some apps but not others? | 12:30 |
adamw | or is that one of the things we need to find out? :) | 12:30 |
jlaska | I was leaning towards the later | 12:30 |
-!- neverho0d [n=psv@vpn-pool-78-139-211-168.tomtel.ru] has joined #fedora-meeting | 12:30 | |
zprikryl | adamw: it should work with all apps :-) (unless an app is in a package which is in the blacklist) | 12:31 |
-!- RodrigoPadula [n=Rodrigo@189.106.145.113] has quit [Read error: 110 (Connection timed out)] | 12:31 | |
-!- tibbs_ is now known as tibbs | 12:31 | |
jlaska | jmoskovc` is opening up a package review bugzilla for crash-catcher now ... is there a list or channel we can ask for review help? | 12:31 |
f13 | #fedora-devel | 12:32 |
adamw | -devel i guess? | 12:32 |
jlaska | thx | 12:32 |
jlaska | anything else to discuss under "misc" ? | 12:34 |
wwoods | I think we're good | 12:34 |
-!- drago01 [n=linux@chello062178124130.3.13.univie.teleweb.at] has quit [Read error: 110 (Connection timed out)] | 12:34 | |
wwoods | a quick recap of decisions / actions: | 12:34 |
hondra | jmoskovc`, is is possible to test CC in console (no X environment) ? | 12:34 |
wwoods | - jlaska (and/or adamw) to talk to fcami and Infrastructure about the semantic mediawiki plugin | 12:35 |
zprikryl | hondra: yes | 12:35 |
hondra | zprikryl, so it can be maybe aded to the testcases ? | 12:35 |
adamw | hondra: "test it with every app you have installed" is kind of a big test case :) | 12:35 |
zprikryl | hondra: but only in debugmode and no all functions are available | 12:35 |
jlaska | adamw: perhaps we can identify a class of apps | 12:36 |
jlaska | text / gui / servers / dbs etc... ? | 12:36 |
adamw | jlaska: i'd mostly want to get tests with every big app that crashes a lot | 12:36 |
jmoskovc` | jlaska: try smth with small coredump and smth with really big coredump :) | 12:36 |
wwoods | - autoqa "post-tree-compose" watcher and verifytree tests are top priority for autoqa (but f13 / wwoods are busy) - target completion date March 24 | 12:36 |
adamw | jlaska: i.e. firefox, evolution, openoffice, stuff everyone runs | 12:36 |
-!- fab [n=bellet@bellet.info] has joined #fedora-meeting | 12:36 | |
jlaska | yeah, that's a great approach | 12:36 |
-!- fabian_a [n=fab@84-75-175-165.dclient.hispeed.ch] has joined #fedora-meeting | 12:37 | |
wwoods | - Rawhide is still awesome | 12:37 |
-!- kirkz [n=kirk202@71-219-108-3.slkc.qwest.net] has quit ["Leaving"] | 12:37 | |
-!- kirkz [n=kirk202@71-219-108-3.slkc.qwest.net] has joined #fedora-meeting | 12:37 | |
zprikryl | adamw: you'll wait a long time because of installation of debuginfos, at the begining, try smth smaller | 12:37 |
* jlaska digesting summary | 12:37 | |
wwoods | - good luck to viking-ice in his archery competition | 12:37 |
wwoods | - wwoods to create Category:Feature_needing_QA_approval and put all unreviewed Feature pages into that category | 12:37 |
-!- fugolini [n=francesc@host138-199-dynamic.17-87-r.retail.telecomitalia.it] has joined #fedora-meeting | 12:37 | |
hondra | zprikryl, what about different setup/configuration of CC, are there any possibilities (does it make sense) ? | 12:38 |
wwoods | - wwoods to email fedora-test-list asking for help reviewing pages in Category:Feature_needing_QA_approval | 12:38 |
-!- balor [n=balor@gimili.plus.com] has joined #fedora-meeting | 12:38 | |
hondra | adamw, I meant GUI vs TUI - the testcase is designed to run in GUI | 12:38 |
zprikryl | hondra: there are several options for CC and for CC's plugins | 12:38 |
adamw | hondra: oh, yes, missed that flow :) | 12:39 |
wwoods | - Test days for intel KMS, nouveau, AutoFontsAndMimeInstaller (dates TBD) | 12:39 |
adamw | if you guys want to do a quick summary of this discussion about different facets of CC that need testing, i can turn it into testcases | 12:39 |
adamw | just drop me an email or throw it in the wiki somewhere or something | 12:39 |
wwoods | anything else from the meeting for the summary? | 12:40 |
-!- lfoppiano [n=lfoppian@fedora/lfoppiano] has quit [Read error: 60 (Operation timed out)] | 12:40 | |
jlaska | wwoods: you got all the points I recall ... thanks for summarizing | 12:40 |
hondra | zprikryl, then we can test several different configurations, are you able to upload some conf files? | 12:40 |
wwoods | okay then - meeting's over, but please feel free to continue the CC discussion | 12:41 |
--- Log closed Wed Feb 25 12:41:28 2009 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!