From Fedora Project Wiki

< QA‎ | Meetings

(Initial agenda)
 
(Updated minutes)
 
Line 2: Line 2:


People present (lines said)
People present (lines said)
# jlaska (67)
# adamw (16)
# mkrizek (6)


Unable to attend:
Unable to attend:
# [[User:Rhe|Rhe]]
# [[User:Rhe|Rhe]]
# [[User:Newgle1|Newgle1]]
# [[User:Newgle1|Newgle1]]
# [[User:wwoods|wwoods]]
# [[User:kparal|kparal]]
# [[User:jskladan|jskladan]]


= Agenda =
= Agenda =
* [http://lists.fedoraproject.org/pipermail/test/2010-November/095431.html Proposed meeting agenda]
* [http://lists.fedoraproject.org/pipermail/test/2010-November/095431.html Proposed meeting agenda]
* [FIXME MeetBot summary]
* [http://meetbot.fedoraproject.org/fedora-meeting/2010-11-08/fedora-qa.2010-11-08-16.00.html MeetBot summary]


== Previous meeting follow-up ==
== Previous meeting follow-up ==
Line 29: Line 35:


= Open discussion - <Your topic here> =
= Open discussion - <Your topic here> =
== AutoQA ticket#205 ==
[[User:mkrizek|mkrizek]] mentioned he has a working script to submit bodhi update feedback and is looking for a sample test to integrate the support with.  Between <code>depcheck</code> and <code>upgradepath</code>, it was recommended to use <code>upgradepath</path> since <code>depcheck</code> is still in a private branch and it isn't clear whether it's ready to be integrated yet.


= Action items =
= Action items =


= IRC Transcript =
= IRC Transcript =
{|
|- id="t16:00:23"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #startmeeting Fedora QA Meeting
|| [[#t16:00:23|16:00]]
|- id="t16:00:23"
! style="background-color: #42427e" | zodbot
| style="color: #42427e" | Meeting started Mon Nov  8 16:00:23 2010 UTC.  The chair is jlaska. Information about MeetBot at http://wiki.debian.org/MeetBot.
|| [[#t16:00:23|16:00]]
|- id="t16:00:23"
! style="background-color: #42427e" | zodbot
| style="color: #42427e" | Useful Commands: #action #agreed #halp #info #idea #link #topic.
|| [[#t16:00:23|16:00]]
|- id="t16:00:26"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #meetingname fedora-qa
|| [[#t16:00:26|16:00]]
|- id="t16:00:26"
! style="background-color: #42427e" | zodbot
| style="color: #42427e" | The meeting name has been set to 'fedora-qa'
|| [[#t16:00:26|16:00]]
|- id="t16:00:37"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #topic Gathering ...
|| [[#t16:00:37|16:00]]
|- id="t16:00:45"
! style="background-color: #818144" | adamw
| style="color: #818144" | o to the y
|| [[#t16:00:45|16:00]]
|- id="t16:00:54"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | adamw: welcome!
|| [[#t16:00:54|16:00]]
|- id="t16:01:03"
| colspan="2" | * mkrizek is here
|| [[#t16:01:03|16:01]]
|- id="t16:01:07"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | I think we'll be without jskladan and kparal today
|| [[#t16:01:07|16:01]]
|- id="t16:01:10"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | Hi mkrizek
|| [[#t16:01:10|16:01]]
|- id="t16:01:28"
! style="background-color: #854685" | mkrizek
| style="color: #854685" | hi all
|| [[#t16:01:28|16:01]]
|- id="t16:01:29"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | wwoods will be a bit delayed as he needs to see a man about a horse
|| [[#t16:01:29|16:01]]
|- id="t16:01:58"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | anyone else lurking in the shadows?
|| [[#t16:01:58|16:01]]
|- id="t16:02:21"
| colspan="2" | * adamw sprays shadows with rifle
|| [[#t16:02:21|16:02]]
|- id="t16:02:23"
! style="background-color: #818144" | adamw
| style="color: #818144" | not any more, sir!
|| [[#t16:02:23|16:02]]
|- id="t16:02:37"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | wait, no we needed ... oh
|| [[#t16:02:37|16:02]]
|- id="t16:02:37"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | :)
|| [[#t16:02:37|16:02]]
|- id="t16:02:48"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | I'll wait another minute, and we'll get moving
|| [[#t16:02:48|16:02]]
|- id="t16:03:12"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #info Proposed meeting agenda - http://lists.fedoraproject.org/pipermail/test/2010-November/095431.html
|| [[#t16:03:12|16:03]]
|- id="t16:03:28"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | mkrizek: are you in a lecture at the moment?
|| [[#t16:03:28|16:03]]
|- id="t16:03:39"
! style="background-color: #854685" | mkrizek
| style="color: #854685" | jlaska: not today
|| [[#t16:03:39|16:03]]
|- id="t16:03:59"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | okay ... diving into the agenda
|| [[#t16:03:59|16:03]]
|- id="t16:04:12"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | this will be light today, just review and recap on F-14 still
|| [[#t16:04:12|16:04]]
|- id="t16:04:15"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #topic Common_F14_Bugs
|| [[#t16:04:15|16:04]]
|- id="t16:04:42"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | As I'm sure everyone knows, there is a wiki page (and process) used to record common issues users may hit
|| [[#t16:04:42|16:04]]
|- id="t16:04:45"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #link http://fedoraproject.org/wiki/Common_F14_bugs
|| [[#t16:04:45|16:04]]
|- id="t16:05:15"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | This #topic is 1) a quick reminder that the page exists, and instructions for adding your own entries are at the topic of the page
|| [[#t16:05:15|16:05]]
|- id="t16:05:37"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | and 2) we are just about 1-week out from F-14 general availability
|| [[#t16:05:37|16:05]]
|- id="t16:05:52"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | there is still active discussion of changes and issues on the list (and I suspect forums too)
|| [[#t16:05:52|16:05]]
|- id="t16:06:01"
! style="background-color: #818144" | adamw
| style="color: #818144" | erm
|| [[#t16:06:01|16:06]]
|- id="t16:06:06"
| colspan="2" | * adamw hands jlaska the time machine
|| [[#t16:06:06|16:06]]
|- id="t16:06:38"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | adamw: sorry, I meant 1-week s/out/past/
|| [[#t16:06:38|16:06]]
|- id="t16:06:41"
! style="background-color: #818144" | adamw
| style="color: #818144" | =)
|| [[#t16:06:41|16:06]]
|- id="t16:07:07"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | only thing I wanted to discuss here is whether we need to get folks on particular issues
|| [[#t16:07:07|16:07]]
|- id="t16:07:22"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | are there any developing issues/discussion that need further investigation as possible common bug entries?
|| [[#t16:07:22|16:07]]
|- id="t16:07:31"
! style="background-color: #818144" | adamw
| style="color: #818144" | nothing i'm aware of
|| [[#t16:07:31|16:07]]
|- id="t16:07:46"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | I'm tracking a few BIOS RAID bugs still ... but those continue to mature ... no resolution yet that I'm aware of
|| [[#t16:07:46|16:07]]
|- id="t16:08:23"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | adamw: any trends or concerns pop up from the forums?
|| [[#t16:08:23|16:08]]
|- id="t16:08:49"
! style="background-color: #818144" | adamw
| style="color: #818144" | nope, just the usual mix of mini-buglets
|| [[#t16:08:49|16:08]]
|- id="t16:08:57"
! style="background-color: #818144" | adamw
| style="color: #818144" | and people trying to get nvidia working
|| [[#t16:08:57|16:08]]
|- id="t16:09:05"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | anything different there wrt nvidia?
|| [[#t16:09:05|16:09]]
|- id="t16:09:12"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | blacklisting nouveau etc... ?
|| [[#t16:09:12|16:09]]
|- id="t16:09:49"
| colspan="2" | * jlaska hasn't had reason to change to proprietary NVidia drivers ... happy w/ nouveau
|| [[#t16:09:49|16:09]]
|- id="t16:10:11"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | alrighty ... so that's enough on this topic
|| [[#t16:10:11|16:10]]
|- id="t16:10:19"
! style="background-color: #818144" | adamw
| style="color: #818144" | yeah there's a bug in pyxf86config
|| [[#t16:10:19|16:10]]
|- id="t16:10:26"
! style="background-color: #818144" | adamw
| style="color: #818144" | which throws off all the *-config-display tools
|| [[#t16:10:26|16:10]]
|- id="t16:10:38"
! style="background-color: #818144" | adamw
| style="color: #818144" | so the typical install method for nvidia, fglrx and psb doesn't work
|| [[#t16:10:38|16:10]]
|- id="t16:10:45"
! style="background-color: #818144" | adamw
| style="color: #818144" | we (with rpmfusion hat on) should do something about that
|| [[#t16:10:45|16:10]]
|- id="t16:11:38"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | Is this intended to resolve that issue? http://koji.fedoraproject.org/koji/buildinfo?buildID=203948
|| [[#t16:11:38|16:11]]
|- id="t16:11:48"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | * Sun Nov 07 2010 Lubomir Rintel &lt;lkundrak@v3.sk&gt; - 0.3.37-10
|| [[#t16:11:48|16:11]]
|- id="t16:11:48"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | - Unbreak it for new XOrg configuration parser
|| [[#t16:11:48|16:11]]
|- id="t16:12:53"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | anyway, we can talk about that further in #fedora-qa ... don't think that's needed for this meeting (sorry)
|| [[#t16:12:53|16:12]]
|- id="t16:12:58"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #topic F-14 QA Retrospective -- last call
|| [[#t16:12:58|16:12]]
|- id="t16:13:04"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #link http://fedoraproject.org/wiki/Fedora_14_QA_Retrospective
|| [[#t16:13:04|16:13]]
|- id="t16:13:17"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | Another reminder topic ... we've got some really good content on the page so far
|| [[#t16:13:17|16:13]]
|- id="t16:13:31"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | As always though, the more the better
|| [[#t16:13:31|16:13]]
|- id="t16:13:50"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | even if you see something already on the page, it helps me to see when multiple people report the same (or similar) issues
|| [[#t16:13:50|16:13]]
|- id="t16:14:22"
! style="background-color: #818144" | adamw
| style="color: #818144" | jlaska: ooh! possibly.
|| [[#t16:14:22|16:14]]
|- id="t16:14:43"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | In the coming weeks, I plan to organize the content into distinct groups, and then list recommendations based on the issues identified or suggestions contributed
|| [[#t16:14:43|16:14]]
|- id="t16:15:14"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #info Last call for contributions ... add your feedback on what was good/bad/ugly about Fedora 14 Testing
|| [[#t16:15:14|16:15]]
|- id="t16:15:27"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | with regards to the process we followed last time ....
|| [[#t16:15:27|16:15]]
|- id="t16:15:45"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | The format worked for me ... it seemed to lend well to filing tickets so anyone could contribute
|| [[#t16:15:45|16:15]]
|- id="t16:16:03"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | For an example of what I'm talking about ... see http://fedoraproject.org/wiki/Fedora_13_QA_Retrospective#Recommendations
|| [[#t16:16:03|16:16]]
|- id="t16:16:18"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | I'll likely follow that same procedure
|| [[#t16:16:18|16:16]]
|- id="t16:16:35"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | However, I'm open to thoughts/suggestions on how we might better collaborate on the content as a group
|| [[#t16:16:35|16:16]]
|- id="t16:17:37"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | Certainly not something I expect to tackle in todays meeting ... but I am very interested in any ideas on how to collaboratively process the recommendations
|| [[#t16:17:37|16:17]]
|- id="t16:17:43"
! style="background-color: #818144" | adamw
| style="color: #818144" | i like the trac process, t's clear
|| [[#t16:17:43|16:17]]
|- id="t16:18:03"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | yeah that worked well I think ... maybe I need to be more active with directing folks to that list
|| [[#t16:18:03|16:18]]
|- id="t16:18:52"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #info jlaska seeking ideas for improving F-15 QA recommendations process/collaboration
|| [[#t16:18:52|16:18]]
|- id="t16:19:23"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | alright ... last planned topic for today ...
|| [[#t16:19:23|16:19]]
|- id="t16:19:31"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #topic F-15 QA schedule drafted
|| [[#t16:19:31|16:19]]
|- id="t16:19:48"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | poelcat provided a link to the draft F-15 QA schedule
|| [[#t16:19:48|16:19]]
|- id="t16:19:50"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #link http://poelstra.fedorapeople.org/schedules/f-15/f-15-quality-tasks.html
|| [[#t16:19:50|16:19]]
|- id="t16:20:33"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | poelcat and I had a brief discussion about some of the changes to the schedule.  A summary of that talk is available at https://fedorahosted.org/fedora-qa/ticket/147#comment:2
|| [[#t16:20:33|16:20]]
|- id="t16:20:53"
! style="background-color: #818144" | adamw
| style="color: #818144" | looks okay
|| [[#t16:20:53|16:20]]
|- id="t16:21:11"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | I plan to re-review the schedule in the context of the F-14 QA recommendations (once complete)
|| [[#t16:21:11|16:21]]
|- id="t16:21:20"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | but I'm pretty happy with the content
|| [[#t16:21:20|16:21]]
|- id="t16:21:32"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | adamw: excellent
|| [[#t16:21:32|16:21]]
|- id="t16:21:55"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | alright, it's open mic time
|| [[#t16:21:55|16:21]]
|- id="t16:21:58"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #topic Open discussion - &lt;Your topic here&gt;
|| [[#t16:21:58|16:21]]
|- id="t16:22:19"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | mkrizek: is there anything you'd like to call here out with regards to autoqa?
|| [[#t16:22:19|16:22]]
|- id="t16:24:12"
! style="background-color: #854685" | mkrizek
| style="color: #854685" | jlaska: not at the moment, I need to run the #205 with upgradepath/depcheck first before making any conclusions about the #205
|| [[#t16:24:12|16:24]]
|- id="t16:24:50"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | mkrizek: anything you need help with with regards to running those specific tests?
|| [[#t16:24:50|16:24]]
|- id="t16:25:52"
! style="background-color: #854685" | mkrizek
| style="color: #854685" | jlaska: well, one question, is it possible to run depcheck yet?
|| [[#t16:25:52|16:25]]
|- id="t16:26:19"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | mkrizek: I'm sure it's possible, but I think that the code is still in wwoods private branch.  So it's likely not intended for general consumption yet
|| [[#t16:26:19|16:26]]
|- id="t16:26:48"
! style="background-color: #854685" | mkrizek
| style="color: #854685" | ok, I will try the upgradepath first then
|| [[#t16:26:48|16:26]]
|- id="t16:27:18"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | mkrizek: yeah, that's probably the best place to experiment first ... I assume that depcheck is close to final, but hard to say until it's moved into 'master'
|| [[#t16:27:18|16:27]]
|- id="t16:27:29"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | alright ... if no other comments in 1 minute, let's #endmeeting
|| [[#t16:27:29|16:27]]
|- id="t16:28:45"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | okay gang ... let's get back to your post-F14 wrap-up activities and pre-F15 planning
|| [[#t16:28:45|16:28]]
|- id="t16:28:56"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | thanks all
|| [[#t16:28:56|16:28]]
|- id="t16:28:59"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #endmeeting
|| [[#t16:28:59|16:28]]
|}
Generated by irclog2html.py 2.7 by [mailto:marius@pov.lt Marius Gedminas] - find it at [http://mg.pov.lt/irclog2html mg.pov.lt]!

Latest revision as of 16:57, 8 November 2010

Attendees

People present (lines said)

  1. jlaska (67)
  2. adamw (16)
  3. mkrizek (6)

Unable to attend:

  1. Rhe
  2. Newgle1
  3. wwoods
  4. kparal
  5. jskladan

Agenda

Previous meeting follow-up

  • None

Common_F14_Bugs

Quick check-in on Common_F14_bugs and discussion around incoming issues on test@lists.fedoraproject.org

F-14 QA Retrospective -- last call

Last call for feedback on Fedora_14_QA_Retrospective. Really good list of improvement areas generated so far, but more feedback never hurts.

Suggestions/ideas on organizing feedback into recommendations?

F-15 QA schedule drafted

Feedback welcome ... http://poelstra.fedorapeople.org/schedules/f-15/f-15-quality-tasks.html

Open discussion - <Your topic here>

AutoQA ticket#205

mkrizek mentioned he has a working script to submit bodhi update feedback and is looking for a sample test to integrate the support with. Between depcheck and upgradepath, it was recommended to use upgradepath</path> since depcheck is still in a private branch and it isn't clear whether it's ready to be integrated yet.

Action items

IRC Transcript

jlaska #startmeeting Fedora QA Meeting 16:00
zodbot Meeting started Mon Nov 8 16:00:23 2010 UTC. The chair is jlaska. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00
zodbot Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:00
jlaska #meetingname fedora-qa 16:00
zodbot The meeting name has been set to 'fedora-qa' 16:00
jlaska #topic Gathering ... 16:00
adamw o to the y 16:00
jlaska adamw: welcome! 16:00
* mkrizek is here 16:01
jlaska I think we'll be without jskladan and kparal today 16:01
jlaska Hi mkrizek 16:01
mkrizek hi all 16:01
jlaska wwoods will be a bit delayed as he needs to see a man about a horse 16:01
jlaska anyone else lurking in the shadows? 16:01
* adamw sprays shadows with rifle 16:02
adamw not any more, sir! 16:02
jlaska wait, no we needed ... oh 16:02
jlaska :) 16:02
jlaska I'll wait another minute, and we'll get moving 16:02
jlaska #info Proposed meeting agenda - http://lists.fedoraproject.org/pipermail/test/2010-November/095431.html 16:03
jlaska mkrizek: are you in a lecture at the moment? 16:03
mkrizek jlaska: not today 16:03
jlaska okay ... diving into the agenda 16:03
jlaska this will be light today, just review and recap on F-14 still 16:04
jlaska #topic Common_F14_Bugs 16:04
jlaska As I'm sure everyone knows, there is a wiki page (and process) used to record common issues users may hit 16:04
jlaska #link http://fedoraproject.org/wiki/Common_F14_bugs 16:04
jlaska This #topic is 1) a quick reminder that the page exists, and instructions for adding your own entries are at the topic of the page 16:05
jlaska and 2) we are just about 1-week out from F-14 general availability 16:05
jlaska there is still active discussion of changes and issues on the list (and I suspect forums too) 16:05
adamw erm 16:06
* adamw hands jlaska the time machine 16:06
jlaska adamw: sorry, I meant 1-week s/out/past/ 16:06
adamw =) 16:06
jlaska only thing I wanted to discuss here is whether we need to get folks on particular issues 16:07
jlaska are there any developing issues/discussion that need further investigation as possible common bug entries? 16:07
adamw nothing i'm aware of 16:07
jlaska I'm tracking a few BIOS RAID bugs still ... but those continue to mature ... no resolution yet that I'm aware of 16:07
jlaska adamw: any trends or concerns pop up from the forums? 16:08
adamw nope, just the usual mix of mini-buglets 16:08
adamw and people trying to get nvidia working 16:08
jlaska anything different there wrt nvidia? 16:09
jlaska blacklisting nouveau etc... ? 16:09
* jlaska hasn't had reason to change to proprietary NVidia drivers ... happy w/ nouveau 16:09
jlaska alrighty ... so that's enough on this topic 16:10
adamw yeah there's a bug in pyxf86config 16:10
adamw which throws off all the *-config-display tools 16:10
adamw so the typical install method for nvidia, fglrx and psb doesn't work 16:10
adamw we (with rpmfusion hat on) should do something about that 16:10
jlaska Is this intended to resolve that issue? http://koji.fedoraproject.org/koji/buildinfo?buildID=203948 16:11
jlaska * Sun Nov 07 2010 Lubomir Rintel <lkundrak@v3.sk> - 0.3.37-10 16:11
jlaska - Unbreak it for new XOrg configuration parser 16:11
jlaska anyway, we can talk about that further in #fedora-qa ... don't think that's needed for this meeting (sorry) 16:12
jlaska #topic F-14 QA Retrospective -- last call 16:12
jlaska #link http://fedoraproject.org/wiki/Fedora_14_QA_Retrospective 16:13
jlaska Another reminder topic ... we've got some really good content on the page so far 16:13
jlaska As always though, the more the better 16:13
jlaska even if you see something already on the page, it helps me to see when multiple people report the same (or similar) issues 16:13
adamw jlaska: ooh! possibly. 16:14
jlaska In the coming weeks, I plan to organize the content into distinct groups, and then list recommendations based on the issues identified or suggestions contributed 16:14
jlaska #info Last call for contributions ... add your feedback on what was good/bad/ugly about Fedora 14 Testing 16:15
jlaska with regards to the process we followed last time .... 16:15
jlaska The format worked for me ... it seemed to lend well to filing tickets so anyone could contribute 16:15
jlaska For an example of what I'm talking about ... see http://fedoraproject.org/wiki/Fedora_13_QA_Retrospective#Recommendations 16:16
jlaska I'll likely follow that same procedure 16:16
jlaska However, I'm open to thoughts/suggestions on how we might better collaborate on the content as a group 16:16
jlaska Certainly not something I expect to tackle in todays meeting ... but I am very interested in any ideas on how to collaboratively process the recommendations 16:17
adamw i like the trac process, t's clear 16:17
jlaska yeah that worked well I think ... maybe I need to be more active with directing folks to that list 16:18
jlaska #info jlaska seeking ideas for improving F-15 QA recommendations process/collaboration 16:18
jlaska alright ... last planned topic for today ... 16:19
jlaska #topic F-15 QA schedule drafted 16:19
jlaska poelcat provided a link to the draft F-15 QA schedule 16:19
jlaska #link http://poelstra.fedorapeople.org/schedules/f-15/f-15-quality-tasks.html 16:19
jlaska poelcat and I had a brief discussion about some of the changes to the schedule. A summary of that talk is available at https://fedorahosted.org/fedora-qa/ticket/147#comment:2 16:20
adamw looks okay 16:20
jlaska I plan to re-review the schedule in the context of the F-14 QA recommendations (once complete) 16:21
jlaska but I'm pretty happy with the content 16:21
jlaska adamw: excellent 16:21
jlaska alright, it's open mic time 16:21
jlaska #topic Open discussion - <Your topic here> 16:21
jlaska mkrizek: is there anything you'd like to call here out with regards to autoqa? 16:22
mkrizek jlaska: not at the moment, I need to run the #205 with upgradepath/depcheck first before making any conclusions about the #205 16:24
jlaska mkrizek: anything you need help with with regards to running those specific tests? 16:24
mkrizek jlaska: well, one question, is it possible to run depcheck yet? 16:25
jlaska mkrizek: I'm sure it's possible, but I think that the code is still in wwoods private branch. So it's likely not intended for general consumption yet 16:26
mkrizek ok, I will try the upgradepath first then 16:26
jlaska mkrizek: yeah, that's probably the best place to experiment first ... I assume that depcheck is close to final, but hard to say until it's moved into 'master' 16:27
jlaska alright ... if no other comments in 1 minute, let's #endmeeting 16:27
jlaska okay gang ... let's get back to your post-F14 wrap-up activities and pre-F15 planning 16:28
jlaska thanks all 16:28
jlaska #endmeeting 16:28

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