From Fedora Project Wiki
(create skeleton page and agenda for next week's meeting) |
(update with summary / log of meeting) |
||
Line 1: | Line 1: | ||
= Attendees = | = Attendees = | ||
adamw | * adamw (130) | ||
* j_dulaney (43) | |||
* kparal (31) | |||
* tflink (27) | |||
* red_alert (8) | |||
* rbergeron (7) | |||
* zodbot (6) | |||
* nirik (5) | |||
* jskladan (2) | |||
* brunowolff (1) | |||
* pschindl (1) | |||
= Agenda = | = Agenda = | ||
* | * [http://lists.fedoraproject.org/pipermail/test/2011-November/104556.html Proposed meeting agenda] | ||
* | * [http://meetbot.fedoraproject.org/fedora-meeting/2011-11-21/fedora-qa.2011-11-21-16.01.html MeetBot summary] | ||
== Previous meeting follow-up == | == Previous meeting follow-up == | ||
* Nothing from previous short meeting required follow-up | |||
== FUDCon NA hackfest planning == | == FUDCon NA hackfest planning == | ||
* Plan to get anaconda and QA teams together to organize/conduct testing of new UI | |||
* We have room 3 on Sunday from 0900 to 1400 | |||
* FUDCon is too late to notify if we need hooks written into the new UI for testing | |||
* kparal will investigate whether such hooks are needed and notify anaconda team | |||
== Fedora 17 Test Day planning == | == Fedora 17 Test Day planning == | ||
* j_dulaney will act as Fedora 17 Test Day co-ordinator, adamw will help him get going | |||
== Upcoming QA events == | == Upcoming QA events == | ||
* adamw will get F16 retrospective summary posted and tickets filed this week | |||
* We need to agree on how to schedule TCs for F17 and communicate that to rbergeron - scheduling them early for F16 seemed to be a good idea | |||
== AutoQA update == | == AutoQA update == | ||
* Team is still preparing for AutoQA 0.7.0 deployment: need to decide when to schedule downtime | |||
* Test client hardware needs to be upgraded from Fedora 14 to Fedora 16 | |||
* Results mails are still disabled, need a list discussion about whether to try and revive them or wait for resultsdb | |||
== Open floor == | == Open floor == | ||
* kparal asked about relative priorities of various tasks: autoqa, validation test plan updates, test day organization, creating test plans for major F17 features | |||
* adamw said they're all important but those with the skills for autoqa should focus on it | |||
* adamw will try to ensure all outstanding tasks have tickets filed by end of week | |||
* infrastructure team is calling for testing of a rhel6-based fedorahosted.org , see [http://lists.fedoraproject.org/pipermail/infrastructure/2011-November/011151.html here] for more details | |||
== IRC Log == | == IRC Log == | ||
{| | |||
|- id="t16:01:21" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | #startmeeting Fedora QA Meeting | |||
|| [[#t16:01:21|16:01]] | |||
|- id="t16:01:21" | |||
! style="background-color: #42427e" | zodbot | |||
| style="color: #42427e" | Meeting started Mon Nov 21 16:01:21 2011 UTC. The chair is adamw. Information about MeetBot at http://wiki.debian.org/MeetBot. | |||
|| [[#t16:01:21|16:01]] | |||
|- id="t16:01:21" | |||
! style="background-color: #42427e" | zodbot | |||
| style="color: #42427e" | Useful Commands: #action #agreed #halp #info #idea #link #topic. | |||
|| [[#t16:01:21|16:01]] | |||
|- id="t16:01:26" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | #meetingname fedora-qa | |||
|| [[#t16:01:26|16:01]] | |||
|- id="t16:01:26" | |||
! style="background-color: #42427e" | zodbot | |||
| style="color: #42427e" | The meeting name has been set to 'fedora-qa' | |||
|| [[#t16:01:26|16:01]] | |||
|- id="t16:01:27" | |||
! style="background-color: #818144" | jskladan | |||
| style="color: #818144" | j_dulaney: hey there | |||
|| [[#t16:01:27|16:01]] | |||
|- id="t16:01:31" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | #topic roll call | |||
|| [[#t16:01:31|16:01]] | |||
|- id="t16:01:36" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | alright, who's around? | |||
|| [[#t16:01:36|16:01]] | |||
|- id="t16:01:38" | |||
| colspan="2" | * tflink is here | |||
|| [[#t16:01:38|16:01]] | |||
|- id="t16:01:40" | |||
| colspan="2" | * jskladan is ready to rock'n'roll | |||
|| [[#t16:01:40|16:01]] | |||
|- id="t16:01:45" | |||
| colspan="2" | * red_alert | |||
|| [[#t16:01:45|16:01]] | |||
|- id="t16:01:59" | |||
| colspan="2" | * j_dulaney is rocking out to Rammstein | |||
|| [[#t16:01:59|16:01]] | |||
|- id="t16:02:16" | |||
| colspan="2" | * j_dulaney will probably not be able to hear when it's all said and done | |||
|| [[#t16:02:16|16:02]] | |||
|- id="t16:02:38" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | hey, lookit that, when i actually manage to announce the meeting, people show up | |||
|| [[#t16:02:38|16:02]] | |||
|- id="t16:02:39" | |||
| colspan="2" | * brunowolff is for a short while. I have a meeting at work at half past. | |||
|| [[#t16:02:39|16:02]] | |||
|- id="t16:02:42" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | it's like magic or something | |||
|| [[#t16:02:42|16:02]] | |||
|- id="t16:02:50" | |||
| colspan="2" | * kparal pops up | |||
|| [[#t16:02:50|16:02]] | |||
|- id="t16:02:57" | |||
| colspan="2" | * adamw whacks kparal | |||
|| [[#t16:02:57|16:02]] | |||
|- id="t16:03:04" | |||
| colspan="2" | * j_dulaney plays whack-a-kparal | |||
|| [[#t16:03:04|16:03]] | |||
|- id="t16:03:19" | |||
! style="background-color: #854685" | j_dulaney | |||
| style="color: #854685" | adamw is a wizard | |||
|| [[#t16:03:19|16:03]] | |||
|- id="t16:03:29" | |||
| colspan="2" | * kparal pops off | |||
|| [[#t16:03:29|16:03]] | |||
|- id="t16:03:29" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | beat you to it | |||
|| [[#t16:03:29|16:03]] | |||
|- id="t16:03:45" | |||
| colspan="2" | * j_dulaney whacks adamw | |||
|| [[#t16:03:45|16:03]] | |||
|- id="t16:03:47" | |||
! style="background-color: #854685" | j_dulaney | |||
| style="color: #854685" | I win | |||
|| [[#t16:03:47|16:03]] | |||
|- id="t16:03:52" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | oh THAT'S how it's going to be? | |||
|| [[#t16:03:52|16:03]] | |||
|- id="t16:03:53" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | you're fired! | |||
|| [[#t16:03:53|16:03]] | |||
|- id="t16:04:13" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | alrighty | |||
|| [[#t16:04:13|16:04]] | |||
|- id="t16:04:14" | |||
| colspan="2" | * pschindl is here | |||
|| [[#t16:04:14|16:04]] | |||
|- id="t16:04:16" | |||
! style="background-color: #488888" | tflink | |||
| style="color: #488888" | how exactly do you fire someone who doesn't work for you? | |||
|| [[#t16:04:16|16:04]] | |||
|- id="t16:04:27" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | tflink: it's difficult, i admit, but i studied hard | |||
|| [[#t16:04:27|16:04]] | |||
|- id="t16:04:33" | |||
! style="background-color: #8c4a4a" | rbergeron | |||
| style="color: #8c4a4a" | tflink: LOL | |||
|| [[#t16:04:33|16:04]] | |||
|- id="t16:04:52" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | i have many methods | |||
|| [[#t16:04:52|16:04]] | |||
|- id="t16:04:53" | |||
! style="background-color: #854685" | j_dulaney | |||
| style="color: #854685" | Well, since I'm fired... | |||
|| [[#t16:04:53|16:04]] | |||
|- id="t16:05:01" | |||
| colspan="2" | * j_dulaney gets to slack off! | |||
|| [[#t16:05:01|16:05]] | |||
|- id="t16:05:04" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | i'll probably plant a bottle of jack in his desk drawer and call his boss | |||
|| [[#t16:05:04|16:05]] | |||
|- id="t16:05:27" | |||
! style="background-color: #488888" | tflink | |||
| style="color: #488888" | j_dulaney: is that how it works? Dang, I wish I would have know that, I could have been slacking for a month or two | |||
|| [[#t16:05:27|16:05]] | |||
|- id="t16:05:41" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | =) | |||
|| [[#t16:05:41|16:05]] | |||
|- id="t16:05:48" | |||
! style="background-color: #854685" | j_dulaney | |||
| style="color: #854685" | LOL | |||
|| [[#t16:05:48|16:05]] | |||
|- id="t16:05:49" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | #topic previous meeting follow-up | |||
|| [[#t16:05:49|16:05]] | |||
|- id="t16:06:18" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | nothing really doing here, since last week was a short, quiet meeting | |||
|| [[#t16:06:18|16:06]] | |||
|- id="t16:06:20" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | no action items | |||
|| [[#t16:06:20|16:06]] | |||
|- id="t16:06:23" | |||
| colspan="2" | * j_dulaney was halfway between Winston-Salem and Fayetteville during the last meeting | |||
|| [[#t16:06:23|16:06]] | |||
|- id="t16:06:33" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | and still had a job! | |||
|| [[#t16:06:33|16:06]] | |||
|- id="t16:07:08" | |||
! style="background-color: #854685" | j_dulaney | |||
| style="color: #854685" | Indeed | |||
|| [[#t16:07:08|16:07]] | |||
|- id="t16:07:14" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | #info no action items from previous meeting on which to follow up | |||
|| [[#t16:07:14|16:07]] | |||
|- id="t16:07:26" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | #topic FUDCon NA hackfest planning | |||
|| [[#t16:07:26|16:07]] | |||
|- id="t16:07:34" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | so, I think red_alert has been doing some work on this | |||
|| [[#t16:07:34|16:07]] | |||
|- id="t16:07:42" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | where are we atm? | |||
|| [[#t16:07:42|16:07]] | |||
|- id="t16:07:48" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | #chair tflink | |||
|| [[#t16:07:48|16:07]] | |||
|- id="t16:07:48" | |||
! style="background-color: #42427e" | zodbot | |||
| style="color: #42427e" | Current chairs: adamw tflink | |||
|| [[#t16:07:48|16:07]] | |||
|- id="t16:07:51" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | #chair j_dulaney | |||
|| [[#t16:07:51|16:07]] | |||
|- id="t16:07:51" | |||
! style="background-color: #42427e" | zodbot | |||
| style="color: #42427e" | Current chairs: adamw j_dulaney tflink | |||
|| [[#t16:07:51|16:07]] | |||
|- id="t16:08:13" | |||
! style="background-color: #4b904b" | red_alert | |||
| style="color: #4b904b" | well, we have room and time reserved | |||
|| [[#t16:08:13|16:08]] | |||
|- id="t16:08:24" | |||
! style="background-color: #4b904b" | red_alert | |||
| style="color: #4b904b" | anacodna folks know about it and at least clumens likes the idea :) | |||
|| [[#t16:08:24|16:08]] | |||
|- id="t16:08:36" | |||
! style="background-color: #488888" | tflink | |||
| style="color: #488888" | red_alert: for the Anaconda testing hackfest? | |||
|| [[#t16:08:36|16:08]] | |||
|- id="t16:08:49" | |||
! style="background-color: #4b904b" | red_alert | |||
| style="color: #4b904b" | tflink: yes | |||
|| [[#t16:08:49|16:08]] | |||
|- id="t16:08:57" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | yeah, background is good for those who haven't heard | |||
|| [[#t16:08:57|16:08]] | |||
|- id="t16:09:14" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | #link https://www.redhat.com/archives/anaconda-devel-list/2011-November/msg00055.html | |||
|| [[#t16:09:14|16:09]] | |||
|- id="t16:10:09" | |||
! style="background-color: #4b904b" | red_alert | |||
| style="color: #4b904b" | basically we'll sit together for ~4h and talk/do whatever needs to be talked/done. so far we think no strict agenda is needed and everyone will just bring in his topics as necessary | |||
|| [[#t16:10:09|16:10]] | |||
|- id="t16:10:44" | |||
! style="background-color: #854685" | j_dulaney | |||
| style="color: #854685" | #info We have room 3 on Sunday from 0900 to 1400 | |||
|| [[#t16:10:44|16:10]] | |||
|- id="t16:11:37" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | cool | |||
|| [[#t16:11:37|16:11]] | |||
|- id="t16:11:38" | |||
! style="background-color: #854685" | j_dulaney | |||
| style="color: #854685" | Speaking of such, anyone want to room with me? | |||
|| [[#t16:11:38|16:11]] | |||
|- id="t16:12:06" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | #info plan is to get anaconda and qa teams together to work on testing the new installer UI | |||
|| [[#t16:12:06|16:12]] | |||
|- id="t16:13:00" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | so, anyone have questions / ideas about the plan? | |||
|| [[#t16:13:00|16:13]] | |||
|- id="t16:13:04" | |||
! style="background-color: #4b904b" | red_alert | |||
| style="color: #4b904b" | oh, one important thing clumens mentioned: if things need to be built into the new UI to make it testable that needs to be defined ~now, i.e. FUDCon will be too late | |||
|| [[#t16:13:04|16:13]] | |||
|- id="t16:13:32" | |||
! style="background-color: #854685" | j_dulaney | |||
| style="color: #854685" | AutoQA test hooks? | |||
|| [[#t16:13:32|16:13]] | |||
|- id="t16:13:38" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | #info if we need things coded into the UI to make it testable we have to say so now | |||
|| [[#t16:13:38|16:13]] | |||
|- id="t16:14:11" | |||
! style="background-color: #4b904b" | red_alert | |||
| style="color: #4b904b" | j_dulaney: any kind of hooks, yes :) | |||
|| [[#t16:14:11|16:14]] | |||
|- id="t16:14:12" | |||
! style="background-color: #854685" | j_dulaney | |||
| style="color: #854685" | IE, integrate in ways for AutoQA to test it easily without having to use the screenshot method? | |||
|| [[#t16:14:12|16:14]] | |||
|- id="t16:14:23" | |||
! style="background-color: #4d4d93" | kparal | |||
| style="color: #4d4d93" | we don't use it at all | |||
|| [[#t16:14:23|16:14]] | |||
|- id="t16:14:34" | |||
| colspan="2" | * j_dulaney is going to have to think on this | |||
|| [[#t16:14:34|16:14]] | |||
|- id="t16:14:38" | |||
! style="background-color: #4d4d93" | kparal | |||
| style="color: #4d4d93" | OTOH I must admit I have not much insight into our current anaconda testing | |||
|| [[#t16:14:38|16:14]] | |||
|- id="t16:15:04" | |||
! style="background-color: #488888" | tflink | |||
| style="color: #488888" | me neither, I don't know the RATS code/tests very well | |||
|| [[#t16:15:04|16:15]] | |||
|- id="t16:15:09" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | who does? | |||
|| [[#t16:15:09|16:15]] | |||
|- id="t16:15:15" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | twu? | |||
|| [[#t16:15:15|16:15]] | |||
|- id="t16:15:21" | |||
! style="background-color: #4d4d93" | kparal | |||
| style="color: #4d4d93" | jlaska and clumens afaik | |||
|| [[#t16:15:21|16:15]] | |||
|- id="t16:15:23" | |||
! style="background-color: #488888" | tflink | |||
| style="color: #488888" | hongquing and twu, I think | |||
|| [[#t16:15:23|16:15]] | |||
|- id="t16:15:53" | |||
! style="background-color: #488888" | tflink | |||
| style="color: #488888" | I answered the wrong question - I was thinking "who's working on it now" | |||
|| [[#t16:15:53|16:15]] | |||
|- id="t16:16:07" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | heh | |||
|| [[#t16:16:07|16:16]] | |||
|- id="t16:16:10" | |||
! style="background-color: #4d4d93" | kparal | |||
| style="color: #4d4d93" | there is a RATS test, the old one. and there are few more anaconda tests which are newer | |||
|| [[#t16:16:10|16:16]] | |||
|- id="t16:16:14" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | sounds like we maybe need to get all of the above together | |||
|| [[#t16:16:14|16:16]] | |||
|- id="t16:16:25" | |||
! style="background-color: #854685" | j_dulaney | |||
| style="color: #854685" | Indeed | |||
|| [[#t16:16:25|16:16]] | |||
|- id="t16:16:32" | |||
! style="background-color: #4d4d93" | kparal | |||
| style="color: #4d4d93" | the new tests use some framework written by clumens afaik | |||
|| [[#t16:16:32|16:16]] | |||
|- id="t16:17:30" | |||
! style="background-color: #4d4d93" | kparal | |||
| style="color: #4d4d93" | james worked with him on intergration | |||
|| [[#t16:17:30|16:17]] | |||
|- id="t16:17:40" | |||
! style="background-color: #4d4d93" | kparal | |||
| style="color: #4d4d93" | the old RATS test was written by wwoods and jlaska I believe | |||
|| [[#t16:17:40|16:17]] | |||
|- id="t16:18:05" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | kparal: it sounds like you kind of know what's going on there: can I ask you to try and get an email thread going with the parties concerned, either directly or cc them on an anaconda list thread? | |||
|| [[#t16:18:05|16:18]] | |||
|- id="t16:18:27" | |||
! style="background-color: #488888" | tflink | |||
| style="color: #488888" | what about the installation tests that twu and hongquing are working on? Is that something different? | |||
|| [[#t16:18:27|16:18]] | |||
|- id="t16:18:35" | |||
| colspan="2" | * kparal look forward to having an action item | |||
|| [[#t16:18:35|16:18]] | |||
|- id="t16:18:49" | |||
! style="background-color: #4d4d93" | kparal | |||
| style="color: #4d4d93" | tflink: I have to say I don't know | |||
|| [[#t16:18:49|16:18]] | |||
|- id="t16:19:04" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | view it as a wonderful opportunity to find out :) | |||
|| [[#t16:19:04|16:19]] | |||
|- id="t16:19:10" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | but it sure sounds like we need to get ducks in a row there. | |||
|| [[#t16:19:10|16:19]] | |||
|- id="t16:19:13" | |||
! style="background-color: #4d4d93" | kparal | |||
| style="color: #4d4d93" | honqginq worked on media sanity test, which is a different topic | |||
|| [[#t16:19:13|16:19]] | |||
|- id="t16:19:31" | |||
! style="background-color: #488888" | tflink | |||
| style="color: #488888" | ah, maybe I'm getting the different tests confused | |||
|| [[#t16:19:31|16:19]] | |||
|- id="t16:19:48" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | #action kparal to try and co-ordinate all involved in writing installer autoqa tests together to determine if we need any hooks in the new anaconda code | |||
|| [[#t16:19:48|16:19]] | |||
|- id="t16:19:53" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | sound good? | |||
|| [[#t16:19:53|16:19]] | |||
|- id="t16:20:00" | |||
! style="background-color: #4d4d93" | kparal | |||
| style="color: #4d4d93" | yep | |||
|| [[#t16:20:00|16:20]] | |||
|- id="t16:20:19" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | alrighty | |||
|| [[#t16:20:19|16:20]] | |||
|- id="t16:20:25" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | any time you're feeling like an action item, you come ask me ;) | |||
|| [[#t16:20:25|16:20]] | |||
|- id="t16:20:34" | |||
! style="background-color: #4d4d93" | kparal | |||
| style="color: #4d4d93" | will do :) | |||
|| [[#t16:20:34|16:20]] | |||
|- id="t16:20:42" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | #topic Fedora 17 Test Day planning | |||
|| [[#t16:20:42|16:20]] | |||
|- id="t16:20:46" | |||
| colspan="2" | * j_dulaney wants an action item | |||
|| [[#t16:20:46|16:20]] | |||
|- id="t16:20:53" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | you can have this one if you want! | |||
|| [[#t16:20:53|16:20]] | |||
|- id="t16:21:05" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | so i wanted to throw this one open: we need to set up the F17 test day cycle | |||
|| [[#t16:21:05|16:21]] | |||
|- id="t16:21:30" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | up till f16 jlaska and I mostly handled this, but i'm still buried in todo list and it'd be nice to give someone else a shake at it too | |||
|| [[#t16:21:30|16:21]] | |||
|- id="t16:21:37" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | new ideas, raptor proofing, etc etc | |||
|| [[#t16:21:37|16:21]] | |||
|- id="t16:22:17" | |||
! style="background-color: #854685" | j_dulaney | |||
| style="color: #854685" | Raptors? | |||
|| [[#t16:22:17|16:22]] | |||
|- id="t16:22:30" | |||
| colspan="2" | * j_dulaney is more worried about ponies. They sneak up on you | |||
|| [[#t16:22:30|16:22]] | |||
|- id="t16:22:39" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | pony vs. raptor! | |||
|| [[#t16:22:39|16:22]] | |||
|- id="t16:22:40" | |||
! style="background-color: #488888" | tflink | |||
| style="color: #488888" | j_dulaney: if someone gets eaten by a raptor, there is enough knowlege around to get the job done | |||
|| [[#t16:22:40|16:22]] | |||
|- id="t16:22:46" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | ...or a pony. | |||
|| [[#t16:22:46|16:22]] | |||
|- id="t16:23:00" | |||
! style="background-color: #488888" | tflink | |||
| style="color: #488888" | or hit by a bus, choose your poison | |||
|| [[#t16:23:00|16:23]] | |||
|- id="t16:23:12" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | hit by a bus driven by a pony which is being eaten by a raptor? | |||
|| [[#t16:23:12|16:23]] | |||
|- id="t16:23:28" | |||
! style="background-color: #854685" | j_dulaney | |||
| style="color: #854685" | Odd | |||
|| [[#t16:23:28|16:23]] | |||
|- id="t16:23:41" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | that'd get you in the papers. | |||
|| [[#t16:23:41|16:23]] | |||
|- id="t16:23:57" | |||
! style="background-color: #854685" | j_dulaney | |||
| style="color: #854685" | Indeed | |||
|| [[#t16:23:57|16:23]] | |||
|- id="t16:24:04" | |||
! style="background-color: #854685" | j_dulaney | |||
| style="color: #854685" | Not in a way I want, though | |||
|| [[#t16:24:04|16:24]] | |||
|- id="t16:24:06" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | heh | |||
|| [[#t16:24:06|16:24]] | |||
|- id="t16:24:44" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | so, basically this involves setting up the test day schedule - which is really just a table on the wiki you can copy and paste from the f16 one - then helping people to organize and promote the events | |||
|| [[#t16:24:44|16:24]] | |||
|- id="t16:24:58" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | you won't actually have to do all the work for every test day yourself, or even show up at all of them, it's more co-ordination | |||
|| [[#t16:24:58|16:24]] | |||
|- id="t16:25:05" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | so anyone feel like giving that a shot? | |||
|| [[#t16:25:05|16:25]] | |||
|- id="t16:25:06" | |||
| colspan="2" | * j_dulaney will do it | |||
|| [[#t16:25:06|16:25]] | |||
|- id="t16:25:29" | |||
! style="background-color: #854685" | j_dulaney | |||
| style="color: #854685" | Sounds easy enough, just make sure everything is on a Thursday? | |||
|| [[#t16:25:29|16:25]] | |||
|- id="t16:26:21" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | ideally keep things on a thursday | |||
|| [[#t16:26:21|16:26]] | |||
|- id="t16:26:27" | |||
! style="background-color: #854685" | j_dulaney | |||
| style="color: #854685" | Indeed | |||
|| [[#t16:26:27|16:26]] | |||
|- id="t16:26:40" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | but if all the slots are full and someone has a worthwhile idea, you can overflow to other days (usually tuesday) | |||
|| [[#t16:26:40|16:26]] | |||
|- id="t16:27:00" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | and sometimes we do 'test weeks' when people want to do a series of related events (like X test week, or the i18n/l10n week we had last cycle) | |||
|| [[#t16:27:00|16:27]] | |||
|- id="t16:27:16" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | i'll help you out as you go, anyways - any questions, just poke me or the list | |||
|| [[#t16:27:16|16:27]] | |||
|- id="t16:27:20" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | thanks for stepping up! | |||
|| [[#t16:27:20|16:27]] | |||
|- id="t16:27:33" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | #action j_dulaney to take a shot at co-ordinating F17 test days, thanks! | |||
|| [[#t16:27:33|16:27]] | |||
|- id="t16:27:41" | |||
! style="background-color: #4b904b" | red_alert | |||
| style="color: #4b904b" | don't forget that some developers are in different timezones, and so are testers :) just saying | |||
|| [[#t16:27:41|16:27]] | |||
|- id="t16:27:44" | |||
! style="background-color: #854685" | j_dulaney | |||
| style="color: #854685" | Roger that | |||
|| [[#t16:27:44|16:27]] | |||
|- id="t16:28:47" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | #topic Upcoming QA events | |||
|| [[#t16:28:47|16:28]] | |||
|- id="t16:28:55" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | so i threw this in the schedule, but i'm not sure we actually have any | |||
|| [[#t16:28:55|16:28]] | |||
|- id="t16:29:12" | |||
! style="background-color: #854685" | j_dulaney | |||
| style="color: #854685" | How's the post-F16 stuff coming? | |||
|| [[#t16:29:12|16:29]] | |||
|- id="t16:29:34" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | busted! | |||
|| [[#t16:29:34|16:29]] | |||
|- id="t16:29:53" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | retrospective is the next thing on my todo list | |||
|| [[#t16:29:53|16:29]] | |||
|- id="t16:29:57" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | so expect that this week sometime | |||
|| [[#t16:29:57|16:29]] | |||
|- id="t16:30:09" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | #action adamw to get retrospective tickets filed and summary mailed this week | |||
|| [[#t16:30:09|16:30]] | |||
|- id="t16:30:37" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | the preliminary f17 schedule is up at http://rbergero.fedorapeople.org/schedules/f-17/f-17-quality-tasks.html | |||
|| [[#t16:30:37|16:30]] | |||
|- id="t16:30:47" | |||
! style="background-color: #8c4a4a" | rbergeron | |||
| style="color: #8c4a4a" | feel free to send me any updates :) | |||
|| [[#t16:30:47|16:30]] | |||
|- id="t16:30:58" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | yeah, we probably will want to change acceptance tests into TCs again | |||
|| [[#t16:30:58|16:30]] | |||
|- id="t16:30:59" | |||
! style="background-color: #8c4a4a" | rbergeron | |||
| style="color: #8c4a4a" | (which will probably come out of any retrospective stuff) | |||
|| [[#t16:30:59|16:30]] | |||
|- id="t16:31:02" | |||
! style="background-color: #854685" | j_dulaney | |||
| style="color: #854685" | Assuming FESCo accepts it | |||
|| [[#t16:31:02|16:31]] | |||
|- id="t16:31:09" | |||
! style="background-color: #8c4a4a" | rbergeron | |||
| style="color: #8c4a4a" | j_dulaney: they accepted it | |||
|| [[#t16:31:09|16:31]] | |||
|- id="t16:31:09" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | but we'll look at that and let you know | |||
|| [[#t16:31:09|16:31]] | |||
|- id="t16:31:14" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | j_dulaney: heh. | |||
|| [[#t16:31:14|16:31]] | |||
|- id="t16:31:36" | |||
! style="background-color: #854685" | j_dulaney | |||
| style="color: #854685" | Bumping the TCs forward a week did seem to help | |||
|| [[#t16:31:36|16:31]] | |||
|- id="t16:31:51" | |||
! style="background-color: #8c4a4a" | rbergeron | |||
| style="color: #8c4a4a" | though i don't know if fesco needs to approve calling acceptance tests TCs but.... | |||
|| [[#t16:31:51|16:31]] | |||
|- id="t16:31:56" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | yeah, and i think the reasoning about RATS still helps | |||
|| [[#t16:31:56|16:31]] | |||
|- id="t16:32:06" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | rbergeron: i think j_dulaney meant 'assuming fesco accepts the f17 schedule in general' | |||
|| [[#t16:32:06|16:32]] | |||
|- id="t16:32:14" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | s/helps/stands/ | |||
|| [[#t16:32:14|16:32]] | |||
|- id="t16:32:26" | |||
! style="background-color: #854685" | j_dulaney | |||
| style="color: #854685" | adamw: Indeed | |||
|| [[#t16:32:26|16:32]] | |||
|- id="t16:33:15" | |||
! style="background-color: #8c4a4a" | rbergeron | |||
| style="color: #8c4a4a" | okay. well, they accepted it :) | |||
|| [[#t16:33:15|16:33]] | |||
|- id="t16:33:35" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | awesome | |||
|| [[#t16:33:35|16:33]] | |||
|- id="t16:34:10" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | #action adamw to start an ml thread proposing changes to the tc dates for f17 schedule to be sent to rbergeron | |||
|| [[#t16:34:10|16:34]] | |||
|- id="t16:34:30" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | anything else on upcoming events? | |||
|| [[#t16:34:30|16:34]] | |||
|- id="t16:34:49" | |||
! style="background-color: #8c4a4a" | rbergeron | |||
| style="color: #8c4a4a" | If anyone is going to FUDCon, please sign up, if you need funding, file your ticket, EOF :) | |||
|| [[#t16:34:49|16:34]] | |||
|- id="t16:36:30" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | alrighty! | |||
|| [[#t16:36:30|16:36]] | |||
|- id="t16:36:50" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | #info if you're planning on going to FUDCon please sign up, and if you need funding, file a ticket now | |||
|| [[#t16:36:50|16:36]] | |||
|- id="t16:37:01" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | now, it's the moment we've all been waiting for... | |||
|| [[#t16:37:01|16:37]] | |||
|- id="t16:37:04" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | #topic autoqa update | |||
|| [[#t16:37:04|16:37]] | |||
|- id="t16:37:16" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | #chair kparal | |||
|| [[#t16:37:16|16:37]] | |||
|- id="t16:37:16" | |||
! style="background-color: #42427e" | zodbot | |||
| style="color: #42427e" | Current chairs: adamw j_dulaney kparal tflink | |||
|| [[#t16:37:16|16:37]] | |||
|- id="t16:37:17" | |||
! style="background-color: #488888" | tflink | |||
| style="color: #488888" | adamw: we have? | |||
|| [[#t16:37:17|16:37]] | |||
|- id="t16:37:20" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | tflink, kparal, what's the news? | |||
|| [[#t16:37:20|16:37]] | |||
|- id="t16:37:26" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | well *I*'ve been waiting all weekend | |||
|| [[#t16:37:26|16:37]] | |||
|- id="t16:37:39" | |||
! style="background-color: #488888" | tflink | |||
| style="color: #488888" | we're still getting ready to deploy autoqa 0.7.0 | |||
|| [[#t16:37:39|16:37]] | |||
|- id="t16:37:41" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | (with my finger hovering over the 'fired' button) | |||
|| [[#t16:37:41|16:37]] | |||
|- id="t16:37:58" | |||
! style="background-color: #488888" | tflink | |||
| style="color: #488888" | a couple of bugs were found and fixed last week with YOURLS integration and the new logging system | |||
|| [[#t16:37:58|16:37]] | |||
|- id="t16:38:07" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | cool | |||
|| [[#t16:38:07|16:38]] | |||
|- id="t16:38:16" | |||
! style="background-color: #4d4d93" | kparal | |||
| style="color: #4d4d93" | kudos to tflink | |||
|| [[#t16:38:16|16:38]] | |||
|- id="t16:38:32" | |||
! style="background-color: #488888" | tflink | |||
| style="color: #488888" | we still need to schedule downtime for the AutoQA system and figure out when we're going to push out to production | |||
|| [[#t16:38:32|16:38]] | |||
|- id="t16:38:49" | |||
! style="background-color: #4d4d93" | kparal | |||
| style="color: #4d4d93" | this week probably | |||
|| [[#t16:38:49|16:38]] | |||
|- id="t16:39:00" | |||
! style="background-color: #488888" | tflink | |||
| style="color: #488888" | almost all of the test client HW is still running F14, so we have some upgrades to do | |||
|| [[#t16:39:00|16:39]] | |||
|- id="t16:39:10" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | question: is there a plan/schedule to get the results mails back up? | |||
|| [[#t16:39:10|16:39]] | |||
|- id="t16:39:16" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | or are we just waiting for resultsdb now? | |||
|| [[#t16:39:16|16:39]] | |||
|- id="t16:39:18" | |||
! style="background-color: #4d4d93" | kparal | |||
| style="color: #4d4d93" | great question | |||
|| [[#t16:39:18|16:39]] | |||
|- id="t16:39:26" | |||
! style="background-color: #488888" | tflink | |||
| style="color: #488888" | the conversation hasn't come up yet | |||
|| [[#t16:39:26|16:39]] | |||
|- id="t16:39:34" | |||
! style="background-color: #488888" | tflink | |||
| style="color: #488888" | not in detail, anyways | |||
|| [[#t16:39:34|16:39]] | |||
|- id="t16:39:41" | |||
! style="background-color: #4d4d93" | kparal | |||
| style="color: #4d4d93" | I think I proposed some solutions in that thread | |||
|| [[#t16:39:41|16:39]] | |||
|- id="t16:40:04" | |||
! style="background-color: #4d4d93" | kparal | |||
| style="color: #4d4d93" | I'll try to revive that conversation | |||
|| [[#t16:40:04|16:40]] | |||
|- id="t16:40:12" | |||
! style="background-color: #488888" | tflink | |||
| style="color: #488888" | have there been requests for the emails to come back? | |||
|| [[#t16:40:12|16:40]] | |||
|- id="t16:40:38" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | i haven't had any, i just was reminded when i was catching up on the meeting summaries last week | |||
|| [[#t16:40:38|16:40]] | |||
|- id="t16:40:54" | |||
| colspan="2" | * j_dulaney got the impression from Infranstructure that they don't want to serve the huge number of emails, for sure | |||
|| [[#t16:40:54|16:40]] | |||
|- id="t16:42:06" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | j_dulaney: that's the reason it was shut down, yes | |||
|| [[#t16:42:06|16:42]] | |||
|- id="t16:42:15" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | j_dulaney: so we need some kind of plan to reduce the volume to get them back up again | |||
|| [[#t16:42:15|16:42]] | |||
|- id="t16:42:34" | |||
! style="background-color: #488888" | tflink | |||
| style="color: #488888" | assuming we want to spam a list with all results, anyways | |||
|| [[#t16:42:34|16:42]] | |||
|- id="t16:42:50" | |||
! style="background-color: #488888" | tflink | |||
| style="color: #488888" | but that conversation would best be saved for the lists | |||
|| [[#t16:42:50|16:42]] | |||
|- id="t16:42:51" | |||
| colspan="2" | * j_dulaney is leaning for resultsdb | |||
|| [[#t16:42:51|16:42]] | |||
|- id="t16:42:53" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | okay | |||
|| [[#t16:42:53|16:42]] | |||
|- id="t16:42:56" | |||
! style="background-color: #854685" | j_dulaney | |||
| style="color: #854685" | Indeed | |||
|| [[#t16:42:56|16:42]] | |||
|- id="t16:43:01" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | yeah, i just wanted to highlight it as an 'unresolved issue' | |||
|| [[#t16:43:01|16:43]] | |||
|- id="t16:43:34" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | #info autoqa 0.7.0 deployment still in planning | |||
|| [[#t16:43:34|16:43]] | |||
|- id="t16:43:45" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | #info autoqa test client hardware is still running F14, so needs to be upgraded | |||
|| [[#t16:43:45|16:43]] | |||
|- id="t16:44:11" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | anything there you need help with or is it all under control? | |||
|| [[#t16:44:11|16:44]] | |||
|- id="t16:44:41" | |||
! style="background-color: #488888" | tflink | |||
| style="color: #488888" | I think its all under control | |||
|| [[#t16:44:41|16:44]] | |||
|- id="t16:45:13" | |||
! style="background-color: #488888" | tflink | |||
| style="color: #488888" | we just need to hammer out a time for all the upgrades once we're satisfied with the code | |||
|| [[#t16:45:13|16:45]] | |||
|- id="t16:45:23" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | okay, great | |||
|| [[#t16:45:23|16:45]] | |||
|- id="t16:45:29" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | any other news? | |||
|| [[#t16:45:29|16:45]] | |||
|- id="t16:45:44" | |||
! style="background-color: #488888" | tflink | |||
| style="color: #488888" | nothing I can think of for autoqa | |||
|| [[#t16:45:44|16:45]] | |||
|- id="t16:46:10" | |||
! style="background-color: #854685" | j_dulaney | |||
| style="color: #854685" | Nothing here, either | |||
|| [[#t16:46:10|16:46]] | |||
|- id="t16:46:31" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | okey dokey | |||
|| [[#t16:46:31|16:46]] | |||
|- id="t16:46:32" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | thanks | |||
|| [[#t16:46:32|16:46]] | |||
|- id="t16:46:36" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | #topic open floor | |||
|| [[#t16:46:36|16:46]] | |||
|- id="t16:46:49" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | so, anything I missed? anyone have great ideas to forward the noble Project Colada goal? | |||
|| [[#t16:46:49|16:46]] | |||
|- id="t16:47:01" | |||
! style="background-color: #4d4d93" | kparal | |||
| style="color: #4d4d93" | I want to have a quick chat about current QA priorities | |||
|| [[#t16:47:01|16:47]] | |||
|- id="t16:47:09" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | #topic open floor - current QA priorities | |||
|| [[#t16:47:09|16:47]] | |||
|- id="t16:47:12" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | go for it! | |||
|| [[#t16:47:12|16:47]] | |||
|- id="t16:47:41" | |||
! style="background-color: #4d4d93" | kparal | |||
| style="color: #4d4d93" | so basically, I spent the last week reporting tuns of bugs for F16, tflink worked on autoqa and adamw posted a few internal calls for volunteers in different areas | |||
|| [[#t16:47:41|16:47]] | |||
|- id="t16:47:53" | |||
! style="background-color: #4d4d93" | kparal | |||
| style="color: #4d4d93" | so, do we have any priorities regarding all these areas? | |||
|| [[#t16:47:53|16:47]] | |||
|- id="t16:48:00" | |||
! style="background-color: #4d4d93" | kparal | |||
| style="color: #4d4d93" | just curious | |||
|| [[#t16:48:00|16:48]] | |||
|- id="t16:48:55" | |||
! style="background-color: #4d4d93" | kparal | |||
| style="color: #4d4d93" | like do we want to spend much time on improving wiki test cases first, or is autoqa hacking more important now? | |||
|| [[#t16:48:55|16:48]] | |||
|- id="t16:49:03" | |||
| colspan="2" | * j_dulaney is wanting to hop back on AutoQA | |||
|| [[#t16:49:03|16:49]] | |||
|- id="t16:49:32" | |||
! style="background-color: #854685" | j_dulaney | |||
| style="color: #854685" | I've also kind of been hijacked into doing sysv to systemd init conversions | |||
|| [[#t16:49:32|16:49]] | |||
|- id="t16:49:33" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | for the public record, i was looking for volunteers for the Test Day thing which is now covered, updating/revising the validation test plans, and checking the F17 feature list for critical things that will need test plans | |||
|| [[#t16:49:33|16:49]] | |||
|- id="t16:50:16" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | kparal: so the wishy-washy answer is 'they're all important' :) | |||
|| [[#t16:50:16|16:50]] | |||
|- id="t16:50:28" | |||
! style="background-color: #488888" | tflink | |||
| style="color: #488888" | adamw: thanks, that helps a lot | |||
|| [[#t16:50:28|16:50]] | |||
|- id="t16:50:30" | |||
! style="background-color: #488888" | tflink | |||
| style="color: #488888" | :-D | |||
|| [[#t16:50:30|16:50]] | |||
|- id="t16:50:31" | |||
! style="background-color: #4d4d93" | kparal | |||
| style="color: #4d4d93" | :D | |||
|| [[#t16:50:31|16:50]] | |||
|- id="t16:50:35" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | kparal: autoqa is a kind of ongoing priority which is never an emergency | |||
|| [[#t16:50:35|16:50]] | |||
|- id="t16:50:54" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | the challenge there is to try and avoid always pulling people off autoqa to firefight whatever the current emergency is | |||
|| [[#t16:50:54|16:50]] | |||
|- id="t16:51:18" | |||
! style="background-color: #4d4d93" | kparal | |||
| style="color: #4d4d93" | I can help with those validation test plans, but I simply don't know whether I should rather work on autoqa or not | |||
|| [[#t16:51:18|16:51]] | |||
|- id="t16:51:30" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | i think you should probably prioritize autoqa | |||
|| [[#t16:51:30|16:51]] | |||
|- id="t16:51:40" | |||
| colspan="2" | * j_dulaney can do test plans | |||
|| [[#t16:51:40|16:51]] | |||
|- id="t16:51:48" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | so the thing there is that autoqa requires more advanced knowledge/skills than just about any other area | |||
|| [[#t16:51:48|16:51]] | |||
|- id="t16:52:15" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | so the people who have the knowledge/skills to work on autoqa should probably focus on it, because otherwise it just won't get done | |||
|| [[#t16:52:15|16:52]] | |||
|- id="t16:52:50" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | we should be able to cover all the other tasks between rh staff and community, i think | |||
|| [[#t16:52:50|16:52]] | |||
|- id="t16:52:52" | |||
! style="background-color: #4d4d93" | kparal | |||
| style="color: #4d4d93" | ok, that helps me with my bad conscience that I haven't responded to your call yet | |||
|| [[#t16:52:52|16:52]] | |||
|- id="t16:53:19" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | j_dulaney: thanks a lot, but if possible i'd like to try and get someone else on it, just to spread the load a little - it's unfair to you to try and carry two major areas | |||
|| [[#t16:53:19|16:53]] | |||
|- id="t16:53:47" | |||
! style="background-color: #854685" | j_dulaney | |||
| style="color: #854685" | I'm about to have A LOT of free time | |||
|| [[#t16:53:47|16:53]] | |||
|- id="t16:54:25" | |||
! style="background-color: #854685" | j_dulaney | |||
| style="color: #854685" | The next two weeks are going to suck, then I'll have a little over a month of free time | |||
|| [[#t16:54:25|16:54]] | |||
|- id="t16:54:42" | |||
! style="background-color: #4d4d93" | kparal | |||
| style="color: #4d4d93" | so from what I got - autoqa is a high priority, no slacking elsewhere, right? | |||
|| [[#t16:54:42|16:54]] | |||
|- id="t16:55:23" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | kparal: yeah. if we really can't cover everything else we might need to ask you to do some non-autoqa stuff, but it'd be ideal if we could cover things without that. | |||
|| [[#t16:55:23|16:55]] | |||
|- id="t16:55:52" | |||
! style="background-color: #4d4d93" | kparal | |||
| style="color: #4d4d93" | ok | |||
|| [[#t16:55:52|16:55]] | |||
|- id="t16:56:31" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | j_dulaney: great - if it turns out no-one else steps up to do that then we'll impose it on you :) | |||
|| [[#t16:56:31|16:56]] | |||
|- id="t16:56:43" | |||
! style="background-color: #854685" | j_dulaney | |||
| style="color: #854685" | Indeed | |||
|| [[#t16:56:43|16:56]] | |||
|- id="t16:56:46" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | so, this topic also ties up with the retrospective somewhat | |||
|| [[#t16:56:46|16:56]] | |||
|- id="t16:56:57" | |||
! style="background-color: #854685" | j_dulaney | |||
| style="color: #854685" | Except that I'm fired (: | |||
|| [[#t16:56:57|16:56]] | |||
|- id="t16:57:10" | |||
! style="background-color: #4d4d93" | kparal | |||
| style="color: #4d4d93" | j_dulaney: more free time to work! | |||
|| [[#t16:57:10|16:57]] | |||
|- id="t16:57:12" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | we will likely have tickets for all the outstanding tasks once i'm done with the retrospective and we can try and make sure they're all prioritized and assigned at that point | |||
|| [[#t16:57:12|16:57]] | |||
|- id="t16:57:22" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | kparal: exACTly! | |||
|| [[#t16:57:22|16:57]] | |||
|- id="t16:59:41" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | #info all outstanding tasks should have trac tickets by the end of the week, which will help with assignation / prioritization | |||
|| [[#t16:59:41|16:59]] | |||
|- id="t16:59:48" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | does that cover it, kparal? | |||
|| [[#t16:59:48|16:59]] | |||
|- id="t16:59:59" | |||
| colspan="2" | * nirik has one quick item for open floor. | |||
|| [[#t16:59:59|16:59]] | |||
|- id="t17:00:03" | |||
! style="background-color: #4d4d93" | kparal | |||
| style="color: #4d4d93" | it does for me | |||
|| [[#t17:00:03|17:00]] | |||
|- id="t17:00:27" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | nirik: okay, do we have time though? | |||
|| [[#t17:00:27|17:00]] | |||
|- id="t17:00:32" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | is someone else tapping feet for the room? | |||
|| [[#t17:00:32|17:00]] | |||
|- id="t17:00:55" | |||
! style="background-color: #488888" | tflink | |||
| style="color: #488888" | IIRC, the next meeting shifted an hour | |||
|| [[#t17:00:55|17:00]] | |||
|- id="t17:00:57" | |||
! style="background-color: #97974f" | nirik | |||
| style="color: #97974f" | I just wanted to mention: http://lists.fedoraproject.org/pipermail/infrastructure/2011-November/011151.html (I will probibly be announcing it more widely soon). | |||
|| [[#t17:00:57|17:00]] | |||
|- id="t17:01:05" | |||
! style="background-color: #97974f" | nirik | |||
| style="color: #97974f" | adamw: fesco moved an hour I think... | |||
|| [[#t17:01:05|17:01]] | |||
|- id="t17:01:44" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | okay | |||
|| [[#t17:01:44|17:01]] | |||
|- id="t17:02:07" | |||
! style="background-color: #97974f" | nirik | |||
| style="color: #97974f" | so, if anyone wants to test new trac/scms for fedorahosted, please do. | |||
|| [[#t17:02:07|17:02]] | |||
|- id="t17:02:08" | |||
! style="background-color: #97974f" | nirik | |||
| style="color: #97974f" | :) | |||
|| [[#t17:02:08|17:02]] | |||
|- id="t17:02:36" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | #info infrastructure team is calling for testing of a rhel6-based fedorahosted.org , see nirik's link for more details | |||
|| [[#t17:02:36|17:02]] | |||
|- id="t17:02:39" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | alrighty! | |||
|| [[#t17:02:39|17:02]] | |||
|- id="t17:02:44" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | #topic open floor | |||
|| [[#t17:02:44|17:02]] | |||
|- id="t17:02:47" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | anything more? | |||
|| [[#t17:02:47|17:02]] | |||
|- id="t17:03:33" | |||
| colspan="2" | * j_dulaney has nothing | |||
|| [[#t17:03:33|17:03]] | |||
|- id="t17:03:54" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | alrighty, setting fuse for 1 minute then | |||
|| [[#t17:03:54|17:03]] | |||
|- id="t17:05:14" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | thanks folks! | |||
|| [[#t17:05:14|17:05]] | |||
|- id="t17:05:16" | |||
! style="background-color: #407a40" | adamw | |||
| style="color: #407a40" | #endmeeting | |||
|| [[#t17:05:16|17:05]] | |||
|} | |||
Generated by irclog2html.py 2.8 by [mailto:marius@pov.lt Marius Gedminas] - find it at [http://mg.pov.lt/irclog2html mg.pov.lt]! |
Revision as of 00:36, 22 November 2011
Attendees
- adamw (130)
- j_dulaney (43)
- kparal (31)
- tflink (27)
- red_alert (8)
- rbergeron (7)
- zodbot (6)
- nirik (5)
- jskladan (2)
- brunowolff (1)
- pschindl (1)
Agenda
Previous meeting follow-up
- Nothing from previous short meeting required follow-up
FUDCon NA hackfest planning
- Plan to get anaconda and QA teams together to organize/conduct testing of new UI
- We have room 3 on Sunday from 0900 to 1400
- FUDCon is too late to notify if we need hooks written into the new UI for testing
- kparal will investigate whether such hooks are needed and notify anaconda team
Fedora 17 Test Day planning
- j_dulaney will act as Fedora 17 Test Day co-ordinator, adamw will help him get going
Upcoming QA events
- adamw will get F16 retrospective summary posted and tickets filed this week
- We need to agree on how to schedule TCs for F17 and communicate that to rbergeron - scheduling them early for F16 seemed to be a good idea
AutoQA update
- Team is still preparing for AutoQA 0.7.0 deployment: need to decide when to schedule downtime
- Test client hardware needs to be upgraded from Fedora 14 to Fedora 16
- Results mails are still disabled, need a list discussion about whether to try and revive them or wait for resultsdb
Open floor
- kparal asked about relative priorities of various tasks: autoqa, validation test plan updates, test day organization, creating test plans for major F17 features
- adamw said they're all important but those with the skills for autoqa should focus on it
- adamw will try to ensure all outstanding tasks have tickets filed by end of week
- infrastructure team is calling for testing of a rhel6-based fedorahosted.org , see here for more details
IRC Log
adamw | #startmeeting Fedora QA Meeting | 16:01 |
---|---|---|
zodbot | Meeting started Mon Nov 21 16:01:21 2011 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 |
jskladan | j_dulaney: hey there | 16:01 |
adamw | #topic roll call | 16:01 |
adamw | alright, who's around? | 16:01 |
* tflink is here | 16:01 | |
* jskladan is ready to rock'n'roll | 16:01 | |
* red_alert | 16:01 | |
* j_dulaney is rocking out to Rammstein | 16:01 | |
* j_dulaney will probably not be able to hear when it's all said and done | 16:02 | |
adamw | hey, lookit that, when i actually manage to announce the meeting, people show up | 16:02 |
* brunowolff is for a short while. I have a meeting at work at half past. | 16:02 | |
adamw | it's like magic or something | 16:02 |
* kparal pops up | 16:02 | |
* adamw whacks kparal | 16:02 | |
* j_dulaney plays whack-a-kparal | 16:03 | |
j_dulaney | adamw is a wizard | 16:03 |
* kparal pops off | 16:03 | |
adamw | beat you to it | 16:03 |
* j_dulaney whacks adamw | 16:03 | |
j_dulaney | I win | 16:03 |
adamw | oh THAT'S how it's going to be? | 16:03 |
adamw | you're fired! | 16:03 |
adamw | alrighty | 16:04 |
* pschindl is here | 16:04 | |
tflink | how exactly do you fire someone who doesn't work for you? | 16:04 |
adamw | tflink: it's difficult, i admit, but i studied hard | 16:04 |
rbergeron | tflink: LOL | 16:04 |
adamw | i have many methods | 16:04 |
j_dulaney | Well, since I'm fired... | 16:04 |
* j_dulaney gets to slack off! | 16:05 | |
adamw | i'll probably plant a bottle of jack in his desk drawer and call his boss | 16:05 |
tflink | j_dulaney: is that how it works? Dang, I wish I would have know that, I could have been slacking for a month or two | 16:05 |
adamw | =) | 16:05 |
j_dulaney | LOL | 16:05 |
adamw | #topic previous meeting follow-up | 16:05 |
adamw | nothing really doing here, since last week was a short, quiet meeting | 16:06 |
adamw | no action items | 16:06 |
* j_dulaney was halfway between Winston-Salem and Fayetteville during the last meeting | 16:06 | |
adamw | and still had a job! | 16:06 |
j_dulaney | Indeed | 16:07 |
adamw | #info no action items from previous meeting on which to follow up | 16:07 |
adamw | #topic FUDCon NA hackfest planning | 16:07 |
adamw | so, I think red_alert has been doing some work on this | 16:07 |
adamw | where are we atm? | 16:07 |
adamw | #chair tflink | 16:07 |
zodbot | Current chairs: adamw tflink | 16:07 |
adamw | #chair j_dulaney | 16:07 |
zodbot | Current chairs: adamw j_dulaney tflink | 16:07 |
red_alert | well, we have room and time reserved | 16:08 |
red_alert | anacodna folks know about it and at least clumens likes the idea :) | 16:08 |
tflink | red_alert: for the Anaconda testing hackfest? | 16:08 |
red_alert | tflink: yes | 16:08 |
adamw | yeah, background is good for those who haven't heard | 16:08 |
adamw | #link https://www.redhat.com/archives/anaconda-devel-list/2011-November/msg00055.html | 16:09 |
red_alert | basically we'll sit together for ~4h and talk/do whatever needs to be talked/done. so far we think no strict agenda is needed and everyone will just bring in his topics as necessary | 16:10 |
j_dulaney | #info We have room 3 on Sunday from 0900 to 1400 | 16:10 |
adamw | cool | 16:11 |
j_dulaney | Speaking of such, anyone want to room with me? | 16:11 |
adamw | #info plan is to get anaconda and qa teams together to work on testing the new installer UI | 16:12 |
adamw | so, anyone have questions / ideas about the plan? | 16:13 |
red_alert | oh, one important thing clumens mentioned: if things need to be built into the new UI to make it testable that needs to be defined ~now, i.e. FUDCon will be too late | 16:13 |
j_dulaney | AutoQA test hooks? | 16:13 |
adamw | #info if we need things coded into the UI to make it testable we have to say so now | 16:13 |
red_alert | j_dulaney: any kind of hooks, yes :) | 16:14 |
j_dulaney | IE, integrate in ways for AutoQA to test it easily without having to use the screenshot method? | 16:14 |
kparal | we don't use it at all | 16:14 |
* j_dulaney is going to have to think on this | 16:14 | |
kparal | OTOH I must admit I have not much insight into our current anaconda testing | 16:14 |
tflink | me neither, I don't know the RATS code/tests very well | 16:15 |
adamw | who does? | 16:15 |
adamw | twu? | 16:15 |
kparal | jlaska and clumens afaik | 16:15 |
tflink | hongquing and twu, I think | 16:15 |
tflink | I answered the wrong question - I was thinking "who's working on it now" | 16:15 |
adamw | heh | 16:16 |
kparal | there is a RATS test, the old one. and there are few more anaconda tests which are newer | 16:16 |
adamw | sounds like we maybe need to get all of the above together | 16:16 |
j_dulaney | Indeed | 16:16 |
kparal | the new tests use some framework written by clumens afaik | 16:16 |
kparal | james worked with him on intergration | 16:17 |
kparal | the old RATS test was written by wwoods and jlaska I believe | 16:17 |
adamw | kparal: it sounds like you kind of know what's going on there: can I ask you to try and get an email thread going with the parties concerned, either directly or cc them on an anaconda list thread? | 16:18 |
tflink | what about the installation tests that twu and hongquing are working on? Is that something different? | 16:18 |
* kparal look forward to having an action item | 16:18 | |
kparal | tflink: I have to say I don't know | 16:18 |
adamw | view it as a wonderful opportunity to find out :) | 16:19 |
adamw | but it sure sounds like we need to get ducks in a row there. | 16:19 |
kparal | honqginq worked on media sanity test, which is a different topic | 16:19 |
tflink | ah, maybe I'm getting the different tests confused | 16:19 |
adamw | #action kparal to try and co-ordinate all involved in writing installer autoqa tests together to determine if we need any hooks in the new anaconda code | 16:19 |
adamw | sound good? | 16:19 |
kparal | yep | 16:20 |
adamw | alrighty | 16:20 |
adamw | any time you're feeling like an action item, you come ask me ;) | 16:20 |
kparal | will do :) | 16:20 |
adamw | #topic Fedora 17 Test Day planning | 16:20 |
* j_dulaney wants an action item | 16:20 | |
adamw | you can have this one if you want! | 16:20 |
adamw | so i wanted to throw this one open: we need to set up the F17 test day cycle | 16:21 |
adamw | up till f16 jlaska and I mostly handled this, but i'm still buried in todo list and it'd be nice to give someone else a shake at it too | 16:21 |
adamw | new ideas, raptor proofing, etc etc | 16:21 |
j_dulaney | Raptors? | 16:22 |
* j_dulaney is more worried about ponies. They sneak up on you | 16:22 | |
adamw | pony vs. raptor! | 16:22 |
tflink | j_dulaney: if someone gets eaten by a raptor, there is enough knowlege around to get the job done | 16:22 |
adamw | ...or a pony. | 16:22 |
tflink | or hit by a bus, choose your poison | 16:23 |
adamw | hit by a bus driven by a pony which is being eaten by a raptor? | 16:23 |
j_dulaney | Odd | 16:23 |
adamw | that'd get you in the papers. | 16:23 |
j_dulaney | Indeed | 16:23 |
j_dulaney | Not in a way I want, though | 16:24 |
adamw | heh | 16:24 |
adamw | so, basically this involves setting up the test day schedule - which is really just a table on the wiki you can copy and paste from the f16 one - then helping people to organize and promote the events | 16:24 |
adamw | you won't actually have to do all the work for every test day yourself, or even show up at all of them, it's more co-ordination | 16:24 |
adamw | so anyone feel like giving that a shot? | 16:25 |
* j_dulaney will do it | 16:25 | |
j_dulaney | Sounds easy enough, just make sure everything is on a Thursday? | 16:25 |
adamw | ideally keep things on a thursday | 16:26 |
j_dulaney | Indeed | 16:26 |
adamw | but if all the slots are full and someone has a worthwhile idea, you can overflow to other days (usually tuesday) | 16:26 |
adamw | and sometimes we do 'test weeks' when people want to do a series of related events (like X test week, or the i18n/l10n week we had last cycle) | 16:27 |
adamw | i'll help you out as you go, anyways - any questions, just poke me or the list | 16:27 |
adamw | thanks for stepping up! | 16:27 |
adamw | #action j_dulaney to take a shot at co-ordinating F17 test days, thanks! | 16:27 |
red_alert | don't forget that some developers are in different timezones, and so are testers :) just saying | 16:27 |
j_dulaney | Roger that | 16:27 |
adamw | #topic Upcoming QA events | 16:28 |
adamw | so i threw this in the schedule, but i'm not sure we actually have any | 16:28 |
j_dulaney | How's the post-F16 stuff coming? | 16:29 |
adamw | busted! | 16:29 |
adamw | retrospective is the next thing on my todo list | 16:29 |
adamw | so expect that this week sometime | 16:29 |
adamw | #action adamw to get retrospective tickets filed and summary mailed this week | 16:30 |
adamw | the preliminary f17 schedule is up at http://rbergero.fedorapeople.org/schedules/f-17/f-17-quality-tasks.html | 16:30 |
rbergeron | feel free to send me any updates :) | 16:30 |
adamw | yeah, we probably will want to change acceptance tests into TCs again | 16:30 |
rbergeron | (which will probably come out of any retrospective stuff) | 16:30 |
j_dulaney | Assuming FESCo accepts it | 16:31 |
rbergeron | j_dulaney: they accepted it | 16:31 |
adamw | but we'll look at that and let you know | 16:31 |
adamw | j_dulaney: heh. | 16:31 |
j_dulaney | Bumping the TCs forward a week did seem to help | 16:31 |
rbergeron | though i don't know if fesco needs to approve calling acceptance tests TCs but.... | 16:31 |
adamw | yeah, and i think the reasoning about RATS still helps | 16:31 |
adamw | rbergeron: i think j_dulaney meant 'assuming fesco accepts the f17 schedule in general' | 16:32 |
adamw | s/helps/stands/ | 16:32 |
j_dulaney | adamw: Indeed | 16:32 |
rbergeron | okay. well, they accepted it :) | 16:33 |
adamw | awesome | 16:33 |
adamw | #action adamw to start an ml thread proposing changes to the tc dates for f17 schedule to be sent to rbergeron | 16:34 |
adamw | anything else on upcoming events? | 16:34 |
rbergeron | If anyone is going to FUDCon, please sign up, if you need funding, file your ticket, EOF :) | 16:34 |
adamw | alrighty! | 16:36 |
adamw | #info if you're planning on going to FUDCon please sign up, and if you need funding, file a ticket now | 16:36 |
adamw | now, it's the moment we've all been waiting for... | 16:37 |
adamw | #topic autoqa update | 16:37 |
adamw | #chair kparal | 16:37 |
zodbot | Current chairs: adamw j_dulaney kparal tflink | 16:37 |
tflink | adamw: we have? | 16:37 |
adamw | tflink, kparal, what's the news? | 16:37 |
adamw | well *I*'ve been waiting all weekend | 16:37 |
tflink | we're still getting ready to deploy autoqa 0.7.0 | 16:37 |
adamw | (with my finger hovering over the 'fired' button) | 16:37 |
tflink | a couple of bugs were found and fixed last week with YOURLS integration and the new logging system | 16:37 |
adamw | cool | 16:38 |
kparal | kudos to tflink | 16:38 |
tflink | we still need to schedule downtime for the AutoQA system and figure out when we're going to push out to production | 16:38 |
kparal | this week probably | 16:38 |
tflink | almost all of the test client HW is still running F14, so we have some upgrades to do | 16:39 |
adamw | question: is there a plan/schedule to get the results mails back up? | 16:39 |
adamw | or are we just waiting for resultsdb now? | 16:39 |
kparal | great question | 16:39 |
tflink | the conversation hasn't come up yet | 16:39 |
tflink | not in detail, anyways | 16:39 |
kparal | I think I proposed some solutions in that thread | 16:39 |
kparal | I'll try to revive that conversation | 16:40 |
tflink | have there been requests for the emails to come back? | 16:40 |
adamw | i haven't had any, i just was reminded when i was catching up on the meeting summaries last week | 16:40 |
* j_dulaney got the impression from Infranstructure that they don't want to serve the huge number of emails, for sure | 16:40 | |
adamw | j_dulaney: that's the reason it was shut down, yes | 16:42 |
adamw | j_dulaney: so we need some kind of plan to reduce the volume to get them back up again | 16:42 |
tflink | assuming we want to spam a list with all results, anyways | 16:42 |
tflink | but that conversation would best be saved for the lists | 16:42 |
* j_dulaney is leaning for resultsdb | 16:42 | |
adamw | okay | 16:42 |
j_dulaney | Indeed | 16:42 |
adamw | yeah, i just wanted to highlight it as an 'unresolved issue' | 16:43 |
adamw | #info autoqa 0.7.0 deployment still in planning | 16:43 |
adamw | #info autoqa test client hardware is still running F14, so needs to be upgraded | 16:43 |
adamw | anything there you need help with or is it all under control? | 16:44 |
tflink | I think its all under control | 16:44 |
tflink | we just need to hammer out a time for all the upgrades once we're satisfied with the code | 16:45 |
adamw | okay, great | 16:45 |
adamw | any other news? | 16:45 |
tflink | nothing I can think of for autoqa | 16:45 |
j_dulaney | Nothing here, either | 16:46 |
adamw | okey dokey | 16:46 |
adamw | thanks | 16:46 |
adamw | #topic open floor | 16:46 |
adamw | so, anything I missed? anyone have great ideas to forward the noble Project Colada goal? | 16:46 |
kparal | I want to have a quick chat about current QA priorities | 16:47 |
adamw | #topic open floor - current QA priorities | 16:47 |
adamw | go for it! | 16:47 |
kparal | so basically, I spent the last week reporting tuns of bugs for F16, tflink worked on autoqa and adamw posted a few internal calls for volunteers in different areas | 16:47 |
kparal | so, do we have any priorities regarding all these areas? | 16:47 |
kparal | just curious | 16:48 |
kparal | like do we want to spend much time on improving wiki test cases first, or is autoqa hacking more important now? | 16:48 |
* j_dulaney is wanting to hop back on AutoQA | 16:49 | |
j_dulaney | I've also kind of been hijacked into doing sysv to systemd init conversions | 16:49 |
adamw | for the public record, i was looking for volunteers for the Test Day thing which is now covered, updating/revising the validation test plans, and checking the F17 feature list for critical things that will need test plans | 16:49 |
adamw | kparal: so the wishy-washy answer is 'they're all important' :) | 16:50 |
tflink | adamw: thanks, that helps a lot | 16:50 |
tflink | :-D | 16:50 |
kparal | :D | 16:50 |
adamw | kparal: autoqa is a kind of ongoing priority which is never an emergency | 16:50 |
adamw | the challenge there is to try and avoid always pulling people off autoqa to firefight whatever the current emergency is | 16:50 |
kparal | I can help with those validation test plans, but I simply don't know whether I should rather work on autoqa or not | 16:51 |
adamw | i think you should probably prioritize autoqa | 16:51 |
* j_dulaney can do test plans | 16:51 | |
adamw | so the thing there is that autoqa requires more advanced knowledge/skills than just about any other area | 16:51 |
adamw | so the people who have the knowledge/skills to work on autoqa should probably focus on it, because otherwise it just won't get done | 16:52 |
adamw | we should be able to cover all the other tasks between rh staff and community, i think | 16:52 |
kparal | ok, that helps me with my bad conscience that I haven't responded to your call yet | 16:52 |
adamw | j_dulaney: thanks a lot, but if possible i'd like to try and get someone else on it, just to spread the load a little - it's unfair to you to try and carry two major areas | 16:53 |
j_dulaney | I'm about to have A LOT of free time | 16:53 |
j_dulaney | The next two weeks are going to suck, then I'll have a little over a month of free time | 16:54 |
kparal | so from what I got - autoqa is a high priority, no slacking elsewhere, right? | 16:54 |
adamw | kparal: yeah. if we really can't cover everything else we might need to ask you to do some non-autoqa stuff, but it'd be ideal if we could cover things without that. | 16:55 |
kparal | ok | 16:55 |
adamw | j_dulaney: great - if it turns out no-one else steps up to do that then we'll impose it on you :) | 16:56 |
j_dulaney | Indeed | 16:56 |
adamw | so, this topic also ties up with the retrospective somewhat | 16:56 |
j_dulaney | Except that I'm fired (: | 16:56 |
kparal | j_dulaney: more free time to work! | 16:57 |
adamw | we will likely have tickets for all the outstanding tasks once i'm done with the retrospective and we can try and make sure they're all prioritized and assigned at that point | 16:57 |
adamw | kparal: exACTly! | 16:57 |
adamw | #info all outstanding tasks should have trac tickets by the end of the week, which will help with assignation / prioritization | 16:59 |
adamw | does that cover it, kparal? | 16:59 |
* nirik has one quick item for open floor. | 16:59 | |
kparal | it does for me | 17:00 |
adamw | nirik: okay, do we have time though? | 17:00 |
adamw | is someone else tapping feet for the room? | 17:00 |
tflink | IIRC, the next meeting shifted an hour | 17:00 |
nirik | I just wanted to mention: http://lists.fedoraproject.org/pipermail/infrastructure/2011-November/011151.html (I will probibly be announcing it more widely soon). | 17:00 |
nirik | adamw: fesco moved an hour I think... | 17:01 |
adamw | okay | 17:01 |
nirik | so, if anyone wants to test new trac/scms for fedorahosted, please do. | 17:02 |
nirik | :) | 17:02 |
adamw | #info infrastructure team is calling for testing of a rhel6-based fedorahosted.org , see nirik's link for more details | 17:02 |
adamw | alrighty! | 17:02 |
adamw | #topic open floor | 17:02 |
adamw | anything more? | 17:02 |
* j_dulaney has nothing | 17:03 | |
adamw | alrighty, setting fuse for 1 minute then | 17:03 |
adamw | thanks folks! | 17:05 |
adamw | #endmeeting | 17:05 |
Generated by irclog2html.py 2.8 by Marius Gedminas - find it at mg.pov.lt!