| --- Log opened Wed Aug 06 11:04:56 2008 | ||
| -!- vwbusguy [n=scott@99-153-230-117.lightspeed.iplsin.sbcglobal.net] has quit [Nick collision from services.] | 11:05 | |
| -!- hanthana [n=hanthana@124.43.77.172] has joined #fedora-meeting | 11:05 | |
| wwoods | jlaska, jds2001, f13, poelcat: ping | 11:05 |
|---|---|---|
| * jlaska | 11:05 | |
| -!- vwbusguy- [n=scott@99-153-230-117.lightspeed.iplsin.sbcglobal.net] has joined #Fedora-meeting | 11:05 | |
| wwoods | qa meeting starting, say "hi" for the logs | 11:05 |
| f13 | wwoods: pong | 11:06 |
| jds2001 | sorry i've been less than reliable lately - $DAYJOB has insane deadlines, and add to that my surgeon likes to schedle appts on Wednesday at 10:15 | 11:06 |
| f13 | "hi" for the logs | 11:06 |
| jds2001 | "hi" for the logs | 11:06 |
| * jds2001 just feels like a big copycat | 11:06 | |
| wwoods | hah | 11:07 |
| -!- No5251 [n=No5251@p50990d02.dip0.t-ipconnect.de] has quit ["Wenn du den Fnord nicht siehst, kann er dich auch nicht essen."] | 11:07 | |
| wwoods | it's OK | 11:07 |
| wwoods | so, as usual, I don't have a big agenda | 11:08 |
| -!- John5342 [n=John5342@user-54470a1c.wfd82a.dsl.pol.co.uk] has joined #fedora-meeting | 11:08 | |
| wwoods | first things first: Alpha's out. yay! | 11:08 |
| jlaska | jds2001: no worries ... "it" happens ;) | 11:08 |
| -!- hanthana_ [n=hanthana@124.43.43.212] has joined #fedora-meeting | 11:08 | |
| -!- wwoods changed the topic of #fedora-meeting to: Fedora QA Meeting | F10Alpha release/review | 11:08 | |
| wwoods | we need to think about whether we want to do a non-blocking freeze for F11Alpha | 11:08 |
| wwoods | (we're not going to decide that right now, though) | 11:09 |
| f13 | f10 alpha wasn't our best of releases :/ | 11:09 |
| wwoods | one lesson learned, though: we need to start composing and testing images *before* the "freeze" | 11:09 |
| -!- J5 [n=quintice@66.187.234.199] has joined #fedora-meeting | 11:09 | |
| wwoods | so we have some advance warning of Big Bads | 11:09 |
| jds2001 | or do a blocking freeze, which folks would probably cry out about :/ | 11:10 |
| wwoods | either way | 11:10 |
| -!- AndreasR [n=zeus@urz-ar224.urz.unibas.ch] has quit ["Verlassend"] | 11:10 | |
| jlaska | the confusion for me is the process by which we free the bits for folks to play leading up to a milestone ... f13 summed it up rather nicely during the releng meeting | 11:10 |
| wwoods | we still need to do some early composes and get the word out to devs to get bugs fixed *BEFORE* the freeze | 11:10 |
| f13 | indeed | 11:11 |
| f13 | I did a number of composes leading up to the freeze, but they were just on my workstation, not a lot of attention was paid to them (although andy poked at them whenever they were there) | 11:11 |
| jds2001 | what I think is that it'd be useful to move reducto into Fedora infra. (but that'ss just me - there may be reasons i dont know that it's internal) | 11:12 |
| wwoods | not possible | 11:12 |
| jlaska | it's not clear what needs to be done on those internal composes in order for them to be considered worthy of the community | 11:12 |
| wwoods | reducto isn't magical | 11:12 |
| * jds2001 knows that :) | 11:12 | |
| wwoods | it's just a machine that happens to be on jesse's desk that has a bunch of disk space | 11:12 |
| f13 | jds2001: I now have a few machines in the fedora infrastructure to do composes on | 11:13 |
| f13 | but the problem with that is it greatly increases the lag time between compose and test | 11:13 |
| jds2001 | how do you mean? | 11:13 |
| f13 | with reducto in BOS, I can compose, test it in kvm/xen on reducto, get it into the hands of the anaconda folks for immediate use, as well as andy for immediate qa work | 11:13 |
| jds2001 | network issues? | 11:13 |
| jds2001 | yeah | 11:14 |
| f13 | if I compose in PHX, we're talking a good chunk of time to sync down the compose bits to test them. | 11:14 |
| wwoods | the reason we build the images in the office is because we then have instant access to the images to smoketest 'em | 11:14 |
| f13 | 700~K/s is the transfer rate out of PHX to BOS | 11:14 |
| wwoods | building them in the fedora infrastructure means *nobody* gets instant smoketest ability | 11:14 |
| jds2001 | yeah that sucks | 11:14 |
| wwoods | that's not helpful | 11:14 |
| f13 | however one can do multile composes | 11:14 |
| wwoods | right | 11:14 |
| f13 | multiple that is | 11:14 |
| f13 | and nothing stopped people from composing on their own against rawhide | 11:15 |
| wwoods | composing in the office *and* in the fedora infrastructure simultaneously would solve the problem, but | 11:15 |
| wwoods | yeah, exactly. anyone with sufficient disk can compose just as well on their own | 11:15 |
| jlaska | I don't have a problem doing one compose ... but I Don't feel like we have visibility on what is expected to happen on that compose before we provide community access | 11:16 |
| wwoods | define "community" | 11:16 |
| jlaska | for example, how does f13 know that the reducto compose is "good" enough to push to mirrors? | 11:16 |
| wwoods | full Fedora community access to the pre-release compose attempts is not useful | 11:16 |
| wwoods | the question you're asking is: "when is it ready for release?" | 11:17 |
| jlaska | wwoods: I'm not asking about that right now ... | 11:17 |
| jlaska | right ... how does f13 get confidence in the bits so that he can go through the mirror process | 11:17 |
| wwoods | QA team testing of the candidate bits | 11:17 |
| f13 | jlaska: the bits I compose gets rsynced to various locations for other QA folks to look at | 11:18 |
| jlaska | f13: internal or external? | 11:18 |
| f13 | we verify needed fixes, do cursory smoke testing for regressions | 11:18 |
| f13 | jlaska: could be both if we had more active QA people outside RH | 11:18 |
| jlaska | right | 11:18 |
| f13 | jlaska: this is where composing in both locatiosn could help | 11:18 |
| f13 | compose in phx and anybody can get to it, compose in BOS and we get to it immediately | 11:19 |
| * jds2001 just does his own composes. | 11:19 | |
| f13 | and there is that too (: | 11:19 |
| -!- kital [n=Joerg_Si@fedora/kital] has joined #fedora-meeting | 11:19 | |
| * jlaska imagining a wiki page where we outline a summary of the milestone release process | 11:19 | |
| jds2001 | since i mirror locally, it is faster for me to do a compose than download some other bits. | 11:19 |
| jlaska | and we can then stub out links to "here's the link to roll your own tree" (as some folks do), and "here's the list of tests we perform prior to releasing" | 11:20 |
| jds2001 | we have the release tests | 11:20 |
| jds2001 | and i've blogged how to do a compose. | 11:20 |
| jds2001 | (porbably needs to move someplace more foraml) | 11:20 |
| wwoods | the tests we perform prior to release.. that's the installation test plan | 11:20 |
| jlaska | definitely, the informatoin is out there ... just think it would be worthwhile to organize | 11:20 |
| f13 | jds2001: the trick is to coordinate when I toss extra packages into my compose | 11:20 |
| f13 | jds2001: freshly built packages after teh latest rawhide | 11:21 |
| jlaska | wwoods: we don't perform the installation test plan prior to a milestone release, do we? | 11:21 |
| wwoods | yes. we do. | 11:21 |
| jds2001 | f13: yeah, and that's what sucks :) | 11:21 |
| jlaska | wwoods: https://fedoraproject.org/wiki/QA/TestResults/Fedora10Install/Alpha ? | 11:21 |
| zodbot | <http://tinyurl.com/6bjv7g> (at fedoraproject.org) | 11:21 |
| f13 | jds2001: yeah, those on IRC when that happens knows what's going on | 11:21 |
| wwoods | jlaska: yep. | 11:21 |
| jlaska | wwoods: I'm thinking milestone in the sense of Alpha, Beta, PR, RC | 11:21 |
| jlaska | not just GA | 11:21 |
| wwoods | yes. | 11:21 |
| jlaska | if we executed the full plan prior, that page would be red||yellow||green | 11:22 |
| jlaska | (not white) | 11:22 |
| jds2001 | jlaska: you can compose reawhide and run through those wehenver | 11:22 |
| wwoods | we never have time to execute the full plan as a prerequisite to release. | 11:22 |
| f13 | jlaska: there isn't enough time/people to execute teh entire test fully | 11:22 |
| * jds2001 cant type | 11:22 | |
| wwoods | we do as much as we can and releng/qa make a judgement call based on the current results. | 11:22 |
| f13 | jlaska: we do the best we can with what we got, and make decisions based on coverage, milestone, and schedule. | 11:22 |
| wwoods | there's always more testing that can be done. | 11:22 |
| jlaska | right, so should we bother specifying all this stuff if no one runs it? | 11:22 |
| f13 | yes, we should | 11:22 |
| wwoods | "not finished" != "no one runs it" | 11:22 |
| f13 | because if we don't, it'll definitely never get done. | 11:23 |
| f13 | jlaska: also, many of these tests get ran after the release too, to fill in coverate | 11:23 |
| wwoods | testing is never, and will never, be Complete | 11:23 |
| f13 | coverage | 11:23 |
| jlaska | that seems like something we'd want to address | 11:23 |
| f13 | unlike RHEL, we can't stand in the road and hold up traffic until we've searched every car | 11:23 |
| wwoods | something we'd want to address? you mean.. "we should test more"? | 11:23 |
| wwoods | I fully agree. | 11:23 |
| f13 | we have a set time to do as much testing as we possibly can, and eventually make a judgement call as to ship or delay | 11:24 |
| wwoods | I think we could rewrite the test plan to better match the actual priorities | 11:24 |
| wwoods | e.g. we do not care if ext2 is tested for non-final releases | 11:25 |
| jlaska | how about extending our FUDCon rawhide acceptance discussion into the milestone acceptance realm? | 11:25 |
| -!- hanthana [n=hanthana@124.43.77.172] has quit [Read error: 113 (No route to host)] | 11:25 | |
| f13 | jlaska: that's essentially what we've been trying to do since fudcon | 11:26 |
| -!- mether [n=sundaram@nat/redhat-in/x-44d38762873e3721] has joined #fedora-meeting | 11:26 | |
| f13 | at fudcon we sort of handwaved at "alpha acceptance" and "beta acceptance" | 11:26 |
| f13 | since then we've been trying to define what those mean | 11:26 |
| wwoods | that's what we were trying to do with testopia, before it went dark | 11:26 |
| jlaska | very true | 11:26 |
| jds2001 | btw, extjs 2.2 was released on monday | 11:26 |
| f13 | also, it's hard to state what we care/don't care about in a static way, since it changes based on deadline. | 11:26 |
| jds2001 | with the FLOSS exception | 11:26 |
| jds2001 | need spot to opine on that :) | 11:26 |
| spot | do not want | 11:27 |
| f13 | at teh beginning of the freeze, we certainly care about every test, but 5 minutes before the go/nogo deadline, we suddenly care a lot less about a lot of the tests | 11:27 |
| f13 | and which we care less about also depends on what other testing had been done. | 11:27 |
| jlaska | f13: right ... we start with a baseline ... and test change from that point on | 11:27 |
| spot | RH Legal says stay far far far away from ExtJS. Exception, or no exception. | 11:27 |
| * jlaska trying to find FUDCon wiki pages ... | 11:28 | |
| jds2001 | spot: understood :( | 11:28 |
| wwoods | blerg | 11:28 |
| f13 | jlaska: https://fedoraproject.org/wiki/JohnPoelstra/ImproveRawhideF10 | 11:29 |
| zodbot | <http://tinyurl.com/5eem6f> (at fedoraproject.org) | 11:29 |
| wwoods | so basically: no testopia ever | 11:29 |
| jlaska | f13: that's it ... thanks! | 11:29 |
| * wwoods wonders what dmalcolm is up to | 11:29 | |
| -!- mbacovsk [n=mbacovsk@nat/redhat/x-0d5e8063327bce09] has quit [Read error: 110 (Connection timed out)] | 11:29 | |
| f13 | wwoods: not unless you port testopia to some other js api | 11:29 |
| stickster | f13: dmalcolm tells me that's not an unattainable goal | 11:30 |
| f13 | too many negatives! | 11:30 |
| f13 | "it's possible" yes or no? | 11:30 |
| * stickster being positive! | 11:30 | |
| stickster | f13: dmalcolm tells me that's an attainable goal! Yay! | 11:31 |
| stickster | f13: Proabably a couple months for some contractor... now where did I leave my spares lying around? | 11:31 |
| f13 | heh | 11:31 |
| -!- sdziallas [n=sebastia@p57A2D752.dip.t-dialin.net] has quit ["Ex-Chat"] | 11:31 | |
| jlaska | f13: perfect ... https://fedoraproject.org/wiki/JohnPoelstra/ImproveRawhideF10#rawhide_as_a_MAJOR_MILESTONE | 11:31 |
| zodbot | <http://tinyurl.com/5eem6f> (at fedoraproject.org) | 11:31 |
| f13 | jlaska: it's that step 11 that's the big one (: | 11:32 |
| wwoods | and we were working on a testopia plan | 11:32 |
| wwoods | with priorities etc. | 11:33 |
| wwoods | there's some tests that we just cannot release without results | 11:33 |
| f13 | although we do have code to do steps 1,5,6, but not many of the others. | 11:33 |
| jlaska | yup :) | 11:33 |
| wwoods | and there's some tests that we can take or leave | 11:33 |
| -!- giallu [n=giallu@fedora/giallu] has quit [Read error: 110 (Connection timed out)] | 11:33 | |
| jlaska | we can certainly work up the testing milestone criteria w/o testopia | 11:33 |
| wwoods | ppc netboot? ext2 raid 1+0 on LVM? yeah, okay, if we've got time | 11:33 |
| jlaska | just in terms of outlining test areas, or even discrete cases | 11:34 |
| wwoods | right, I'm just saying we've got a start at it already | 11:34 |
| jlaska | wwoods: certainly ... so replacing testopia with ${mgmt_tool_formerly_known_as_testopia} | 11:35 |
| -!- No5251 [n=No5251@p50990d02.dip0.t-ipconnect.de] has joined #fedora-meeting | 11:35 | |
| f13 | yeah, we probably need to come up with a couple different classifications | 11:36 |
| wwoods | we need to pull some data outta the testopia db but yeah | 11:36 |
| f13 | mandatory, default, optional (for lack of a better naming scheme) | 11:36 |
| f13 | and then tag the tests with these labels | 11:36 |
| wwoods | we typically call those "tier1 / 2 / 3" | 11:36 |
| jlaska | indeed | 11:36 |
| f13 | ok, sure | 11:36 |
| wwoods | except it gets funkier when you're talking about different milestones | 11:36 |
| f13 | but | 11:36 |
| wwoods | so, yeah | 11:36 |
| f13 | we also have different arches to deal with | 11:36 |
| f13 | so if DVD install (tier1) was tested on i386, its' not manditory for x86_64 or ppc | 11:37 |
| wwoods | (DVD install being separate from DVD boot) | 11:37 |
| f13 | sure | 11:37 |
| f13 | I think that we definitely won't ship without tier1 tests being complete (pass) on at least one of the arches | 11:38 |
| jlaska | does it matter whether MILESTONE is alpha, beta, PreviewRelease, or ReleaseCandidate? | 11:38 |
| f13 | that moves the rest of the arches to tier2 | 11:38 |
| f13 | jlaska: at this time, I don't think so. | 11:38 |
| wwoods | technically RC is not a milestone | 11:38 |
| wwoods | RCs are the test composes we do before GA | 11:38 |
| jlaska | wwoods: so should a different process apply for RC? | 11:38 |
| f13 | jlaska: if we magically got a bunch more QA resources and know ahead of time we have the man power to blow through all the tests on all the arches, I'd change my mind. | 11:38 |
| jlaska | f13: nod | 11:39 |
| wwoods | no different than the process we apply to the test composes for alpha/beta/pr | 11:39 |
| f13 | jlaska: in my mind, RC's are just attempts at getting to the milestone, not a milestone itself | 11:39 |
| wwoods | except that we make a much stronger effort to get community access to the GA RCs | 11:39 |
| -!- mdomsch [n=Matt_Dom@cpe-70-124-62-55.austin.res.rr.com] has joined #fedora-meeting | 11:39 | |
| f13 | nod | 11:39 |
| wwoods | f13: exactly | 11:39 |
| f13 | which I think can easily be done by using the dual-compose method | 11:39 |
| jlaska | so in Fedora ... a release candidate won't become the GA? We will always re-compose a GA tree? | 11:39 |
| wwoods | huh? release candidates become GA. where did you get that idea? | 11:40 |
| jlaska | software quality assurance ;) | 11:40 |
| f13 | the only thing we do to a RC to make it GA is gpg sign the sha1sums | 11:40 |
| f13 | and filter in teh Live images | 11:41 |
| f13 | although jigdo metadata may not show up for the first couple RCs | 11:41 |
| jlaska | okay so no respinning or anything, you take an existing spin and sign it? | 11:41 |
| f13 | yep | 11:41 |
| jlaska | gotcha | 11:41 |
| -!- sdziallas [n=sebastia@p57A2D752.dip.t-dialin.net] has joined #fedora-meeting | 11:41 | |
| f13 | it's a REAL release candidate | 11:41 |
| jlaska | wwoods: sorry, was thinking about how I'm used to release candidates and how they relate to the final product | 11:41 |
| wwoods | as in it is a candidate to become the release | 11:41 |
| wwoods | yeah that method is total horseshit | 11:42 |
| f13 | (: | 11:42 |
| wwoods | if you call something a "release candidate" without being fairly confident that you could end up releasing those exact bits | 11:42 |
| wwoods | you are lying to yourself and your users | 11:42 |
| jlaska | I don't disagree | 11:42 |
| f13 | I laugh at schedules that have marked "RC1, RC2, RC3" | 11:42 |
| wwoods | this is why we have a Preview Release | 11:43 |
| jlaska | right ... planning RC[2-9] is an interesting discussion between QA and PM | 11:43 |
| wwoods | that fills the role that other people call the "Release candidate" | 11:43 |
| -!- Frankly3D [n=frank@194.46.228.148] has quit [Remote closed the connection] | 11:43 | |
| jlaska | wwoods: I see ... so you were distinquishing between the public RC (called PreviewRelease), and the internal trees f13 builds leading up to the official GA, is that accurate? | 11:44 |
| f13 | we also don't re-compose because software/hardware is fickle, something could go wrong in the compose process, so I want to sign/publish the bits we actually tested | 11:44 |
| wwoods | jlaska: yes. | 11:44 |
| wwoods | the internal trees that get built before each milestone are for QA-team consumption only | 11:45 |
| wwoods | we're resolved to make an effort to compose in public *and* in the RH offices simultaneously | 11:45 |
| -!- Frankly3D [n=frank@194.46.228.148] has joined #fedora-meeting | 11:45 | |
| wwoods | to allow more of the QA team to work on testing the RCs | 11:45 |
| wwoods | and we actually put some of the F9GA RCs up as torrents, if memory serves | 11:46 |
| f13 | yeah | 11:47 |
| jlaska | okay, thanks ... this was very helpful to hilight how the bits are freed. And the different needs each milestone (internal and public) has | 11:47 |
| f13 | at teh end of the day though, it's the bits that we've tested most that will be the ones that go out | 11:47 |
| f13 | those typically are the ones done on reducto | 11:47 |
| f13 | we'll just use the bits in PHX as a pre-sync content | 11:47 |
| -!- John5342 [n=John5342@user-54470a1c.wfd82a.dsl.pol.co.uk] has left #fedora-meeting [] | 11:49 | |
| wwoods | so, yeah - F10Alpha, Not The Best Release Process Ever (but not that bad) | 11:50 |
| wwoods | when we talked in the releng meeting monday it seemed like we were inclined to make the Alpha a blocking freeze | 11:51 |
| wwoods | either way we should compose images a week or two before the freeze to get early warning of potential issues | 11:51 |
| f13 | that gets more people paying attention to the bits we're actually composing | 11:51 |
| wwoods | definitely | 11:51 |
| f13 | wwoods: i think we have scheduled weekly snapshots after alpha | 11:52 |
| wwoods | really? you willing to do that? | 11:52 |
| f13 | beta freeze isn't that far away though, given the length of alpha | 11:52 |
| f13 | wwoods: snapshots are 'best attempt' | 11:52 |
| -!- cmpahar [n=cmpahar@83.212.120.204] has quit ["Leaving"] | 11:53 | |
| wwoods | true | 11:54 |
| wwoods | so yeah, if you'll make images we'll be better for it, I think | 11:54 |
| wwoods | okay, anything else relating to the alpha? | 11:57 |
| * wwoods getting distracted | 11:57 | |
| f13 | we could still get people to fill in test cases after the fact | 11:57 |
| f13 | which will help us to focus on things in the snapshots and beta pre-testing | 11:57 |
| wwoods | f13: very true | 11:58 |
| f13 | and by 'could' I mean 'should'. | 11:58 |
| f13 | and by 'we' I mean 'you' (: | 11:58 |
| wwoods | heh! | 11:58 |
| wwoods | fair 'nuff | 11:58 |
| wwoods | and I have been doing some testing there | 11:58 |
| wwoods | so I'll continue with that and try to encourage others. | 11:58 |
| wwoods | okay, so | 11:59 |
| -!- wwoods changed the topic of #fedora-meeting to: Fedora QA Meeting | New Bugzilla! | 11:59 | |
| wwoods | woo, the Great Grand Bugzilla Upgrade is upon us | 11:59 |
| wwoods | things are a little shaky but coming together | 11:59 |
| wwoods | I'm updating python-bugzilla to understand the BZ 3.2 methods | 11:59 |
| wwoods | sending reports to the bugzilla team where applicable | 11:59 |
| wwoods | jds2001: I'll be interested to hear how it's affecting you and the other triagers | 12:00 |
| f13 | SLOOOOOW | 12:00 |
| f13 | and I'm constantly trying to find where the UI moved things | 12:00 |
| f13 | summary box is in a /really/ bad place | 12:00 |
| wwoods | yeah, it's kinda weird | 12:00 |
| f13 | if we thought bugzilla was scary to users before, it's down right pants filling now | 12:00 |
| wwoods | which is why it's important to update python-bugzilla | 12:01 |
| wwoods | and try to make bug filing automatic and easy when possible | 12:01 |
| -!- rnorwood_ [n=rnorwood@adsl-144-134-115.rmo.bellsouth.net] has quit [Read error: 110 (Connection timed out)] | 12:02 | |
| -!- rnorwood_ [n=rnorwood@nat/redhat/x-d2ef9bf71088a4b4] has joined #fedora-meeting | 12:02 | |
| wwoods | but yeah, it's kind of intimidating | 12:03 |
| wwoods | it'd be nice if the whole big form block at the top was hideable | 12:03 |
| f13 | and the yukon is kind of cold | 12:03 |
| -!- fbijlsma [n=fbijlsma@66.187.227.198] has quit [Read error: 110 (Connection timed out)] | 12:04 | |
| f13 | I think a number of the canned queries for triage don't work anymore | 12:04 |
| wwoods | oh, yeah, someone mentioned that my canned rawhide/f8 queries are broken | 12:04 |
| wwoods | gotta look into that | 12:05 |
| f13 | The search named rawhide-thisweek does not exist. | 12:05 |
| f13 | The search named F8-thisweek does not exist. | 12:05 |
| f13 | thankfully bugz.fedoraproject.org didn't break, I use that a ton | 12:05 |
| wwoods | WORKSFORME - must be a perms thing | 12:05 |
| wwoods | that's cool - that's based on python-bugzilla | 12:05 |
| f13 | odd that you'd have perms for it and I wouldn't | 12:05 |
| wwoods | so it looks like I did *something* right | 12:05 |
| wwoods | f13: I created those queries | 12:05 |
| wwoods | so they work for me. | 12:06 |
| wwoods | I'll figure that out as soon as I get a chance | 12:06 |
| f13 | k | 12:06 |
| wwoods | so yeah - looks like I'm spending most of this week on bugzilla stuff | 12:06 |
| wwoods | which is fine. bugzilla is pretty dang important. | 12:06 |
| -!- sdziallas [n=sebastia@p57A2D752.dip.t-dialin.net] has quit ["Ex-Chat"] | 12:07 | |
| -!- mdomsch [n=Matt_Dom@cpe-70-124-62-55.austin.res.rr.com] has quit ["Leaving"] | 12:08 | |
| wwoods | Soon I'll bug people about stuff they'd like to see in python-bugzilla | 12:08 |
| wwoods | as I start working toward a python-bugzilla 1.0 API | 12:08 |
| wwoods | I know clumens wanted Bug.attach(file), for instance | 12:08 |
| f13 | kcool | 12:08 |
| wwoods | so think about that, if you use python-bugzilla at all | 12:08 |
| wwoods | lunch looms large overhead | 12:09 |
| f13 | I haven't used it since I did the massive bugfiling exercise a while back | 12:09 |
| wwoods | so I'll try to wrap up quick here | 12:09 |
| -!- wwoods changed the topic of #fedora-meeting to: Fedora QA Meeting | Feature testing | 12:09 | |
| wwoods | features! woo! | 12:09 |
| wwoods | we need to make sure their test plans don't suck. | 12:09 |
| wwoods | anyone here a feature owner? | 12:09 |
| f13 | not I | 12:09 |
| * wwoods is listed on a couple. doh. | 12:09 | |
| f13 | I'm listed, but I don't own it | 12:10 |
| wwoods | just call me Mr. Bit Off More Than He Can Chew | 12:10 |
| wwoods | anyway, if you happen to be looking at a Feature page, see if you can figure out how to test that feature in Rawhide | 12:10 |
| wwoods | if you can't.. ask a bunch of questions in the Talk page | 12:10 |
| wwoods | if the owner(s) won't/can't answer them, their feature can't be tested. if we can't test it, we can't really use it | 12:11 |
| -!- sdziallas [n=sebastia@p57A2D752.dip.t-dialin.net] has joined #fedora-meeting | 12:12 | |
| wwoods | if we can't test it, it should get dropped. | 12:12 |
| abadger1999 | f13: It did but maploin pointed out it was broken and I fixed it. | 12:12 |
| -!- giallu [n=giallu@fedora/giallu] has joined #fedora-meeting | 12:13 | |
| wwoods | So yeah. I don't want it to sound like a threat, but if feature owners won't help with the test plans we will have to drop their features. | 12:13 |
| wwoods | so there that is. | 12:14 |
| f13 | heh | 12:14 |
| wwoods | yer on notice, feature owners. | 12:14 |
| wwoods | that's about all I can think of right now. anyone else got anything? | 12:14 |
| f13 | a hungry tummy | 12:14 |
| f13 | oh | 12:14 |
| f13 | I may be moving in the middle of beta freeze cycle | 12:15 |
| jds2001 | wwoods: i've been looking at them and reacting accordingly at FESCo meetings | 12:15 |
| f13 | although I may also be camping at somebody's house until beta is out the door too | 12:15 |
| jds2001 | f13: moving not allowed :) | 12:15 |
| f13 | jds2001: moving across the country even. | 12:15 |
| jds2001 | ouch | 12:15 |
| jds2001 | back to Seattle? | 12:15 |
| wwoods | WEST SIIIIIDE | 12:15 |
| -!- Sonar_Gal [n=Andrea@fedora/SonarGal] has quit ["Leaving"] | 12:16 | |
| abadger1999 | You going to move to PHX? That's one way to cut the network latency for composes :-) | 12:16 |
| wwoods | ahem. yes. noted. | 12:16 |
| f13 | jds2001: seattleish | 12:16 |
| wwoods | man I should find somewhere cool to move to and work remotely. | 12:16 |
| wwoods | too bad I'm so lazy and we're just getting the house the way we like it | 12:16 |
| wwoods | also Leah refuses to move any further north. we're already in *North* Carolina after all. | 12:17 |
| skvidal | wwoods: where is she from? | 12:17 |
| f13 | for the lolz | 12:17 |
| wwoods | skvidal: gulf coast mississippi | 12:17 |
| skvidal | wwoods: move to asheville, nc | 12:17 |
| skvidal | that's no further north but it is less hot than raleigh | 12:18 |
| * jds2001 has a friend for asheville | 12:18 | |
| jds2001 | ahh, hot is good | 12:18 |
| jds2001 | cold == bad | 12:18 |
| wwoods | yeah she already complains about the winters being too cold and dry here in Raleigh. heh. | 12:18 |
| wwoods | anyway, I'm going wildly off-topic, I assume the meeting is thus concluded | 12:18 |
| f13 | ok, I require foods | 12:18 |
| jds2001 | heh what are tehy like in Raleigh? | 12:19 |
| wwoods | I need lunch to be able to focus | 12:19 |
| -!- spoleeba [n=one@fedora/Jef] has joined #fedora-meeting | 12:19 | |
| f13 | I'm going to likely be AFK the rest of today, and PTO thurs/fri | 12:19 |
| f13 | (house hunting) | 12:19 |
| wwoods | jds2001: I'd say there's one week per year of *real* winter - sub-freezing temps, an inch or two of snow | 12:19 |
| wwoods | the rest of it is, like, low 40s and grayish | 12:20 |
| wwoods | come March 1 it's 70 degrees and sunny, like someone flipped a switch | 12:20 |
| skvidal | wwoods: this year we had a proper spring here | 12:20 |
| skvidal | it gradually warmed up - march was 50s and 60s as it should be | 12:20 |
| skvidal | and we got good rains then | 12:21 |
| wwoods | true | 12:21 |
| skvidal | the farmer's at the market here were talking about it being a proper spring | 12:21 |
| skvidal | and not having to irrigate much | 12:21 |
| wwoods | so that's what it's supposed to be like? good to know | 12:22 |
| wwoods | heh | 12:22 |
| wwoods | okay. lunch. thanks for your time, folks | 12:22 |
| --- Log closed Wed Aug 06 12:22:45 2008 | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!