| --- Log opened Wed Dec 10 11:05:57 2008 | ||
| -!- wwoods changed the topic of #fedora-meeting to: Fedora QA meeting | init | 11:06 | |
| -!- mether [n=sundaram@122.169.3.61] has joined #fedora-meeting | 11:06 | |
| -!- openpercept [n=openperc@unaffiliated/openpercept] has joined #fedora-meeting | 11:06 | |
| wwoods | f13, jds2001, jlaska, poelcat: ping | 11:06 |
|---|---|---|
| wwoods | anyone else who's around for the QA meeting say "hello" for the logs | 11:06 |
| * f13 | 11:06 | |
| * jds2001 | 11:06 | |
| jwb | wwoods, i have a quick question for QA | 11:07 |
| wwoods | jwb: what's that? | 11:07 |
| jwb | https://www.redhat.com/archives/fedora-qa-list/ | 11:08 |
| wwoods | dead | 11:08 |
| wwoods | ignore | 11:08 |
| * viking_ice_ here | 11:08 | |
| wwoods | fedora-test-list | 11:08 |
| wwoods | is the list you want | 11:08 |
| wwoods | kthxbye | 11:08 |
| jwb | can it be removed? | 11:08 |
| wwoods | sure, if you know how | 11:08 |
| -!- mbonnet [n=mikeb@c-76-19-115-225.hsd1.ma.comcast.net] has quit [Read error: 60 (Operation timed out)] | 11:08 | |
| * jwb goes to file infrastructure ticket | 11:08 | |
| -!- mbonnet [n=mikeb@c-76-19-115-225.hsd1.ma.comcast.net] has joined #fedora-meeting | 11:09 | |
| -!- spoleeba [n=one@fedora/Jef] has quit ["Leaving"] | 11:09 | |
| wwoods | it turns out to be really unhelpful to separate "testers" from "qa" | 11:09 |
| wwoods | which should have been obvious in the first place | 11:09 |
| wwoods | but oh well, lesson learned | 11:09 |
| -!- Gaaruto [n=Gaaruto@fedora/Gaaruto] has quit [Remote closed the connection] | 11:09 | |
| wwoods | okay so. agenda is here: https://www.redhat.com/archives/fedora-test-list/2008-December/msg00297.html | 11:10 |
| viking_ice_ | hehe first post in a year.. | 11:10 |
| wwoods | 1st item: review CommonBugs | 11:10 |
| wwoods | https://fedoraproject.org/wiki/Common_F10_bugs | 11:10 |
| -!- wwoods changed the topic of #fedora-meeting to: Fedora QA meeting | https://fedoraproject.org/wiki/Common_F10_bugs | 11:11 | |
| wwoods | look over the list; is anything missing? are any of these fixed? | 11:12 |
| f13 | I wonder if it's worth temporarily putting up the broken PackageKit and broken deps bugs | 11:13 |
| wwoods | yeah, might be worthy | 11:13 |
| wwoods | anyone have a good summary of the problem / link to bug report? | 11:13 |
| jds2001 | and the dbus stuff, but I think that's fixed already, right? | 11:13 |
| -!- leitz [n=leitz@adsl-068-209-163-224.sip.clt.bellsouth.net] has joined #fedora-meeting | 11:14 | |
| f13 | jds2001: provided the last updates push didn't result in broken deps | 11:14 |
| f13 | the jury is still out, I'm told the last push did "weird things" | 11:14 |
| wwoods | the last push itself, or the last-pushed package did? | 11:15 |
| -!- Gaaruto [n=Gaaruto@fedora/Gaaruto] has joined #fedora-meeting | 11:15 | |
| wwoods | nobody? I know nothing about this bug | 11:18 |
| f13 | the last push itself | 11:18 |
| f13 | which finished sometime yesterday evening | 11:18 |
| wwoods | f13: ah, that's less-bad then | 11:18 |
| f13 | but still don't know if all is well | 11:18 |
| wwoods | can you summarize the problem? or point me at a bugzilla bug? | 11:19 |
| f13 | man there are a bunch. | 11:20 |
| f13 | actually walters would be the best person for that | 11:20 |
| jds2001 | http://tinyurl.com/dbusbug http://tinyurl.com/dbusbluez | 11:20 |
| jds2001 | that's what's in the topic of #fedora right now. | 11:20 |
| nirik | dbus security update, breaks all dbus using apps including PackageKit. | 11:20 |
| wwoods | *all* of them? zang | 11:21 |
| nirik | new PK pushed out, but still other apps have issues (although many of them are fixed now, but it's unclear) | 11:21 |
| ivazquez | And the fixes are in varying states of "pushed". | 11:21 |
| wwoods | I thought it just bonked PK | 11:21 |
| nirik | also some system-config* and a report of NM, and... | 11:21 |
| ivazquez | avahi | 11:22 |
| wwoods | jds2001: do you want to summarize for CommonBugs or should I ask walters | 11:22 |
| -!- JSchmitt [n=s4504kr@fedora/JSchmitt] has quit [Remote closed the connection] | 11:22 | |
| -!- nphilipp [n=nils@155.56.40.12] has quit [Read error: 145 (Connection timed out)] | 11:22 | |
| jds2001 | wwoods: i would ask walters since I really don't feel qualified to summarize that. | 11:23 |
| wwoods | 'kay | 11:25 |
| wwoods | I'll ask him | 11:25 |
| wwoods | and, for the record: no amount of magical QA sauce would have helped here, since the developer(s) decided to skip the entire QA process | 11:26 |
| wwoods | walters knows this, no need to hurl further blame | 11:26 |
| viking_ice_ | So the flaw lies in the process.. | 11:26 |
| wwoods | the QA process is supposed to be *technically* optional but you're not supposed to skip it unless you have a really damn good reason | 11:27 |
| * nirik notes that he is the one who approved it from security... but even if I had tested it I wouldn't have seen the issue, as I don't use packagekit and seldom use system-config-* | 11:27 | |
| wwoods | and you're 100% sure you're not going to break anything | 11:27 |
| f13 | the QA blame, or maybe the infrastructure / releng blame, does come into play with the resulting broken deps of PackageKit and gnome-apckagekit | 11:27 |
| wwoods | if you skip the process, you accept responsibility for the outcome | 11:28 |
| f13 | I talked with the board about this yesterday because the issue came up | 11:28 |
| wwoods | but yes, some amount of automated checking of deps would still be great | 11:28 |
| f13 | and I'm charged with getting something in place this release cycle | 11:28 |
| viking_ice_ | no but it points if further restrictions are perhaps necessary.. | 11:28 |
| f13 | so I'm going to be working with lmacken, skvidal, the QA group, and well myself to get /something/ in place to help developers from shooting themselves in the foot with broken deps | 11:29 |
| f13 | viking_ice_: I really don't think more hurdles and red-tape is really the answer. | 11:29 |
| jds2001 | me either. This can be solved technically. | 11:29 |
| viking_ice_ | ok | 11:30 |
| wwoods | no, the real upshot of this problem is: 1) it is very damn clean to everyone that you should NOT skip the updates-testing phase | 11:30 |
| wwoods | and 2) we really do need some kind of automated dep checking in bodhi etc. | 11:30 |
| wwoods | both of which we knew beforehand | 11:31 |
| nirik | so can security updates go to testing? I know at one point they automagically went to stable. We should confirm that they can go to testing at least. | 11:32 |
| viking_ice_ | Could we not make every package to have a time in updates-testing just some minimum? | 11:32 |
| f13 | I don't think so | 11:32 |
| viking_ice_ | Sec updates stay for 6 perhaps 12 hours.. | 11:32 |
| wwoods | security updates generally need to go out as quick as possible, which is why we allow people to skip the testing phase *if* they are *really* sure they know what they are doing | 11:32 |
| f13 | (to forcing things into -testing) | 11:32 |
| wwoods | generally the security team knows what they're doing | 11:32 |
| f13 | I think at this point it's the submitters who decide where it goes | 11:33 |
| f13 | not the security team | 11:33 |
| ivazquez | I don't think this was decided by the security team. | 11:33 |
| wwoods | so forcing them to go through extra work for the 98% of the time when they get everything right | 11:33 |
| f13 | the security team just verifies that the security info is accurate | 11:33 |
| wwoods | just to avoid the 2% of the time when they get it wrong | 11:33 |
| wwoods | is not useful | 11:33 |
| wwoods | it just slows down our security updates | 11:33 |
| nirik | yeah, it's submitter and/or bodhi that determines that, not security team | 11:34 |
| viking_ice_ | slight delay on sec updates vs potential broken system | 11:34 |
| wwoods | false-positive paradox. it means we slow down all good updates unnecessarily, and doesn't even guarantee that we'll catch the bad ones. | 11:34 |
| wwoods | it's not useful. | 11:34 |
| wwoods | it's more useful to provide better tools for testing | 11:35 |
| -!- abadger19991 is now known as abadger1999 | 11:35 | |
| wwoods | so the security team (et. al.) can be *more* sure that the update is OK, and test stuff *faster* | 11:35 |
| wwoods | rather than slowing everything down | 11:35 |
| wwoods | the answer is better tools and clearer docs for testing, not forced delays on all packages | 11:37 |
| wwoods | anyway. ACTION: wwoods will talk to walters about the dbus bug and update Common_F10_Bugs appropriately | 11:38 |
| wwoods | any further discussion on that? | 11:38 |
| * nirik would like to have a fudcon session about security and updates...if the approval is usefull and what exactly should be checked, but thats possibly another topic. | 11:38 | |
| -!- Kick__ [n=karsten@p54A3C740.dip.t-dialin.net] has quit [Connection timed out] | 11:38 | |
| -!- Kick__ [n=karsten@p54A3C740.dip.t-dialin.net] has joined #fedora-meeting | 11:39 | |
| -!- jsmith [n=jsmith@asterisk/training-and-documentation-guru/jsmith] has joined #fedora-meeting | 11:39 | |
| wwoods | nirik: definitely worth discussing at FUDCon - viking_ice_ and I have been talking a lot about getting test plans/scripts into the wiki and/or package CVS | 11:39 |
| wwoods | but that's a big topic and we'll cover it some other time | 11:39 |
| wwoods | next agenda item, then | 11:40 |
| -!- wwoods changed the topic of #fedora-meeting to: Fedora QA | automated installer testing | 11:40 | |
| wwoods | yes, once again, automated installer testing. | 11:40 |
| wwoods | Here's what we've been working with: https://fedorahosted.org/snake/ | 11:40 |
| wwoods | the goal, for a long time now, has been: automated nightly smoke tests of rawhide | 11:41 |
| -!- stickster is now known as stickster_afk | 11:41 | |
| -!- hanthana [n=hanthana@124.43.34.236] has quit [Read error: 113 (No route to host)] | 11:41 | |
| wwoods | this is going to require a special lab setup (which I'm putting together here) | 11:42 |
| wwoods | hardware's the easy part | 11:42 |
| wwoods | the hard part is getting the software to do what you want | 11:42 |
| jds2001 | OK, why not in PHX? (just curious) | 11:42 |
| wwoods | it could be in PHX but that's irrelevant | 11:42 |
| wwoods | hardware is easy | 11:42 |
| wwoods | and I dunno if we have space in PHX | 11:43 |
| f13 | well, hardware outside of PHX is easy (: | 11:43 |
| * leitz wonders what PHX is. | 11:43 | |
| viking_ice_ | Link to PHX please.. | 11:43 |
| f13 | wwoods: we're supposed to talk to mmcgrath about QA resources in our PHX colo at FUDCon | 11:43 |
| wwoods | (PHX is our colocation facility in Phoenix) | 11:43 |
| leitz | Ah, Pheonix. | 11:43 |
| f13 | PHX is where koji lives, and where all the Fedora packages live | 11:43 |
| wwoods | PHX = "public Fedora infrastructure" | 11:43 |
| f13 | and it's where the rawhide composes happen, so it's a logical place for the rawhide testing to happen. | 11:44 |
| wwoods | but the point of snake is to have something that you can run anywhere | 11:44 |
| wwoods | this should work so long as you have power control - either a remote power adapter or, you know, sitting next to the machine and flipping the switch | 11:44 |
| leitz | Might be better to not have it in PHX so there's less chance of something escaping and busting production. | 11:44 |
| wwoods | and a way to restore a dead machine - either PXE-booting an automatic install or just installing from a LiveCD | 11:45 |
| f13 | leitz: it can be isolated. | 11:45 |
| wwoods | the point is that this will run *somewhere* - and it doesn't matter where - and that will generate logs | 11:45 |
| wwoods | that people can inspect | 11:45 |
| f13 | nod | 11:45 |
| jds2001 | yeppers | 11:45 |
| wwoods | and it will color some boxes green or red | 11:45 |
| f13 | in fact, it should be ran in as many places as possible (: | 11:45 |
| wwoods | and that's how we'll know if rawhide is broken | 11:45 |
| jds2001 | well, we'll know it installs and boot | 11:46 |
| wwoods | right | 11:46 |
| wwoods | so for that specific definition of "broken" | 11:46 |
| jds2001 | whether or not it does anything useful is another thing entirely :) | 11:46 |
| wwoods | anyone who knows python or has some spare machines and disk space | 11:46 |
| wwoods | and wants to work on automatic install stuff | 11:47 |
| * jds2001 has the latter and a little of the former | 11:47 | |
| wwoods | should definitely email me or come to #fedora-qa and we'll talk about trying to set up a snake-server and what needs doing | 11:47 |
| wwoods | I think that's going to be my primary goal between now and, say, F11Alpha | 11:48 |
| * jds2001 already has a snake-server, but it's on an F8 machine :P | 11:48 | |
| f13 | given that I have a local mirror, cobbler setup, and the ability to manually control power, my office is a good candidate for doing such tests | 11:48 |
| f13 | mostly I've been doing the tests in virt | 11:48 |
| viking_ice_ | wwoods; cant you create a step by step how to ( thinking materal for testing advanced/expert ) | 11:48 |
| wwoods | AFAIK there are teams inside RH working on some of the other stuff I've been messing with - CrashHandling, test reporting, etc. | 11:48 |
| jds2001 | f13: my "office" is similar, but no cobbler | 11:49 |
| jds2001 | manually controlled PXE and all that, though, so cobbler wouldn't be hard | 11:49 |
| wwoods | viking_ice_: https://fedorahosted.org/snake/wiki/SnakeExamples/ServerSetup etc. | 11:49 |
| f13 | ah codeina | 11:49 |
| f13 | er | 11:49 |
| wwoods | cobbler is kind of weird for QA | 11:50 |
| viking_ice_ | wwoods: step by step from a to b | 11:50 |
| wwoods | it's awesome for datacenters and such | 11:50 |
| wwoods | but when you want to install a new distro every day it doesn't really work the way you want | 11:50 |
| wwoods | but it's probably the best way to set up the fallback stuff | 11:51 |
| f13 | wwoods: how's that? | 11:51 |
| f13 | cobbler works great for me to fire up virt guests like crazy | 11:51 |
| f13 | new one every day | 11:51 |
| -!- hadess [n=hadess@cpc1-glfd1-0-0-cust325.glfd.cable.ntl.com] has joined #fedora-meeting | 11:52 | |
| wwoods | a virt guest install of rawhide? | 11:52 |
| f13 | yep | 11:52 |
| wwoods | well heck | 11:52 |
| f13 | using koan | 11:52 |
| wwoods | maybe I should reexamine cobbler | 11:52 |
| f13 | sudo koan --server localhost --virt --profile=rawhide-http-x86_64 --virt-path /dev/data/rawkvm --virt-name rawkvm | 11:52 |
| * jds2001 was more using snake to to that | 11:53 | |
| wwoods | last time I looked - and that was more than a year ago - it wasn't well-suited to what we wanted to do | 11:53 |
| f13 | the only extra step to do would be: virsh undefine rawkvm | 11:53 |
| jds2001 | but even that requires doing a snake-tree update all every day | 11:53 |
| jlaska | you can use both :) | 11:53 |
| f13 | that removes the libvirt entry for "rawkvm" so that it can be re-created the next day | 11:53 |
| jlaska | I'm trying tou outline how I'm doing it at http://jlaska.livejournal.com/tag/cobbler | 11:53 |
| f13 | my cobbler setup has profiles for rawhide-{http,nfs}-{i386,x86_64} | 11:54 |
| f13 | and I can add profiles easily based on these that have different package sets, different partitioning, etc... | 11:54 |
| f13 | all very very easy to manage | 11:54 |
| viking_ice_ | wwoods: if you create some doc ( set up a snake-server or just copy/paste and send me) discussion I got my hands full coming up with ext4 testing docs which will end as "how to test a posix filesystem" | 11:55 |
| viking_ice_ | irc discussion | 11:55 |
| leitz | Is it feasible to snake/cobbler from a remote host? | 11:55 |
| wwoods | f13: yeah, I have to revisit cobbler then | 11:55 |
| f13 | leitz: well, my cobbler box is "remote" | 11:56 |
| wwoods | last I looked at it, it wanted to create a local copy of the distribution and wanted me to recreate the profile daily or something | 11:56 |
| f13 | leitz: as in it sits in my office without a head | 11:56 |
| f13 | leitz: I ssh into it to launch koan, and then use virt-manager on my laptop to connect to the libvirt on the cobbler box and view the guest vi vnc | 11:56 |
| f13 | via vnc | 11:56 |
| f13 | wwoods: it grew the ability to have --available-as=nfs://blah | 11:57 |
| f13 | or --available-as=http://blah | 11:57 |
| leitz | f13: I'm probably giong to decomission the old servers I have at my feet, so the question is, can I do testing on this from someone else's machines? | 11:57 |
| -!- kital [n=Joerg_Si@fedora/kital] has joined #fedora-meeting | 11:57 | |
| wwoods | well, hey, I'll be happy if cobbler has grown all the stuff we need to deal with automated installs | 11:57 |
| wwoods | less work for me | 11:57 |
| f13 | wwoods: we should talk at FUDCon | 11:58 |
| wwoods | okay. ACTION: reinvestigate cobbler as an automated installer tool | 11:58 |
| wwoods | if that works, we just need remote logging (which we can do a bunch of different ways) | 11:58 |
| viking_ice_ | snake or cobbler.. | 11:58 |
| f13 | oh it has that | 11:58 |
| jlaska | sort of | 11:58 |
| f13 | it uses syslog to log everything back to the cobbler host | 11:58 |
| -!- JSchmitt [n=s4504kr@fedora/JSchmitt] has joined #fedora-meeting | 11:58 | |
| wwoods | jlaska: I assume you've looked at this more recently than I have | 11:58 |
| jlaska | yup | 11:59 |
| jds2001 | wwoods: he has a whole set of blog entries on it! :) | 11:59 |
| wwoods | whee | 11:59 |
| wwoods | okay I'll do some reading and we'll talk more about this next week | 11:59 |
| wwoods | and I may get the itch to prototype something new | 12:00 |
| wwoods | because I was never happy about reinventing the wheel in SNAKE | 12:00 |
| wwoods | ugh, gotta get some hardware that'll do KVM | 12:00 |
| wwoods | stupid BIOS-disabled intel box | 12:00 |
| viking_ice_ | jlaska: nice.. | 12:01 |
| wwoods | we'll talk more about cobbler in the coming weeks, I'm sure | 12:01 |
| jlaska | more to come :) | 12:01 |
| f13 | wwoods: doesn't RDU have an intel critter running around? | 12:01 |
| f13 | wwoods: who delivers magical sdv boxes? | 12:02 |
| wwoods | f13: probably, but I've had my fill of SDV wonkiness | 12:02 |
| f13 | heh | 12:02 |
| wwoods | I want some actual production hardware | 12:02 |
| wwoods | heh | 12:02 |
| wwoods | anyway. reinvestigating cobbler for automated installs. whee! | 12:03 |
| wwoods | anything else on the topic of automated install testing? | 12:03 |
| f13 | not much, other than I need to see if rawhide is working again | 12:03 |
| viking_ice_ | first settle on a test system then let's extend.. | 12:04 |
| -!- No5251 [n=No5251@p50990d02.dip0.t-ipconnect.de] has quit [Read error: 110 (Connection timed out)] | 12:04 | |
| wwoods | yeah, last I checked it was a little nasty in rawhideland | 12:04 |
| f13 | well I fixed the mkinitrd fallout | 12:04 |
| wwoods | viking_ice_: right, we'll research the options and pick some way to do the installs ASAP | 12:04 |
| wwoods | oh, and I still need to talk to the wiki folks about the QA: wiki namespace | 12:05 |
| f13 | I just didn't sync yesterday or the day before to see if things started working | 12:05 |
| f13 | oh right | 12:05 |
| f13 | we got images, we were justmissing squashfs in the kernel, which we shold have today | 12:05 |
| leitz | wwoods: Am I correct in thinking Snake *or* Cobbler? Are the supplementary or does one replace the other for what you need? | 12:05 |
| wwoods | I had a trac ticket for that once, dunno if it's been closed or if it's just fallow | 12:05 |
| wwoods | leitz: they're basically the same idea, yeah | 12:05 |
| wwoods | jlaska and I started writing SNAKE around the same time as Cobbler, and we keep talking to mpdehaan (Cobbler author) about it | 12:06 |
| wwoods | and we always came to the conclusion that we were doing approximately the same thing, but there wasn't any clear way to merge the projects | 12:06 |
| wwoods | or share code | 12:06 |
| f13 | one area I think snake has in favor | 12:06 |
| jlaska | I'm using snake to build the kickstarts still | 12:06 |
| f13 | is that there is a snake client that can setup an already installed system when said system isn't on the same PXE network as the cobbler box | 12:06 |
| -!- fab [n=bellet@monkey.creatis.insa-lyon.fr] has quit ["Leaving"] | 12:07 | |
| wwoods | hrm. wonder if you could do that with cobbler | 12:07 |
| f13 | it should be easy if you can reach teh cobbler server | 12:08 |
| f13 | to query where the vmlinuz and initrd could be found and grabbed | 12:08 |
| f13 | maybe this already exists for cobbler and I missed it | 12:08 |
| f13 | (I wasn't looking closely) | 12:08 |
| wwoods | I'll check into that | 12:08 |
| jlaska | f13: run koan on the client? | 12:08 |
| f13 | jlaska: koan is for virt through isn't it? | 12:08 |
| jlaska | nope | 12:08 |
| jlaska | both | 12:08 |
| f13 | ah, well, there you go | 12:09 |
| leitz | wwoods: Would your time be better spent merging into Cobbler then moving on to the rest of your task load? | 12:09 |
| wwoods | leitz: I keep thinking that, yeah | 12:09 |
| wwoods | it wasn't feasible in the past, though | 12:09 |
| wwoods | might be time now | 12:09 |
| wwoods | I liked messing with SNAKE but I'd be happy to have less code to worry about maintaining | 12:10 |
| wwoods | so I'll bug jlaska for some cobbler/koan help and try to prototype that this week | 12:10 |
| wwoods | and we'll see how it goes | 12:10 |
| wwoods | woo, exciting! | 12:11 |
| wwoods | anything else about automated installs? | 12:11 |
| wwoods | I think we defined the basic rawhide test goals at the last Boston FUDCon | 12:12 |
| wwoods | I'll need to see if I can find those again. it's pretty obvious: does it boot? | 12:12 |
| f13 | yeah, we just need something to run on the host or in the %post that says pass or fail. | 12:12 |
| wwoods | but it's nice to have an explicitly documented set of goals. | 12:12 |
| jlaska | https://fedoraproject.org/wiki/JohnPoelstra/ImproveRawhideF10 | 12:12 |
| wwoods | f13: probably it'll run as an initscript after the system reboots | 12:12 |
| wwoods | jlaska: aha, thanks | 12:12 |
| -!- mether [n=sundaram@122.169.3.61] has quit [Read error: 104 (Connection reset by peer)] | 12:12 | |
| f13 | wwoods: yeah, we can easily fetch test scripts in %post of theinstall to be launched upon reboot | 12:13 |
| wwoods | f13: right, which gives us a platform for any automated testing | 12:13 |
| wwoods | and then things start getting really interesting. | 12:14 |
| -!- mether [n=sundaram@122.169.3.61] has joined #fedora-meeting | 12:14 | |
| wwoods | anyway. don't want to look too far ahead | 12:14 |
| wwoods | anything else we need to discuss? | 12:14 |
| -!- wwoods changed the topic of #fedora-meeting to: Fedora QA | other | 12:14 | |
| -!- mether [n=sundaram@122.169.3.61] has quit [Read error: 54 (Connection reset by peer)] | 12:14 | |
| f13 | this week is when I'll be taking a much closer re-look at our compose processes, to figure out where we can insert some pre-QA | 12:14 |
| f13 | I'm going to be eyeballing the added work to verifytree, and things like repoclosure | 12:15 |
| -!- mether [n=sundaram@122.169.3.61] has joined #fedora-meeting | 12:15 | |
| wwoods | repoclosure? mercy | 12:15 |
| -!- fbijlsma [n=fbijlsma@h-217.111.50.177.host.de.colt.net] has quit ["Leaving"] | 12:15 | |
| viking_ice_ | One thing Early feature testing.. | 12:15 |
| viking_ice_ | lets do it :) | 12:16 |
| wwoods | ah yes, early feature testing stuff | 12:16 |
| wwoods | so all Features need to have a "spec" by Alpha - basically the Scope section needs to say exactly what changes the Feature will make | 12:16 |
| wwoods | and what it will (and won't) be capable of doing | 12:17 |
| wwoods | if there's any features that catch your fancy | 12:17 |
| wwoods | http://fedoraproject.org/wiki/Features/Dashboard <-- check this page for feature status | 12:17 |
| leitz | Sort of like a Use Case. :) | 12:17 |
| wwoods | leitz: pretty much, yeah | 12:17 |
| wwoods | Use Case, Spec, Scope | 12:18 |
| wwoods | whatever you call it - it needs to be there by Alpha | 12:18 |
| wwoods | and by Beta, the feature owner (with our help) needs to write a test plan - docs for us testers on how to make sure the feature matches the spec | 12:18 |
| leitz | My *opinion*, for whatever it's worth, is that the whole bhodi voting thing get tossed. | 12:18 |
| viking_ice_ | We need extensive cases for the *DE what they are bringing in and so fourth .. | 12:18 |
| leitz | Take your "Feature Set" or "Use Case" and test against that. With extra packagers able to parallel an expected outcome. | 12:19 |
| wwoods | leitz: whoa. the point of bodhi voting is for testers to be able to say "pass/fail" | 12:20 |
| wwoods | if packages had test plans, this would be natural | 12:20 |
| wwoods | but we're kind of mixing up two different things: updates to stable releases | 12:20 |
| wwoods | and new features going into the development tree | 12:20 |
| viking_ice_ | There are potential privacy concerns regarding a feature of the user-switcher-applet it automatically logs you in on your IM server | 12:20 |
| wwoods | new features never hit bodhi during development | 12:21 |
| -!- mether [n=sundaram@122.169.3.61] has quit [Client Quit] | 12:21 | |
| leitz | Right, but you're pas/failing at the package level. | 12:21 |
| wwoods | viking_ice_: right, so the spec should say that can be disabled | 12:21 |
| leitz | pas/pass | 12:21 |
| -!- mether [n=sundaram@122.169.3.61] has joined #fedora-meeting | 12:21 | |
| wwoods | leitz: yeah - in theory each Feature has one or more packages, and each Feature has a test plan | 12:22 |
| -!- drago01 [n=linux@chello062178124130.3.13.univie.teleweb.at] has quit [Remote closed the connection] | 12:22 | |
| wwoods | so once you get to a stable release, if you're updating one of the packages from a Feature | 12:22 |
| * leitz is always subject to correction. :) | 12:22 | |
| wwoods | then you can use that Feature's test plan to test the package | 12:22 |
| viking_ice_ | wwoods: well I think the board needs to take a stand on that one should it be on by default or off I personally dont like some IM server know when I'm online or not and have some app set the status for me | 12:23 |
| hadess | did i miss the fingerprint reader chat? poke me when you guys are ready to talk about it | 12:23 |
| wwoods | hadess: heh, sorry, QA meeting running long | 12:23 |
| hadess | right | 12:23 |
| f13 | if we're into feature talk, I'm goign to step out and go have breakfast | 12:23 |
| wwoods | FESCo should be at 1PM EST (1800UTC).. unless.. I'm mistaken? | 12:23 |
| bpepple | no your right. | 12:24 |
| leitz | I'm suggesting not pass/failing by Feature because the understanding (subject to facts) is that there are ways to game the system. | 12:24 |
| leitz | Sorry, /the understanding/my understanding/ | 12:24 |
| f13 | bodhi wouldn't be used for features. | 12:24 |
| wwoods | leitz: I'm not sure I understand you, but currently Features and bodhi are completely separate | 12:24 |
| wwoods | the feature planning stuff only applies to Rawhide, which doesn't go through bodhi | 12:24 |
| hadess | Wednesday at 17:00 UTC (13:00 EST) <- huh? | 12:25 |
| leitz | Hmm...lemme go clarify my thinking and review my notes. | 12:25 |
| wwoods | huh, it's listed as 1700-1900 | 12:25 |
| -!- knurd_afk is now known as knurd | 12:25 | |
| hadess | 18:00 utc then | 12:25 |
| wwoods | crap, are we stomping on FESCo? | 12:25 |
| wwoods | we can take the rest of this discussion to #fedora-qa | 12:25 |
| bpepple | wwoods: no, we don't start for another 30 minutes or so. | 12:26 |
| wwoods | well, either way, I need to get some lunch before I fall over | 12:26 |
| wwoods | QA discussion will move to #fedora-qa | 12:26 |
| f13 | and I some breakfast | 12:26 |
| wwoods | we'll try to straighten out bodhi vs. features a bit | 12:27 |
| * leitz will smooch with his wife for a while. :) | 12:27 | |
| viking_ice_ | soon supper for me.... | 12:27 |
| hadess | bpepple: you got one or the other times wrong then | 12:27 |
| wwoods | leitz, viking_ice_, f13, jlaska, jds2001: thanks. and anyone else I missed. | 12:28 |
| bpepple | I probably forgot to adjust the UTC time. Big fail on my part obviously. :( | 12:28 |
| -!- leitz is now known as leitz_afk | 12:28 | |
| -!- wwoods changed the topic of #fedora-meeting to: Channel is used by various Fedora groups and committees for their regular meetings | Note that meetings often get logged | For questions about using Fedora please ask in #fedora | See http://fedoraproject.org/wiki/Communicate/FedoraMeetingChannel for meeting schedule | 12:28 | |
| --- Log closed Wed Dec 10 12:28:12 2008 | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!