From Fedora Project Wiki

< QA‎ | Meetings

m (Initial draft)
 
m (internal link cleaning)
 
(3 intermediate revisions by one other user not shown)
Line 2: Line 2:


People present (lines said):
People present (lines said):
# jlaska (137)
# rbergeron (45)
# adamw (40)
# j_dulaney (40)
# vhumpa (35)
# kparal (15)
# Viking-Ice (15)
# tgr__ (14)
# tflink (6)
# athmane (4)
# jsmith (2)
# Southern_Gentlem (1)


Unable to attend:
Unable to attend:
Line 9: Line 21:


= Agenda =
= Agenda =
* [FIXME Proposed meeting agenda]
* [http://lists.fedoraproject.org/pipermail/test/2011-June/100743.html Proposed meeting agenda]
* [FIXME MeetBot summary]
* [http://meetbot.fedoraproject.org/fedora-meeting/2011-06-06/fedora-qa.2011-06-06-15.00.html MeetBot summary]


== Previous meeting follow-up ==
== Release criteria updates ==
* vhumpa started a discussion on test + desktop lists last week - http://lists.fedoraproject.org/pipermail/desktop/2011-June/007274.html
* Next steps ... decide whether to adjust upstream, or to resolve using Fedora .desktop files
* ACTION: vhumpa/adamw - reach out to GNOME for opinions on presenting duplicate application names in overview


== Release criteria updates ==
* Status on desktop proposal for too-similar menu names


== AutoQA updates ==
== AutoQA updates ==
* Kparal reported that the announcement of 'pretty patch' that was just posted into autoqa-devel - https://fedorahosted.org/pipermail/autoqa-devel/2011-June/002344.html
* Tflink is finalizing test result email reduction patchset - expecting patch out for review later today
* Jlaska noted that packaging/testing for soon-to-be-released autotest-0.13.0 is almost complete. Packages available in autoqa ''fedora-15-testing'' repo.
# Patch review and testing of autoqa-0.5.0 expected this week


== IPv6 Test Day ==
== IPv6 Test Day ==
* wiki page: https://fedoraproject.org/wiki/QA/Test_Day:2011-06-08_IPv6
* World IPv6 Day is happening on June 8, along with a Fedora IPv6 test day - [[QA/Test_Day:2011-06-08_IPv6]]
* World IPv6 Day is happening on june 8 so we have decided to have a fedora IPv6 test day as well
* Red Hat blog post expected tomorrow that will link to test day wiki
* Tasks:
* Some test cases available on the wiki already, including http://fedoraproject.org/wiki/QA:Testcase_NetworkManager_ipv6, http://fedoraproject.org/wiki/QA:Testcase_NFS_ipv6
*# Announce - blog, list, irc etc...
* More test needed for any cli ipv6 tools, printing and <other>
* ACTION: adamw - send test-announce@ for IPv6 test day (jlaska, 15:33:42)
* ACTION: jlaska - test day wiki cleanup (remove boilerplate) (jlaska, 15:33:53)
* ACTION: tgr__ - provide wiki instructions for native ipv6 connectivity (jlaska, 15:34:10)
 


== Open Discussion - <your topic here> ==
== Open Discussion - <your topic here> ==
=== Fedora-qa F15 TRAC tickets ===
* Jlaska cleaning up the Fedora 15 fedora-qa TRAC milestone in preparation for Fedora 16 tickets
* Please cleanup any tickets currently assigned to you - https://fedorahosted.org/fedora-qa/query?status=new&status=assigned&status=reopened&milestone=Fedora+15
===  F16 QA Schedule ===
* [[Releases/16/Schedule]]
* rbergeron noted that the Fedora 16 QA schedule is available for review.  Patches/comments/questions encouraged
* Times/milestones should not have changed, comparison between f15 and f16 available at http://rbergero.fedorapeople.org/schedules/f-15/f-15-quality-tasks.html vs. http://rbergero.fedorapeople.org/schedules/f-16/f-16-quality-tasks.html
=== Fixing features ===
* Discussion is underway on how to identify and resolve specific issues with the feature proces
* If you have any thoughts on the good, the bad, the ugly in the feature process, feel free to add your commentary to wiki page - [[Fixing_features]]
=== Fedora 16 Cloud Test Days ===
* http://lists.fedoraproject.org/pipermail/cloud/2011-June/000632.html
* David Nalley started discussion about possible cloud test day topics for F16.  Planning is happening much earlier this time, if interested, please join and help move the discussion along.
= Action Items =
# vhumpa/adamw - reach out to GNOME for opinions on presenting duplicate application names in overview
# adamw - send test-announce@ for IPv6 test day
# jlaska - test day wiki cleanup (remove boilerplate)
# tgr - provide wiki instructions for native ipv6 connectivity


= IRC Log =
= IRC Log =
{|
|- id="t15:00:13"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #startmeeting Fedora QA Meeting
|| [[#t15:00:13|15:00]]
|- id="t15:00:13"
! style="background-color: #42427e" | zodbot
| style="color: #42427e" | Meeting started Mon Jun  6 15:00:13 2011 UTC.  The chair is jlaska. Information about MeetBot at http://wiki.debian.org/MeetBot.
|| [[#t15:00:13|15:00]]
|- id="t15:00:13"
! style="background-color: #42427e" | zodbot
| style="color: #42427e" | Useful Commands: #action #agreed #halp #info #idea #link #topic.
|| [[#t15:00:13|15:00]]
|- id="t15:00:17"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #meetingname fedora-qa
|| [[#t15:00:17|15:00]]
|- id="t15:00:17"
! style="background-color: #42427e" | zodbot
| style="color: #42427e" | The meeting name has been set to 'fedora-qa'
|| [[#t15:00:17|15:00]]
|- id="t15:00:20"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #topic Roll Call
|| [[#t15:00:20|15:00]]
|- id="t15:00:37"
| colspan="2" | * Viking-Ice here..
|| [[#t15:00:37|15:00]]
|- id="t15:00:41"
! style="background-color: #818144" | adamw
| style="color: #818144" | yo
|| [[#t15:00:41|15:00]]
|- id="t15:00:41"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | tgr__: Hi there ... we're just doing roll call atm
|| [[#t15:00:41|15:00]]
|- id="t15:00:48"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | Viking-Ice: adamw: hey hey
|| [[#t15:00:48|15:00]]
|- id="t15:00:50"
| colspan="2" | * tflink is here
|| [[#t15:00:50|15:00]]
|- id="t15:01:00"
| colspan="2" | * athmane is there
|| [[#t15:01:00|15:01]]
|- id="t15:01:15"
! style="background-color: #854685" | tgr__
| style="color: #854685" | well, i'm here :)
|| [[#t15:01:15|15:01]]
|- id="t15:01:21"
| colspan="2" | * jlaska greets tflink &amp; athmane
|| [[#t15:01:21|15:01]]
|- id="t15:01:29"
| colspan="2" | * jsmith lurks
|| [[#t15:01:29|15:01]]
|- id="t15:01:50"
| colspan="2" | * j_dulaney waves
|| [[#t15:01:50|15:01]]
|- id="t15:01:52"
| colspan="2" | * kparal here
|| [[#t15:01:52|15:01]]
|- id="t15:01:58"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | hi j_dulaney &amp;&amp; kparal
|| [[#t15:01:58|15:01]]
|- id="t15:02:21"
| colspan="2" | * vhumpa says hi
|| [[#t15:02:21|15:02]]
|- id="t15:02:39"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | helloooo
|| [[#t15:02:39|15:02]]
|- id="t15:02:39"
| colspan="2" | * rbergeron takes a seat
|| [[#t15:02:39|15:02]]
|- id="t15:02:42"
! style="background-color: #488888" | j_dulaney
| style="color: #488888" | jlaska, vhumpa, kparal
|| [[#t15:02:42|15:02]]
|- id="t15:02:55"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | okay, let's get started
|| [[#t15:02:55|15:02]]
|- id="t15:03:08"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | we don't have a complicated/lengthy agenda today ... just checking in on a few recurring topics
|| [[#t15:03:08|15:03]]
|- id="t15:03:17"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | as always, feel free to raise topics during open-discussion
|| [[#t15:03:17|15:03]]
|- id="t15:03:37"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | and thanks to vhumpa j_dulaney and adamw for #chair'ing last week
|| [[#t15:03:37|15:03]]
|- id="t15:03:38"
! style="background-color: #488888" | j_dulaney
| style="color: #488888" | .bacon
|| [[#t15:03:38|15:03]]
|- id="t15:03:38"
! style="background-color: #42427e" | zodbot
| style="color: #42427e" | I love bacon, you love bacon, WE ALL LOVE BACON!
|| [[#t15:03:38|15:03]]
|- id="t15:03:50"
! style="background-color: #8c4a4a" | vhumpa
| style="color: #8c4a4a" | jlaska: was fun
|| [[#t15:03:50|15:03]]
|- id="t15:03:53"
! style="background-color: #488888" | j_dulaney
| style="color: #488888" | Indeed
|| [[#t15:03:53|15:03]]
|- id="t15:04:09"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | So, I'm skipping the 'previous meeting follow-up' topic today ... since that's really covered by the agenda
|| [[#t15:04:09|15:04]]
|- id="t15:04:23"
| colspan="2" | * jlaska queues adamw first ..
|| [[#t15:04:23|15:04]]
|- id="t15:04:27"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #topic Release Criteria Updates
|| [[#t15:04:27|15:04]]
|- id="t15:04:32"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | well, vhumpa too really
|| [[#t15:04:32|15:04]]
|- id="t15:04:51"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | What's the word on the "too-similar menu names" proposal that went out last week?
|| [[#t15:04:51|15:04]]
|- id="t15:05:16"
! style="background-color: #8c4a4a" | vhumpa
| style="color: #8c4a4a" | jlaska: I started a discussion on test + desktops mailing lists
|| [[#t15:05:16|15:05]]
|- id="t15:05:16"
| colspan="2" | * adamw defers to vhumpa
|| [[#t15:05:16|15:05]]
|- id="t15:05:37"
! style="background-color: #8c4a4a" | vhumpa
| style="color: #8c4a4a" | People are supportive of the idea that *something* needs to be done with the issue
|| [[#t15:05:37|15:05]]
|- id="t15:05:45"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #info vhumpa started a discussion on test + desktop lists last week
|| [[#t15:05:45|15:05]]
|- id="t15:06:39"
! style="background-color: #8c4a4a" | vhumpa
| style="color: #8c4a4a" | vhumpa: ideas spread from modifying the app launcher to make sure that they would differentiate the apps with same names properly - to just renaming some of the problematic apps
|| [[#t15:06:39|15:06]]
|- id="t15:07:09"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | I guess depending on the solution ... a different group of people would need to make the changes?
|| [[#t15:07:09|15:07]]
|- id="t15:07:21"
! style="background-color: #8c4a4a" | vhumpa
| style="color: #8c4a4a" | For example of this issue: You all know terminal/terminal etc.
|| [[#t15:07:21|15:07]]
|- id="t15:07:22"
! style="background-color: #488888" | j_dulaney
| style="color: #488888" | Indeed
|| [[#t15:07:22|15:07]]
|- id="t15:07:39"
! style="background-color: #8c4a4a" | vhumpa
| style="color: #8c4a4a" | jlaska: Yes, the first one, simply, is upstream
|| [[#t15:07:39|15:07]]
|- id="t15:07:53"
! style="background-color: #8c4a4a" | vhumpa
| style="color: #8c4a4a" | thus not something I think we can do very quickly
|| [[#t15:07:53|15:07]]
|- id="t15:08:24"
! style="background-color: #8c4a4a" | vhumpa
| style="color: #8c4a4a" | Should gnome-shell offer e.g. popups for the app icons, that would present one set of means how to deal with the issue
|| [[#t15:08:24|15:08]]
|- id="t15:08:35"
! style="background-color: #4b904b" | Viking-Ice
| style="color: #4b904b" | how does QA fit into this discussion as in is this not something all the *DE should take care of among themselves ?
|| [[#t15:08:35|15:08]]
|- id="t15:08:44"
! style="background-color: #8c4a4a" | vhumpa
| style="color: #8c4a4a" | But, I am not sure how reasonable it would be to push that through
|| [[#t15:08:44|15:08]]
|- id="t15:08:45"
! style="background-color: #818144" | adamw
| style="color: #818144" | right,viking
|| [[#t15:08:45|15:08]]
|- id="t15:08:59"
! style="background-color: #818144" | adamw
| style="color: #818144" | the fix isn't our problem exactly
|| [[#t15:08:59|15:08]]
|- id="t15:09:00"
! style="background-color: #4d4d93" | athmane
| style="color: #4d4d93" | Viking-Ice, +1
|| [[#t15:09:00|15:09]]
|- id="t15:09:01"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | Viking-Ice: yeah ... I'm just seeing this as  QA bringing this to appropriate desktop attn
|| [[#t15:09:01|15:09]]
|- id="t15:09:14"
! style="background-color: #8c4a4a" | vhumpa
| style="color: #8c4a4a" | That brings me to what FEdora can do...
|| [[#t15:09:14|15:09]]
|- id="t15:09:27"
! style="background-color: #818144" | adamw
| style="color: #818144" | what we're concerned with is whether this should be a release requirement
|| [[#t15:09:27|15:09]]
|- id="t15:09:40"
! style="background-color: #488888" | j_dulaney
| style="color: #488888" | Indeed
|| [[#t15:09:40|15:09]]
|- id="t15:09:57"
! style="background-color: #8c4a4a" | vhumpa
| style="color: #8c4a4a" | It's a problem of a few apps really... So what we can do is merely to rename some of them, in their desktop files
|| [[#t15:09:57|15:09]]
|- id="t15:09:57"
! style="background-color: #4b904b" | Viking-Ice
| style="color: #4b904b" | I'm not seeing this as an  release requirement
|| [[#t15:09:57|15:09]]
|- id="t15:10:03"
! style="background-color: #8c4a4a" | vhumpa
| style="color: #8c4a4a" | the QE connection:
|| [[#t15:10:03|15:10]]
|- id="t15:10:13"
! style="background-color: #8c4a4a" | vhumpa
| style="color: #8c4a4a" | enforce that it is done with a requirement
|| [[#t15:10:13|15:10]]
|- id="t15:10:41"
! style="background-color: #4d4d93" | athmane
| style="color: #4d4d93" | if we tests each desktop separately this issue will not raise, afaik
|| [[#t15:10:41|15:10]]
|- id="t15:10:58"
! style="background-color: #8c4a4a" | vhumpa
| style="color: #8c4a4a" | athmane: true
|| [[#t15:10:58|15:10]]
|- id="t15:11:05"
! style="background-color: #8c4a4a" | vhumpa
| style="color: #8c4a4a" | athmane: partially
|| [[#t15:11:05|15:11]]
|- id="t15:11:07"
! style="background-color: #488888" | j_dulaney
| style="color: #488888" | The biggest issue I see is apps within the same desktop
|| [[#t15:11:07|15:11]]
|- id="t15:11:16"
! style="background-color: #8c4a4a" | vhumpa
| style="color: #8c4a4a" | there are issues even withing single desktop
|| [[#t15:11:16|15:11]]
|- id="t15:11:17"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | what's the ideal outcome for this topic?  ... upstream acknowledgement of the issue?
|| [[#t15:11:17|15:11]]
|- id="t15:11:35"
! style="background-color: #8c4a4a" | vhumpa
| style="color: #8c4a4a" | I suppose so
|| [[#t15:11:35|15:11]]
|- id="t15:11:38"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | ... formalizing tests and applicable criteria?
|| [[#t15:11:38|15:11]]
|- id="t15:11:58"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | (depending on whether it's accepted or not)
|| [[#t15:11:58|15:11]]
|- id="t15:12:03"
! style="background-color: #8c4a4a" | vhumpa
| style="color: #8c4a4a" | Meaning.. upstream acknowledgment is a "pony" perhaps
|| [[#t15:12:03|15:12]]
|- id="t15:12:06"
! style="background-color: #818144" | adamw
| style="color: #818144" | we should probably add it to the desktop menus test case
|| [[#t15:12:06|15:12]]
|- id="t15:12:22"
! style="background-color: #488888" | j_dulaney
| style="color: #488888" | I'm thinking that a good outcome would simply be that what the user sees is different names for different apps
|| [[#t15:12:22|15:12]]
|- id="t15:12:33"
! style="background-color: #8c4a4a" | vhumpa
| style="color: #8c4a4a" | I agree with Adam on this one.
|| [[#t15:12:33|15:12]]
|- id="t15:12:36"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | I don't see any feedback from anyone upstream on this topic ... have they weighed in on this yet?
|| [[#t15:12:36|15:12]]
|- id="t15:12:52"
! style="background-color: #8c4a4a" | vhumpa
| style="color: #8c4a4a" | jlaska: nope
|| [[#t15:12:52|15:12]]
|- id="t15:13:04"
! style="background-color: #4d4d93" | athmane
| style="color: #4d4d93" | maybe we should fill bugs on upstream tracking app ?
|| [[#t15:13:04|15:13]]
|- id="t15:13:05"
! style="background-color: #488888" | j_dulaney
| style="color: #488888" | The actual names don't necesarily have to be different for the actual app, just the menu choices
|| [[#t15:13:05|15:13]]
|- id="t15:13:16"
! style="background-color: #4b904b" | Viking-Ice
| style="color: #4b904b" | are these apps that any of the *DE ship by default or is this something that is mixed apps between *DE ?
|| [[#t15:13:16|15:13]]
|- id="t15:13:36"
! style="background-color: #488888" | j_dulaney
| style="color: #488888" | Viking-Ice:  Default
|| [[#t15:13:36|15:13]]
|- id="t15:13:55"
! style="background-color: #488888" | j_dulaney
| style="color: #488888" | For instance, within just Gnome:  Softare Update and Software Updates
|| [[#t15:13:55|15:13]]
|- id="t15:14:08"
! style="background-color: #818144" | adamw
| style="color: #818144" | so we have a plan for testing
|| [[#t15:14:08|15:14]]
|- id="t15:14:11"
! style="background-color: #8c4a4a" | vhumpa
| style="color: #8c4a4a" | Some are issue in deafult, some become an issue when you have multiple environments installed
|| [[#t15:14:11|15:14]]
|- id="t15:14:13"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | What's the next step?  Should we focus on trying to get feedback/input from upstream on this topic?
|| [[#t15:14:13|15:14]]
|- id="t15:14:19"
! style="background-color: #4b904b" | Viking-Ice
| style="color: #4b904b" | anyway this sounds to me just something that the relevant *DE maintainers need to take care of not something related to QA per se
|| [[#t15:14:19|15:14]]
|- id="t15:14:31"
! style="background-color: #818144" | adamw
| style="color: #818144" | then the question is, should it be a release criterion, i.e., should we require same name situations to be resolved for release
|| [[#t15:14:31|15:14]]
|- id="t15:14:36"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | adamw: should we move forward with testing and criteria without feedback from GNOME?
|| [[#t15:14:36|15:14]]
|- id="t15:14:40"
! style="background-color: #488888" | j_dulaney
| style="color: #488888" | The QA angle would be enforcement
|| [[#t15:14:40|15:14]]
|- id="t15:14:44"
! style="background-color: #8c4a4a" | vhumpa
| style="color: #8c4a4a" | I would concentrate in choosing menu names around Fedora desktops to minimize this issue... Upstream should come later
|| [[#t15:14:44|15:14]]
|- id="t15:14:57"
! style="background-color: #488888" | j_dulaney
| style="color: #488888" | adamw:  I think so
|| [[#t15:14:57|15:14]]
|- id="t15:15:00"
! style="background-color: #818144" | adamw
| style="color: #818144" | jlaska: feedback would be good, i guess
|| [[#t15:15:00|15:15]]
|- id="t15:15:08"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | adamw: seems like it should be required to me
|| [[#t15:15:08|15:15]]
|- id="t15:15:16"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | how can we create criteria and tests without their input?
|| [[#t15:15:16|15:15]]
|- id="t15:15:24"
| colspan="2" | * jlaska might be missing something though
|| [[#t15:15:24|15:15]]
|- id="t15:15:57"
! style="background-color: #8c4a4a" | vhumpa
| style="color: #8c4a4a" | The problem lies in how Fedora names apps, which I am not sure how connected is to upstream really
|| [[#t15:15:57|15:15]]
|- id="t15:15:58"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | err ... I'd want to avoid creating tests and criteria that GNOME isn't interested in honoring/fixing etc...
|| [[#t15:15:58|15:15]]
|- id="t15:16:13"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | vhumpa: good point ... it really depends on the implementation
|| [[#t15:16:13|15:16]]
|- id="t15:16:16"
! style="background-color: #818144" | adamw
| style="color: #818144" | jlaska: well, addressing it upstream is only one approach
|| [[#t15:16:16|15:16]]
|- id="t15:16:30"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | yes, I see now, gotcha
|| [[#t15:16:30|15:16]]
|- id="t15:16:37"
! style="background-color: #818144" | adamw
| style="color: #818144" | i can see, for instance, that if upstream GNOME decide they don't care, we would decide Fedora still does care
|| [[#t15:16:37|15:16]]
|- id="t15:16:45"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | right, that makes sense
|| [[#t15:16:45|15:16]]
|- id="t15:16:50"
! style="background-color: #8c4a4a" | vhumpa
| style="color: #8c4a4a" | adamw: yes
|| [[#t15:16:50|15:16]]
|- id="t15:16:56"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | so when will we know which of those routes to take?
|| [[#t15:16:56|15:16]]
|- id="t15:16:57"
! style="background-color: #4b904b" | Viking-Ice
| style="color: #4b904b" | sounds like a ( test ) candidate for fit and finish
|| [[#t15:16:57|15:16]]
|- id="t15:16:59"
! style="background-color: #488888" | j_dulaney
| style="color: #488888" | +1
|| [[#t15:16:59|15:16]]
|- id="t15:17:46"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | I guess we can conclude that if we don't get GNOME feedback, then it's up to Fedora to decide?
|| [[#t15:17:46|15:17]]
|- id="t15:17:53"
! style="background-color: #8c4a4a" | vhumpa
| style="color: #8c4a4a" | So the question is 1) Do we ask upstream to help with this 2) We just rename a few menu items in Fedora
|| [[#t15:17:53|15:17]]
|- id="t15:18:04"
| colspan="2" | * j_dulaney goes with 2
|| [[#t15:18:04|15:18]]
|- id="t15:18:10"
! style="background-color: #8c4a4a" | vhumpa
| style="color: #8c4a4a" | +1
|| [[#t15:18:10|15:18]]
|- id="t15:18:14"
! style="background-color: #97974f" | Southern_Gentlem
| style="color: #97974f" | both
|| [[#t15:18:14|15:18]]
|- id="t15:18:15"
! style="background-color: #488888" | j_dulaney
| style="color: #488888" | Easiest solution
|| [[#t15:18:15|15:18]]
|- id="t15:18:17"
| colspan="2" | * jsmith goes with 1)
|| [[#t15:18:17|15:18]]
|- id="t15:18:19"
! style="background-color: #4b904b" | Viking-Ice
| style="color: #4b904b" | both
|| [[#t15:18:19|15:18]]
|- id="t15:18:20"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | we'll likely go with #2 ... but I'd like to give #1 another attempt
|| [[#t15:18:20|15:18]]
|- id="t15:18:21"
! style="background-color: #818144" | adamw
| style="color: #818144" | vhumpa: i think that's kind of up to the devs to decide really
|| [[#t15:18:21|15:18]]
|- id="t15:18:47"
! style="background-color: #818144" | adamw
| style="color: #818144" | i think we may be going round in circles at this point?
|| [[#t15:18:47|15:18]]
|- id="t15:18:54"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | yup ... let's wrap up on this topic
|| [[#t15:18:54|15:18]]
|- id="t15:18:54"
! style="background-color: #8c4a4a" | vhumpa
| style="color: #8c4a4a" | 1) definitely too - but facing reality that it would be a more long term solution but for later
|| [[#t15:18:54|15:18]]
|- id="t15:19:07"
! style="background-color: #8c4a4a" | vhumpa
| style="color: #8c4a4a" | True
|| [[#t15:19:07|15:19]]
|- id="t15:19:10"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | anyone want to approach GNOME with this topic this week?
|| [[#t15:19:10|15:19]]
|- id="t15:19:14"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | if not ... I'll take it
|| [[#t15:19:14|15:19]]
|- id="t15:19:38"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | or any other #action items ... feel free to grab
|| [[#t15:19:38|15:19]]
|- id="t15:19:45"
! style="background-color: #8c4a4a" | vhumpa
| style="color: #8c4a4a" | If I know how to approach them, I will
|| [[#t15:19:45|15:19]]
|- id="t15:20:17"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | vhumpa: okay, thank you
|| [[#t15:20:17|15:20]]
|- id="t15:20:29"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | anything else to cover on this before next week?
|| [[#t15:20:29|15:20]]
|- id="t15:20:34"
! style="background-color: #818144" | adamw
| style="color: #818144" | i'll sync up with you on that
|| [[#t15:20:34|15:20]]
|- id="t15:20:40"
! style="background-color: #4b904b" | Viking-Ice
| style="color: #4b904b" | is this only relevant to Gnome or is this problem present in all *DE we ship ?
|| [[#t15:20:40|15:20]]
|- id="t15:20:41"
! style="background-color: #8c4a4a" | vhumpa
| style="color: #8c4a4a" | Meaning: we'll be aproaching for modifing the launcher, right? You don't just mean renaming apps on Upstream side
|| [[#t15:20:41|15:20]]
|- id="t15:20:57"
! style="background-color: #8c4a4a" | vhumpa
| style="color: #8c4a4a" | Unsure on that
|| [[#t15:20:57|15:20]]
|- id="t15:21:01"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #action vhumpa/adamw - reach out to GNOME for opinions on presenting duplicate application names in overview
|| [[#t15:21:01|15:21]]
|- id="t15:21:04"
! style="background-color: #488888" | j_dulaney
| style="color: #488888" | Viking-Ice:  I'm not sure about within other DEs
|| [[#t15:21:04|15:21]]
|- id="t15:21:21"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | Viking-Ice: KDE solves it iirc, but it's not specific to a single DE
|| [[#t15:21:21|15:21]]
|- id="t15:21:44"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | While we are here, anything else on release criteria?
|| [[#t15:21:44|15:21]]
|- id="t15:21:59"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | adamw: any other notable criteria changes to highlight?
|| [[#t15:21:59|15:21]]
|- id="t15:22:30"
! style="background-color: #818144" | adamw
| style="color: #818144" | er, i think i did some
|| [[#t15:22:30|15:22]]
|- id="t15:22:36"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | heh
|| [[#t15:22:36|15:22]]
|- id="t15:22:40"
! style="background-color: #818144" | adamw
| style="color: #818144" | but i think we may have covered them last week
|| [[#t15:22:40|15:22]]
|- id="t15:22:43"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | okay
|| [[#t15:22:43|15:22]]
|- id="t15:22:50"
! style="background-color: #818144" | adamw
| style="color: #818144" | oh, the 'release-blocking desktops' thing may have been this week
|| [[#t15:22:50|15:22]]
|- id="t15:23:01"
! style="background-color: #488888" | j_dulaney
| style="color: #488888" | That was last
|| [[#t15:23:01|15:23]]
|- id="t15:23:08"
! style="background-color: #818144" | adamw
| style="color: #818144" | okay. then, i think nothing new.
|| [[#t15:23:08|15:23]]
|- id="t15:23:12"
! style="background-color: #818144" | adamw
| style="color: #818144" | (sorry, it's been a busy week.)
|| [[#t15:23:12|15:23]]
|- id="t15:23:19"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | okay, then moving on
|| [[#t15:23:19|15:23]]
|- id="t15:23:32"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | I'm switching the next two topics so we don't keep tgr__ waiting too long
|| [[#t15:23:32|15:23]]
|- id="t15:23:40"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #topic IPv6 Test Day
|| [[#t15:23:40|15:23]]
|- id="t15:23:46"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #link [[QA/Test_Day:2011-06-08_IPv6]]
|| [[#t15:23:46|15:23]]
|- id="t15:24:06"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #info World IPv6 Day is happening on June 8, along with a Fedora IPv6 test day
|| [[#t15:24:06|15:24]]
|- id="t15:24:22"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | so this is just intended as a check-in for Test Day preparedness
|| [[#t15:24:22|15:24]]
|- id="t15:24:57"
| colspan="2" | * j_dulaney has the network in his house setup for IPv6 already
|| [[#t15:24:57|15:24]]
|- id="t15:25:14"
! style="background-color: #818144" | adamw
| style="color: #818144" | i haven't checked in on this for a few days i'm afraid
|| [[#t15:25:14|15:25]]
|- id="t15:25:17"
! style="background-color: #818144" | adamw
| style="color: #818144" | since my last email shot
|| [[#t15:25:17|15:25]]
|- id="t15:25:25"
! style="background-color: #818144" | adamw
| style="color: #818144" | anyone know of any recent developments?
|| [[#t15:25:25|15:25]]
|- id="t15:25:25"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | looks like we have 2 test cases linked .. .and one in need of a test case
|| [[#t15:25:25|15:25]]
|- id="t15:25:40"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | tgr__: any updates/concerns on your end with regards to test day prep?
|| [[#t15:25:40|15:25]]
|- id="t15:25:43"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #link http://fedoraproject.org/wiki/QA:Testcase_NetworkManager_ipv6
|| [[#t15:25:43|15:25]]
|- id="t15:25:47"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #link
|| [[#t15:25:47|15:25]]
|- id="t15:25:50"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #link http://fedoraproject.org/wiki/QA:Testcase_NFS_ipv6
|| [[#t15:25:50|15:25]]
|- id="t15:26:14"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #info test case needed for ipv6 printing
|| [[#t15:26:14|15:26]]
|- id="t15:26:29"
! style="background-color: #854685" | tgr__
| style="color: #854685" | Red Hat will announce the event in a blog and refer to the Fedora test and ask for participation
|| [[#t15:26:29|15:26]]
|- id="t15:26:41"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | tgr__: do you know when that is going out?
|| [[#t15:26:41|15:26]]
|- id="t15:27:01"
| colspan="2" | * Viking-Ice throws in --&gt; http://ipv6eyechart.ripe.net/  &lt;-- for interested parties reading the meeting logs..
|| [[#t15:27:01|15:27]]
|- id="t15:27:03"
! style="background-color: #854685" | tgr__
| style="color: #854685" | tomorrow if everything goes right
|| [[#t15:27:03|15:27]]
|- id="t15:27:10"
! style="background-color: #818144" | adamw
| style="color: #818144" | awesome
|| [[#t15:27:10|15:27]]
|- id="t15:27:18"
! style="background-color: #9b519b" | rbergeron
| style="color: #9b519b" | the press blog?
|| [[#t15:27:18|15:27]]
|- id="t15:27:20"
! style="background-color: #854685" | tgr__
| style="color: #854685" | I've written a howto which covers enabling ipv6 on RHEL/fedora
|| [[#t15:27:20|15:27]]
|- id="t15:27:21"
! style="background-color: #818144" | adamw
| style="color: #818144" | today would be a good day to be blogging about this for everyone else
|| [[#t15:27:21|15:27]]
|- id="t15:27:35"
! style="background-color: #854685" | tgr__
| style="color: #854685" | using configuration file/NetworkManager
|| [[#t15:27:35|15:27]]
|- id="t15:27:59"
! style="background-color: #854685" | tgr__
| style="color: #854685" | and instructions how to verify if a website has been reached via IPv6 or not
|| [[#t15:27:59|15:27]]
|- id="t15:28:10"
! style="background-color: #854685" | tgr__
| style="color: #854685" | this alone should get us some feedback on any basic issues
|| [[#t15:28:10|15:28]]
|- id="t15:28:27"
! style="background-color: #488888" | j_dulaney
| style="color: #488888" | tgr_:  You want to link to that for info?
|| [[#t15:28:27|15:28]]
|- id="t15:28:36"
! style="background-color: #488888" | j_dulaney
| style="color: #488888" | Or is it not online, yet?
|| [[#t15:28:36|15:28]]
|- id="t15:28:48"
| colspan="2" | * j_dulaney notes that he'll put something in his blog as well.
|| [[#t15:28:48|15:28]]
|- id="t15:28:49"
! style="background-color: #854685" | tgr__
| style="color: #854685" | it's not online yet, we are having ISP troubles
|| [[#t15:28:49|15:28]]
|- id="t15:29:04"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | the wiki links to rawhide live images ... I assume we just want F15 live images for this?
|| [[#t15:29:04|15:29]]
|- id="t15:29:21"
! style="background-color: #854685" | tgr__
| style="color: #854685" | if we can't get it up within red hat I will provide the info via the fedora wiki
|| [[#t15:29:21|15:29]]
|- id="t15:29:22"
! style="background-color: #488888" | j_dulaney
| style="color: #488888" | jlaska: +1
|| [[#t15:29:22|15:29]]
|- id="t15:29:23"
! style="background-color: #818144" | adamw
| style="color: #818144" | yeah, good catch, let's fix that
|| [[#t15:29:23|15:29]]
|- id="t15:29:26"
| colspan="2" | * jlaska fixes
|| [[#t15:29:26|15:29]]
|- id="t15:30:37"
! style="background-color: #854685" | tgr__
| style="color: #854685" | i'm working on getting www.fedoraproject.org listed as participant on isoc.org
|| [[#t15:30:37|15:30]]
|- id="t15:30:46"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | anyone want to volunteer to send an event reminder to test-announce@ ?
|| [[#t15:30:46|15:30]]
|- id="t15:30:47"
! style="background-color: #854685" | tgr__
| style="color: #854685" | it's currently only listed as IPv6 enabled website
|| [[#t15:30:47|15:30]]
|- id="t15:30:55"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | tgr__: nice!
|| [[#t15:30:55|15:30]]
|- id="t15:31:12"
! style="background-color: #818144" | adamw
| style="color: #818144" | jlaska: i can do it
|| [[#t15:31:12|15:31]]
|- id="t15:31:24"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | adamw: thank you
|| [[#t15:31:24|15:31]]
|- id="t15:32:03"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | Anyone object if I move the different setup procedures out into unique wiki pages?
|| [[#t15:32:03|15:32]]
|- id="t15:32:07"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | just to clean up the main page a little?
|| [[#t15:32:07|15:32]]
|- id="t15:32:13"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | or is that not really needed
|| [[#t15:32:13|15:32]]
|- id="t15:32:16"
! style="background-color: #488888" | j_dulaney
| style="color: #488888" | jlaska:  Good idea
|| [[#t15:32:16|15:32]]
|- id="t15:32:18"
! style="background-color: #854685" | tgr__
| style="color: #854685" | i think that's a good idea
|| [[#t15:32:18|15:32]]
|- id="t15:32:31"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | okay, I'll make a minor adjustment after the meeting
|| [[#t15:32:31|15:32]]
|- id="t15:32:37"
! style="background-color: #818144" | adamw
| style="color: #818144" | yeah sounds great
|| [[#t15:32:37|15:32]]
|- id="t15:32:53"
! style="background-color: #854685" | tgr__
| style="color: #854685" | i will add instructions how to do setup if isp provides native ipv6 connectivity
|| [[#t15:32:53|15:32]]
|- id="t15:32:56"
! style="background-color: #818144" | adamw
| style="color: #818144" | there's some boilerplate text still in there too which we should remove
|| [[#t15:32:56|15:32]]
|- id="t15:33:08"
! style="background-color: #488888" | j_dulaney
| style="color: #488888" | +1
|| [[#t15:33:08|15:33]]
|- id="t15:33:11"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | adamw: like the test results stuff?
|| [[#t15:33:11|15:33]]
|- id="t15:33:13"
! style="background-color: #818144" | adamw
| style="color: #818144" | "Provide a list of test areas or test cases that you'd like contributors to execute. For other examples, see Category:Test_Cases. "
|| [[#t15:33:13|15:33]]
|- id="t15:33:15"
! style="background-color: #818144" | adamw
| style="color: #818144" | and yes
|| [[#t15:33:15|15:33]]
|- id="t15:33:21"
! style="background-color: #818144" | adamw
| style="color: #818144" | though we need to set up a proper table for that
|| [[#t15:33:21|15:33]]
|- id="t15:33:29"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | okay ... I'll include that in my wiki cleanup
|| [[#t15:33:29|15:33]]
|- id="t15:33:33"
! style="background-color: #818144" | adamw
| style="color: #818144" | thanks
|| [[#t15:33:33|15:33]]
|- id="t15:33:42"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #action adamw - send test-announce@ for IPv6 test day
|| [[#t15:33:42|15:33]]
|- id="t15:33:53"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #action jlaska - test day wiki cleanup (remove boilerplate)
|| [[#t15:33:53|15:33]]
|- id="t15:34:10"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #action tgr__ - provide wiki instructions for native ipv6 connectivity
|| [[#t15:34:10|15:34]]
|- id="t15:34:20"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | feel free to grab any #action's that I missed
|| [[#t15:34:20|15:34]]
|- id="t15:35:25"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | tgr__: thanks for joining today ... anything else you want to cover before we move on?
|| [[#t15:35:25|15:35]]
|- id="t15:35:40"
! style="background-color: #854685" | tgr__
| style="color: #854685" | jlaska: i think i'm done, thanks
|| [[#t15:35:40|15:35]]
|- id="t15:35:48"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | tgr__: great, thank you!
|| [[#t15:35:48|15:35]]
|- id="t15:35:54"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #topic AutoQA Updates
|| [[#t15:35:54|15:35]]
|- id="t15:36:08"
| colspan="2" | * kparal goes on stage
|| [[#t15:36:08|15:36]]
|- id="t15:36:19"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | it's time for a regular autoqa check-in!
|| [[#t15:36:19|15:36]]
|- id="t15:36:24"
! style="background-color: #539e9e" | kparal
| style="color: #539e9e" | I have only one update today
|| [[#t15:36:24|15:36]]
|- id="t15:36:30"
| colspan="2" | * jlaska sees he has plenty of unread autoqa-devel mails to catch up on
|| [[#t15:36:30|15:36]]
|- id="t15:36:47"
! style="background-color: #539e9e" | kparal
| style="color: #539e9e" | and that is the announcement of 'pretty patch' that was just posted into autoqa-devel
|| [[#t15:36:47|15:36]]
|- id="t15:36:49"
! style="background-color: #539e9e" | kparal
| style="color: #539e9e" | #link https://fedorahosted.org/pipermail/autoqa-devel/2011-June/002344.html
|| [[#t15:36:49|15:36]]
|- id="t15:37:07"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | woah, that knocks out quite a few tickets :)
|| [[#t15:37:07|15:37]]
|- id="t15:37:22"
! style="background-color: #539e9e" | kparal
| style="color: #539e9e" | this patch should allow us to create pretty html logs
|| [[#t15:37:22|15:37]]
|- id="t15:37:22"
| colspan="2" | * j_dulaney was just looking at that
|| [[#t15:37:22|15:37]]
|- id="t15:37:35"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | yay! ...
|| [[#t15:37:35|15:37]]
|- id="t15:37:36"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #link http://kparal.fedorapeople.org/autoqa/upgradepath2.html
|| [[#t15:37:36|15:37]]
|- id="t15:37:36"
! style="background-color: #488888" | j_dulaney
| style="color: #488888" | Shiny
|| [[#t15:37:36|15:37]]
|- id="t15:37:40"
! style="background-color: #539e9e" | kparal
| style="color: #539e9e" | they should be more concise and readable than the previous logs
|| [[#t15:37:40|15:37]]
|- id="t15:38:13"
! style="background-color: #818144" | adamw
| style="color: #818144" | ooooooh pretty
|| [[#t15:38:13|15:38]]
|- id="t15:38:19"
! style="background-color: #488888" | j_dulaney
| style="color: #488888" | More shiny
|| [[#t15:38:19|15:38]]
|- id="t15:38:22"
! style="background-color: #8c4a4a" | vhumpa
| style="color: #8c4a4a" | Thus the name :)
|| [[#t15:38:22|15:38]]
|- id="t15:38:26"
| colspan="2" | * j_dulaney likes shiny
|| [[#t15:38:26|15:38]]
|- id="t15:38:27"
! style="background-color: #818144" | adamw
| style="color: #818144" | now people will break their packages just to see the failure
|| [[#t15:38:27|15:38]]
|- id="t15:38:38"
! style="background-color: #539e9e" | kparal
| style="color: #539e9e" | now we need to review the patch and merge into master. but the most of the work should be done already
|| [[#t15:38:38|15:38]]
|- id="t15:38:45"
! style="background-color: #539e9e" | kparal
| style="color: #539e9e" | adamw: let's hope not :)
|| [[#t15:38:45|15:38]]
|- id="t15:38:46"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #link http://kparal.fedorapeople.org/autoqa/depcheck.html
|| [[#t15:38:46|15:38]]
|- id="t15:39:13"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | that's awesome stuff
|| [[#t15:39:13|15:39]]
|- id="t15:39:22"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | I think I can understand depcheck output now :)
|| [[#t15:39:22|15:39]]
|- id="t15:39:23"
! style="background-color: #488888" | j_dulaney
| style="color: #488888" | Wow, the shiny just keeps piling up
|| [[#t15:39:23|15:39]]
|- id="t15:39:33"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | hopefully I can stop bugging tflink for help with that!
|| [[#t15:39:33|15:39]]
|- id="t15:39:37"
! style="background-color: #539e9e" | kparal
| style="color: #539e9e" | this patch should be the core of 0.5.0 release, hopefully to come really soon
|| [[#t15:39:37|15:39]]
|- id="t15:39:51"
! style="background-color: #539e9e" | kparal
| style="color: #539e9e" | together with email reduction patch from tflink
|| [[#t15:39:51|15:39]]
|- id="t15:40:01"
! style="background-color: #488888" | j_dulaney
| style="color: #488888" | How's that one going?
|| [[#t15:40:01|15:40]]
|- id="t15:40:16"
! style="background-color: #a25555" | tflink
| style="color: #a25555" | pretty much done, other than a little bit more of cleanup and testing
|| [[#t15:40:16|15:40]]
|- id="t15:40:30"
| colspan="2" | * j_dulaney keeps getting distracted; cheerleaders
|| [[#t15:40:30|15:40]]
|- id="t15:40:40"
! style="background-color: #a25555" | tflink
| style="color: #a25555" | I'm planning to send out a patch email to autoqa-devel today
|| [[#t15:40:40|15:40]]
|- id="t15:40:59"
! style="background-color: #539e9e" | kparal
| style="color: #539e9e" | tflink: great
|| [[#t15:40:59|15:40]]
|- id="t15:41:06"
! style="background-color: #8c4a4a" | vhumpa
| style="color: #8c4a4a" | tflink: nice!
|| [[#t15:41:06|15:41]]
|- id="t15:41:27"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | tflink: I still haven't heard back yet on the email notification for all passed results
|| [[#t15:41:27|15:41]]
|- id="t15:41:27"
! style="background-color: #488888" | j_dulaney
| style="color: #488888" | +1
|| [[#t15:41:27|15:41]]
|- id="t15:41:49"
! style="background-color: #a25555" | tflink
| style="color: #a25555" | jlaska: I'll make sure that the configuration works so that we can change it later
|| [[#t15:41:49|15:41]]
|- id="t15:41:54"
! style="background-color: #a25555" | tflink
| style="color: #a25555" | without changing code
|| [[#t15:41:54|15:41]]
|- id="t15:41:58"
! style="background-color: #539e9e" | kparal
| style="color: #539e9e" | jlaska: I have talked to some developers and they liked the idea of not getting bothered when everything works fine
|| [[#t15:41:58|15:41]]
|- id="t15:41:59"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | tflink: but I now see my lucky ping recipient online ... so I'll see if we can get some more info
|| [[#t15:41:59|15:41]]
|- id="t15:42:41"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | kparal: okay, good to know ... sounds like this will be tunable (without patching) based on how tflink is implementing
|| [[#t15:42:41|15:42]]
|- id="t15:43:27"
! style="background-color: #539e9e" | kparal
| style="color: #539e9e" | well, and that was the big announcement of today. I have no further updates
|| [[#t15:43:27|15:43]]
|- id="t15:43:31"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #info tflink finalizing test result email reduction patchset - expecting patch out for review later today
|| [[#t15:43:31|15:43]]
|- id="t15:43:52"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | With help from lmr, I've been packaging what will become autotest-0.13.0
|| [[#t15:43:52|15:43]]
|- id="t15:44:09"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | finding a few bugs here and there (nothing major), but so far it's working okay
|| [[#t15:44:09|15:44]]
|- id="t15:44:35"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | note, those changes are in the autoqa fedora-15-testing repo ... so make sure you *arent* using that when you are testing for the next autoqa release
|| [[#t15:44:35|15:44]]
|- id="t15:44:35"
! style="background-color: #8c4a4a" | vhumpa
| style="color: #8c4a4a" | Need to run, bye for now everybody.
|| [[#t15:44:35|15:44]]
|- id="t15:44:38"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | vhumpa: cya!
|| [[#t15:44:38|15:44]]
|- id="t15:45:14"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #info Packaging for soon-to-be-released autotest-0.13.0 almost complete
|| [[#t15:45:14|15:45]]
|- id="t15:45:39"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | kparal: tflink: anything else to cover on AutoQA?  I guess it depends on patch review for when we'll start the packaging machine for autoqa-0.5.0 ?
|| [[#t15:45:39|15:45]]
|- id="t15:46:05"
! style="background-color: #539e9e" | kparal
| style="color: #539e9e" | jlaska: no. yes. :)
|| [[#t15:46:05|15:46]]
|- id="t15:46:30"
! style="background-color: #a25555" | tflink
| style="color: #a25555" | nothing I can think of. review and testing for this week, yes
|| [[#t15:46:30|15:46]]
|- id="t15:46:38"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | heh, okay ... thanks for the autoqa updates all
|| [[#t15:46:38|15:46]]
|- id="t15:46:52"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #topic Open Discussion - &lt;your topic here&gt;
|| [[#t15:46:52|15:46]]
|- id="t15:47:08"
| colspan="2" | * rbergeron raises her hand
|| [[#t15:47:08|15:47]]
|- id="t15:47:10"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | I've got just a quick status update if there are no other open discussion topics
|| [[#t15:47:10|15:47]]
|- id="t15:47:14"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | rbergeron: what's up?
|| [[#t15:47:14|15:47]]
|- id="t15:47:21"
! style="background-color: #9b519b" | rbergeron
| style="color: #9b519b" | jlaska: go first, i have a few minor things
|| [[#t15:47:21|15:47]]
|- id="t15:47:26"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | s/I've got/I have/
|| [[#t15:47:26|15:47]]
|- id="t15:47:45"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #topic Open Discussion - fedora-qa F15 TRAC tickets
|| [[#t15:47:45|15:47]]
|- id="t15:48:07"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | I'm doing some TRAC ticket maintenance to prepare for the retrospective tickets
|| [[#t15:48:07|15:48]]
|- id="t15:48:09"
| colspan="2" | * Viking-Ice points out we need to start looking at potential features being introduced and if we need to cover that ( grub2 and btrfs pop up to my mind )
|| [[#t15:48:09|15:48]]
|- id="t15:48:11"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #link https://fedorahosted.org/fedora-qa/query?status=new&amp;status=assigned&amp;status=reopened&amp;milestone=Fedora+15
|| [[#t15:48:11|15:48]]
|- id="t15:48:28"
! style="background-color: #9b519b" | rbergeron
| style="color: #9b519b" | Viking-Ice: +1
|| [[#t15:48:28|15:48]]
|- id="t15:48:37"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | Viking-Ice: good point ... I believe grub2 is in TRAC already, we'll need something for btrfs I believe
|| [[#t15:48:37|15:48]]
|- id="t15:48:56"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | there are still some open tickets in the 'Fedora 15' TRAC milestone ... I closed out all the completed test events already
|| [[#t15:48:56|15:48]]
|- id="t15:49:15"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | and I'll likely start annoying ticket owners to find the most suitable outcome for any remaining tickets
|| [[#t15:49:15|15:49]]
|- id="t15:49:21"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | prepare to be annoyed!
|| [[#t15:49:21|15:49]]
|- id="t15:49:52"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #chair rbergeron
|| [[#t15:49:52|15:49]]
|- id="t15:49:52"
! style="background-color: #42427e" | zodbot
| style="color: #42427e" | Current chairs: jlaska rbergeron
|| [[#t15:49:52|15:49]]
|- id="t15:49:55"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | rbergeron: #topic away
|| [[#t15:49:55|15:49]]
|- id="t15:50:00"
! style="background-color: #9b519b" | rbergeron
| style="color: #9b519b" | Woot. thanks
|| [[#t15:50:00|15:50]]
|- id="t15:50:04"
! style="background-color: #488888" | j_dulaney
| style="color: #488888" | jlaska: Since I'm already using btrfs, I can start on test cases for it
|| [[#t15:50:04|15:50]]
|- id="t15:50:04"
! style="background-color: #9b519b" | rbergeron
| style="color: #9b519b" | #topic Schedule
|| [[#t15:50:04|15:50]]
|- id="t15:50:12"
! style="background-color: #9b519b" | rbergeron
| style="color: #9b519b" | #link [[Releases/16/Schedule]]
|| [[#t15:50:12|15:50]]
|- id="t15:50:21"
! style="background-color: #9b519b" | rbergeron
| style="color: #9b519b" | #info schedule is posted, feedback is welcome, please.
|| [[#t15:50:21|15:50]]
|- id="t15:50:41"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | rbergeron: is there any *easy* way to diff the F15 and F16 schedules?
|| [[#t15:50:41|15:50]]
|- id="t15:50:51"
! style="background-color: #9b519b" | rbergeron
| style="color: #9b519b" | I know you guys have a retrospective; if there are things to be converted into schedule changes, let me know.
|| [[#t15:50:51|15:50]]
|- id="t15:50:59"
! style="background-color: #9b519b" | rbergeron
| style="color: #9b519b" | jlaska: ahahahahaha.
|| [[#t15:50:59|15:50]]
|- id="t15:51:08"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | okay, I'll be bugging you about any schedule topics that come out of the retrospective
|| [[#t15:51:08|15:51]]
|- id="t15:51:15"
! style="background-color: #9b519b" | rbergeron
| style="color: #9b519b" | I assume you mean the "original" schedule vs. schedule as it turned out?
|| [[#t15:51:15|15:51]]
|- id="t15:51:19"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | rbergeron: I should clarify ... a human-readable diff :)
|| [[#t15:51:19|15:51]]
|- id="t15:51:26"
! style="background-color: #9b519b" | rbergeron
| style="color: #9b519b" | I haven't added anything *new* for you guys.
|| [[#t15:51:26|15:51]]
|- id="t15:51:33"
! style="background-color: #9b519b" | rbergeron
| style="color: #9b519b" | I'd speculate that the easiest way would be this:
|| [[#t15:51:33|15:51]]
|- id="t15:51:38"
! style="background-color: #818144" | adamw
| style="color: #818144" | are any of the windows noticeably different?
|| [[#t15:51:38|15:51]]
|- id="t15:52:09"
! style="background-color: #9b519b" | rbergeron
| style="color: #9b519b" | http://rbergero.fedorapeople.org/schedules/f-15/f-15-quality-tasks.html vs. http://rbergero.fedorapeople.org/schedules/f-16/f-16-quality-tasks.html
|| [[#t15:52:09|15:52]]
|- id="t15:52:17"
! style="background-color: #9b519b" | rbergeron
| style="color: #9b519b" | adamw: they shouldn't be.
|| [[#t15:52:17|15:52]]
|- id="t15:52:32"
! style="background-color: #9b519b" | rbergeron
| style="color: #9b519b" | Other than - the dates showing in *that* F15 schedule are the slipped dates.
|| [[#t15:52:32|15:52]]
|- id="t15:52:39"
! style="background-color: #4b904b" | Viking-Ice
| style="color: #4b904b" | you might want to compose any previous schedules as in what they where and how they turned out to be
|| [[#t15:52:39|15:52]]
|- id="t15:52:39"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | ah, okay
|| [[#t15:52:39|15:52]]
|- id="t15:52:57"
! style="background-color: #9b519b" | rbergeron
| style="color: #9b519b" | This schedule is more or less as the original f15 schedule was.
|| [[#t15:52:57|15:52]]
|- id="t15:53:16"
! style="background-color: #9b519b" | rbergeron
| style="color: #9b519b" | Just, 6 months later.
|| [[#t15:53:16|15:53]]
|- id="t15:54:01"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | I'll try to come up with more focused feedback after finishing the retrospective ... but the branch timing and Alpha still lend to slippage
|| [[#t15:54:01|15:54]]
|- id="t15:54:08"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | I don't have any great ideas at the moment
|| [[#t15:54:08|15:54]]
|- id="t15:54:14"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | will try to process
|| [[#t15:54:14|15:54]]
|- id="t15:54:33"
| colspan="2" | * rbergeron nods
|| [[#t15:54:33|15:54]]
|- id="t15:54:47"
! style="background-color: #9b519b" | rbergeron
| style="color: #9b519b" | happy to have a brainstorming meeting with you / whoever else is interested.
|| [[#t15:54:47|15:54]]
|- id="t15:54:51"
! style="background-color: #9b519b" | rbergeron
| style="color: #9b519b" | (or should be there, lol)
|| [[#t15:54:51|15:54]]
|- id="t15:54:52"
| colspan="2" | * jlaska notes ... there isn't an option to "Create a new month" in the schedule
|| [[#t15:54:52|15:54]]
|- id="t15:55:12"
| colspan="2" | * Viking-Ice is not foreseeing any slips this release cycle..
|| [[#t15:55:12|15:55]]
|- id="t15:55:30"
! style="background-color: #9b519b" | rbergeron
| style="color: #9b519b" | any other schedule q's/comments?
|| [[#t15:55:30|15:55]]
|- id="t15:55:59"
! style="background-color: #9b519b" | rbergeron
| style="color: #9b519b" | #topic Fixing features
|| [[#t15:55:59|15:55]]
|- id="t15:56:06"
! style="background-color: #9b519b" | rbergeron
| style="color: #9b519b" | I'll keep this brief:
|| [[#t15:56:06|15:56]]
|- id="t15:56:43"
! style="background-color: #9b519b" | rbergeron
| style="color: #9b519b" | Basically some folks have mentioned that the feature process is perhaps not quite as robust as it could be, or could account for "different types of features" better (aka: marketing-ish features vs. stuff that is going to break the universe features)
|| [[#t15:56:43|15:56]]
|- id="t15:56:54"
! style="background-color: #9b519b" | rbergeron
| style="color: #9b519b" | [[Fixing_features]] &lt;--- your feedback is welcome.
|| [[#t15:56:54|15:56]]
|- id="t15:57:12"
! style="background-color: #9b519b" | rbergeron
| style="color: #9b519b" | #info if you have any thoughts on the good, the bad, the ugly in the feature process, feel free to add your commentary to wiki page.
|| [[#t15:57:12|15:57]]
|- id="t15:57:17"
! style="background-color: #9b519b" | rbergeron
| style="color: #9b519b" | And that's all on that.
|| [[#t15:57:17|15:57]]
|- id="t15:57:24"
| colspan="2" | * jlaska queues for reading
|| [[#t15:57:24|15:57]]
|- id="t15:57:25"
| colspan="2" | * rbergeron looks around before continuing
|| [[#t15:57:25|15:57]]
|- id="t15:57:51"
! style="background-color: #4b904b" | Viking-Ice
| style="color: #4b904b" | features aren't mandadory process afaik ..
|| [[#t15:57:51|15:57]]
|- id="t15:58:26"
! style="background-color: #818144" | adamw
| style="color: #818144" | yes
|| [[#t15:58:26|15:58]]
|- id="t15:58:47"
! style="background-color: #9b519b" | rbergeron
| style="color: #9b519b" | well, i think that depends. and I think that's part of the problem.
|| [[#t15:58:47|15:58]]
|- id="t15:58:55"
! style="background-color: #9b519b" | rbergeron
| style="color: #9b519b" | but not going to open pandora's box at the moment. :)
|| [[#t15:58:55|15:58]]
|- id="t15:59:04"
! style="background-color: #9b519b" | rbergeron
| style="color: #9b519b" | Just wnated to give a heads-up to that, if you're interested.
|| [[#t15:59:04|15:59]]
|- id="t15:59:07"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | yes, save that for #pandora :)
|| [[#t15:59:07|15:59]]
|- id="t15:59:12"
! style="background-color: #9b519b" | rbergeron
| style="color: #9b519b" | #topic Cloud stuff
|| [[#t15:59:12|15:59]]
|- id="t15:59:35"
! style="background-color: #9b519b" | rbergeron
| style="color: #9b519b" | You may notice that there are a boatload of cloud features for f16, we're already talking about test-day stuff, possibly  breaking into two test days.
|| [[#t15:59:35|15:59]]
|- id="t15:59:45"
! style="background-color: #9b519b" | rbergeron
| style="color: #9b519b" | ke4qqq posted something to the cloud list for anyone who might be interested in helping us work that stuff out.
|| [[#t15:59:45|15:59]]
|- id="t15:59:49"
! style="background-color: #9b519b" | rbergeron
| style="color: #9b519b" | http://lists.fedoraproject.org/pipermail/cloud/2011-June/000632.html
|| [[#t15:59:49|15:59]]
|- id="t16:00:06"
! style="background-color: #9b519b" | rbergeron
| style="color: #9b519b" | (basically, we haz lots of stuff, we should start planning now rather than last second like last time.)
|| [[#t16:00:06|16:00]]
|- id="t16:00:06"
! style="background-color: #818144" | adamw
| style="color: #818144" | awesome
|| [[#t16:00:06|16:00]]
|- id="t16:00:23"
! style="background-color: #9b519b" | rbergeron
| style="color: #9b519b" | because there is going to be a lotta stuff. :)
|| [[#t16:00:23|16:00]]
|- id="t16:00:23"
! style="background-color: #818144" | adamw
| style="color: #818144" | it's definitely a good idea to hash out a clear test day topic
|| [[#t16:00:23|16:00]]
|- id="t16:00:31"
! style="background-color: #818144" | adamw
| style="color: #818144" | 'cloud test day' is pretty vague, so splitting it like last time is good\
|| [[#t16:00:31|16:00]]
|- id="t16:00:40"
! style="background-color: #488888" | j_dulaney
| style="color: #488888" | Are there going to be any clouds setup specifically for us to test on?
|| [[#t16:00:40|16:00]]
|- id="t16:00:40"
! style="background-color: #818144" | adamw
| style="color: #818144" | we can always make room for more test days, so don't worry about having too many
|| [[#t16:00:40|16:00]]
|- id="t16:00:45"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | yeah, I think that worked pretty well
|| [[#t16:00:45|16:00]]
|- id="t16:00:47"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | wasn't too vague
|| [[#t16:00:47|16:00]]
|- id="t16:00:49"
! style="background-color: #9b519b" | rbergeron
| style="color: #9b519b" | yeah, and we can group them by different types of cloud apps.
|| [[#t16:00:49|16:00]]
|- id="t16:00:56"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | cloud test week :)
|| [[#t16:00:56|16:00]]
|- id="t16:01:12"
! style="background-color: #9b519b" | rbergeron
| style="color: #9b519b" | j_dulaney: unknown. that's part of what we need to solve ahead of time, so we can get that kind of thing set up for folks without it being a nightmare.
|| [[#t16:01:12|16:01]]
|- id="t16:01:17"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | anyway ... will have to see how the features fall out
|| [[#t16:01:17|16:01]]
|- id="t16:01:18"
! style="background-color: #4b904b" | Viking-Ice
| style="color: #4b904b" | cloud test week sounds like a good way to proceed
|| [[#t16:01:18|16:01]]
|- id="t16:01:22"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | s/fall/pan/
|| [[#t16:01:22|16:01]]
|- id="t16:01:33"
! style="background-color: #488888" | j_dulaney
| style="color: #488888" | +1
|| [[#t16:01:33|16:01]]
|- id="t16:01:40"
! style="background-color: #9b519b" | rbergeron
| style="color: #9b519b" | But: would appreciate any feedback if you're on the cloud list. :)
|| [[#t16:01:40|16:01]]
|- id="t16:01:43"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | Viking-Ice: I know you like the test week idea ... assuming we have a series of clear topics, that might work
|| [[#t16:01:43|16:01]]
|- id="t16:01:48"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | rbergeron: okay
|| [[#t16:01:48|16:01]]
|- id="t16:02:03"
! style="background-color: #9b519b" | rbergeron
| style="color: #9b519b" | And would like to invite folks to come to a meeting maybe in 2 weeks or so, but will update on that next week. :)
|| [[#t16:02:03|16:02]]
|- id="t16:02:07"
! style="background-color: #9b519b" | rbergeron
| style="color: #9b519b" | That's it. :)
|| [[#t16:02:07|16:02]]
|- id="t16:02:17"
! style="background-color: #488888" | j_dulaney
| style="color: #488888" | Sweet
|| [[#t16:02:17|16:02]]
|- id="t16:02:25"
| colspan="2" | * j_dulaney is getting hungry
|| [[#t16:02:25|16:02]]
|- id="t16:02:51"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #topic Open Discussion - Last call for topics
|| [[#t16:02:51|16:02]]
|- id="t16:03:05"
! style="background-color: #4b904b" | Viking-Ice
| style="color: #4b904b" | jlaska, cloud test week which would cover Aeolus,CloudFS,CloudStactk, Sheepdog testing..
|| [[#t16:03:05|16:03]]
|- id="t16:03:06"
| colspan="2" | * jlaska sets the fuse for 2 minutes
|| [[#t16:03:06|16:03]]
|- id="t16:03:40"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | Viking-Ice: yeah, could be ... will see what comes out of that thread
|| [[#t16:03:40|16:03]]
|- id="t16:04:05"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | 1 minute until #endmeeting ...
|| [[#t16:04:05|16:04]]
|- id="t16:04:14"
| colspan="2" | * j_dulaney wanders off in search of food and to start thinking about btrfs test case
|| [[#t16:04:14|16:04]]
|- id="t16:04:19"
! style="background-color: #488888" | j_dulaney
| style="color: #488888" | Peace, y'all
|| [[#t16:04:19|16:04]]
|- id="t16:04:21"
! style="background-color: #9b519b" | rbergeron
| style="color: #9b519b" | Viking-Ice: yeah, and all the other ones I know of in the pipeline but aren't posted yet (openstack, pacemaker-cloud, $others)
|| [[#t16:04:21|16:04]]
|- id="t16:04:24"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | cya j_dulaney
|| [[#t16:04:24|16:04]]
|- id="t16:04:35"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | 30 seconds until #endmeeting ...
|| [[#t16:04:35|16:04]]
|- id="t16:05:02"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | Thanks everyone for your time today!! ... I'll follow-up with minutes to the list
|| [[#t16:05:02|16:05]]
|- id="t16:05:06"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #endmeeting
|| [[#t16:05:06|16:05]]
|}
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 09:05, 18 September 2016

Attendees

People present (lines said):

  1. jlaska (137)
  2. rbergeron (45)
  3. adamw (40)
  4. j_dulaney (40)
  5. vhumpa (35)
  6. kparal (15)
  7. Viking-Ice (15)
  8. tgr__ (14)
  9. tflink (6)
  10. athmane (4)
  11. jsmith (2)
  12. Southern_Gentlem (1)

Unable to attend:

  1. Rhe (hopefully sleeping)
  2. Hongqing (hopefully sleeping)
  3. wutao85 (hopefully sleeping)

Agenda

Release criteria updates


AutoQA updates

  • Kparal reported that the announcement of 'pretty patch' that was just posted into autoqa-devel - https://fedorahosted.org/pipermail/autoqa-devel/2011-June/002344.html
  • Tflink is finalizing test result email reduction patchset - expecting patch out for review later today
  • Jlaska noted that packaging/testing for soon-to-be-released autotest-0.13.0 is almost complete. Packages available in autoqa fedora-15-testing repo.
  1. Patch review and testing of autoqa-0.5.0 expected this week

IPv6 Test Day


Open Discussion - <your topic here>

Fedora-qa F15 TRAC tickets

F16 QA Schedule

Fixing features

  • Discussion is underway on how to identify and resolve specific issues with the feature proces
  • If you have any thoughts on the good, the bad, the ugly in the feature process, feel free to add your commentary to wiki page - Fixing_features

Fedora 16 Cloud Test Days


Action Items

  1. vhumpa/adamw - reach out to GNOME for opinions on presenting duplicate application names in overview
  2. adamw - send test-announce@ for IPv6 test day
  3. jlaska - test day wiki cleanup (remove boilerplate)
  4. tgr - provide wiki instructions for native ipv6 connectivity

IRC Log

jlaska #startmeeting Fedora QA Meeting 15:00
zodbot Meeting started Mon Jun 6 15:00:13 2011 UTC. The chair is jlaska. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00
zodbot Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:00
jlaska #meetingname fedora-qa 15:00
zodbot The meeting name has been set to 'fedora-qa' 15:00
jlaska #topic Roll Call 15:00
* Viking-Ice here.. 15:00
adamw yo 15:00
jlaska tgr__: Hi there ... we're just doing roll call atm 15:00
jlaska Viking-Ice: adamw: hey hey 15:00
* tflink is here 15:00
* athmane is there 15:01
tgr__ well, i'm here :) 15:01
* jlaska greets tflink & athmane 15:01
* jsmith lurks 15:01
* j_dulaney waves 15:01
* kparal here 15:01
jlaska hi j_dulaney && kparal 15:01
* vhumpa says hi 15:02
jlaska helloooo 15:02
* rbergeron takes a seat 15:02
j_dulaney jlaska, vhumpa, kparal 15:02
jlaska okay, let's get started 15:02
jlaska we don't have a complicated/lengthy agenda today ... just checking in on a few recurring topics 15:03
jlaska as always, feel free to raise topics during open-discussion 15:03
jlaska and thanks to vhumpa j_dulaney and adamw for #chair'ing last week 15:03
j_dulaney .bacon 15:03
zodbot I love bacon, you love bacon, WE ALL LOVE BACON! 15:03
vhumpa jlaska: was fun 15:03
j_dulaney Indeed 15:03
jlaska So, I'm skipping the 'previous meeting follow-up' topic today ... since that's really covered by the agenda 15:04
* jlaska queues adamw first .. 15:04
jlaska #topic Release Criteria Updates 15:04
jlaska well, vhumpa too really 15:04
jlaska What's the word on the "too-similar menu names" proposal that went out last week? 15:04
vhumpa jlaska: I started a discussion on test + desktops mailing lists 15:05
* adamw defers to vhumpa 15:05
vhumpa People are supportive of the idea that *something* needs to be done with the issue 15:05
jlaska #info vhumpa started a discussion on test + desktop lists last week 15:05
vhumpa vhumpa: ideas spread from modifying the app launcher to make sure that they would differentiate the apps with same names properly - to just renaming some of the problematic apps 15:06
jlaska I guess depending on the solution ... a different group of people would need to make the changes? 15:07
vhumpa For example of this issue: You all know terminal/terminal etc. 15:07
j_dulaney Indeed 15:07
vhumpa jlaska: Yes, the first one, simply, is upstream 15:07
vhumpa thus not something I think we can do very quickly 15:07
vhumpa Should gnome-shell offer e.g. popups for the app icons, that would present one set of means how to deal with the issue 15:08
Viking-Ice how does QA fit into this discussion as in is this not something all the *DE should take care of among themselves ? 15:08
vhumpa But, I am not sure how reasonable it would be to push that through 15:08
adamw right,viking 15:08
adamw the fix isn't our problem exactly 15:08
athmane Viking-Ice, +1 15:09
jlaska Viking-Ice: yeah ... I'm just seeing this as QA bringing this to appropriate desktop attn 15:09
vhumpa That brings me to what FEdora can do... 15:09
adamw what we're concerned with is whether this should be a release requirement 15:09
j_dulaney Indeed 15:09
vhumpa It's a problem of a few apps really... So what we can do is merely to rename some of them, in their desktop files 15:09
Viking-Ice I'm not seeing this as an release requirement 15:09
vhumpa the QE connection: 15:10
vhumpa enforce that it is done with a requirement 15:10
athmane if we tests each desktop separately this issue will not raise, afaik 15:10
vhumpa athmane: true 15:10
vhumpa athmane: partially 15:11
j_dulaney The biggest issue I see is apps within the same desktop 15:11
vhumpa there are issues even withing single desktop 15:11
jlaska what's the ideal outcome for this topic? ... upstream acknowledgement of the issue? 15:11
vhumpa I suppose so 15:11
jlaska ... formalizing tests and applicable criteria? 15:11
jlaska (depending on whether it's accepted or not) 15:11
vhumpa Meaning.. upstream acknowledgment is a "pony" perhaps 15:12
adamw we should probably add it to the desktop menus test case 15:12
j_dulaney I'm thinking that a good outcome would simply be that what the user sees is different names for different apps 15:12
vhumpa I agree with Adam on this one. 15:12
jlaska I don't see any feedback from anyone upstream on this topic ... have they weighed in on this yet? 15:12
vhumpa jlaska: nope 15:12
athmane maybe we should fill bugs on upstream tracking app ? 15:13
j_dulaney The actual names don't necesarily have to be different for the actual app, just the menu choices 15:13
Viking-Ice are these apps that any of the *DE ship by default or is this something that is mixed apps between *DE ? 15:13
j_dulaney Viking-Ice: Default 15:13
j_dulaney For instance, within just Gnome: Softare Update and Software Updates 15:13
adamw so we have a plan for testing 15:14
vhumpa Some are issue in deafult, some become an issue when you have multiple environments installed 15:14
jlaska What's the next step? Should we focus on trying to get feedback/input from upstream on this topic? 15:14
Viking-Ice anyway this sounds to me just something that the relevant *DE maintainers need to take care of not something related to QA per se 15:14
adamw then the question is, should it be a release criterion, i.e., should we require same name situations to be resolved for release 15:14
jlaska adamw: should we move forward with testing and criteria without feedback from GNOME? 15:14
j_dulaney The QA angle would be enforcement 15:14
vhumpa I would concentrate in choosing menu names around Fedora desktops to minimize this issue... Upstream should come later 15:14
j_dulaney adamw: I think so 15:14
adamw jlaska: feedback would be good, i guess 15:15
jlaska adamw: seems like it should be required to me 15:15
jlaska how can we create criteria and tests without their input? 15:15
* jlaska might be missing something though 15:15
vhumpa The problem lies in how Fedora names apps, which I am not sure how connected is to upstream really 15:15
jlaska err ... I'd want to avoid creating tests and criteria that GNOME isn't interested in honoring/fixing etc... 15:15
jlaska vhumpa: good point ... it really depends on the implementation 15:16
adamw jlaska: well, addressing it upstream is only one approach 15:16
jlaska yes, I see now, gotcha 15:16
adamw i can see, for instance, that if upstream GNOME decide they don't care, we would decide Fedora still does care 15:16
jlaska right, that makes sense 15:16
vhumpa adamw: yes 15:16
jlaska so when will we know which of those routes to take? 15:16
Viking-Ice sounds like a ( test ) candidate for fit and finish 15:16
j_dulaney +1 15:16
jlaska I guess we can conclude that if we don't get GNOME feedback, then it's up to Fedora to decide? 15:17
vhumpa So the question is 1) Do we ask upstream to help with this 2) We just rename a few menu items in Fedora 15:17
* j_dulaney goes with 2 15:18
vhumpa +1 15:18
Southern_Gentlem both 15:18
j_dulaney Easiest solution 15:18
* jsmith goes with 1) 15:18
Viking-Ice both 15:18
jlaska we'll likely go with #2 ... but I'd like to give #1 another attempt 15:18
adamw vhumpa: i think that's kind of up to the devs to decide really 15:18
adamw i think we may be going round in circles at this point? 15:18
jlaska yup ... let's wrap up on this topic 15:18
vhumpa 1) definitely too - but facing reality that it would be a more long term solution but for later 15:18
vhumpa True 15:19
jlaska anyone want to approach GNOME with this topic this week? 15:19
jlaska if not ... I'll take it 15:19
jlaska or any other #action items ... feel free to grab 15:19
vhumpa If I know how to approach them, I will 15:19
jlaska vhumpa: okay, thank you 15:20
jlaska anything else to cover on this before next week? 15:20
adamw i'll sync up with you on that 15:20
Viking-Ice is this only relevant to Gnome or is this problem present in all *DE we ship ? 15:20
vhumpa Meaning: we'll be aproaching for modifing the launcher, right? You don't just mean renaming apps on Upstream side 15:20
vhumpa Unsure on that 15:20
jlaska #action vhumpa/adamw - reach out to GNOME for opinions on presenting duplicate application names in overview 15:21
j_dulaney Viking-Ice: I'm not sure about within other DEs 15:21
jlaska Viking-Ice: KDE solves it iirc, but it's not specific to a single DE 15:21
jlaska While we are here, anything else on release criteria? 15:21
jlaska adamw: any other notable criteria changes to highlight? 15:21
adamw er, i think i did some 15:22
jlaska heh 15:22
adamw but i think we may have covered them last week 15:22
jlaska okay 15:22
adamw oh, the 'release-blocking desktops' thing may have been this week 15:22
j_dulaney That was last 15:23
adamw okay. then, i think nothing new. 15:23
adamw (sorry, it's been a busy week.) 15:23
jlaska okay, then moving on 15:23
jlaska I'm switching the next two topics so we don't keep tgr__ waiting too long 15:23
jlaska #topic IPv6 Test Day 15:23
jlaska #link QA/Test_Day:2011-06-08_IPv6 15:23
jlaska #info World IPv6 Day is happening on June 8, along with a Fedora IPv6 test day 15:24
jlaska so this is just intended as a check-in for Test Day preparedness 15:24
* j_dulaney has the network in his house setup for IPv6 already 15:24
adamw i haven't checked in on this for a few days i'm afraid 15:25
adamw since my last email shot 15:25
adamw anyone know of any recent developments? 15:25
jlaska looks like we have 2 test cases linked .. .and one in need of a test case 15:25
jlaska tgr__: any updates/concerns on your end with regards to test day prep? 15:25
jlaska #link http://fedoraproject.org/wiki/QA:Testcase_NetworkManager_ipv6 15:25
jlaska #link 15:25
jlaska #link http://fedoraproject.org/wiki/QA:Testcase_NFS_ipv6 15:25
jlaska #info test case needed for ipv6 printing 15:26
tgr__ Red Hat will announce the event in a blog and refer to the Fedora test and ask for participation 15:26
jlaska tgr__: do you know when that is going out? 15:26
* Viking-Ice throws in --> http://ipv6eyechart.ripe.net/ <-- for interested parties reading the meeting logs.. 15:27
tgr__ tomorrow if everything goes right 15:27
adamw awesome 15:27
rbergeron the press blog? 15:27
tgr__ I've written a howto which covers enabling ipv6 on RHEL/fedora 15:27
adamw today would be a good day to be blogging about this for everyone else 15:27
tgr__ using configuration file/NetworkManager 15:27
tgr__ and instructions how to verify if a website has been reached via IPv6 or not 15:27
tgr__ this alone should get us some feedback on any basic issues 15:28
j_dulaney tgr_: You want to link to that for info? 15:28
j_dulaney Or is it not online, yet? 15:28
* j_dulaney notes that he'll put something in his blog as well. 15:28
tgr__ it's not online yet, we are having ISP troubles 15:28
jlaska the wiki links to rawhide live images ... I assume we just want F15 live images for this? 15:29
tgr__ if we can't get it up within red hat I will provide the info via the fedora wiki 15:29
j_dulaney jlaska: +1 15:29
adamw yeah, good catch, let's fix that 15:29
* jlaska fixes 15:29
tgr__ i'm working on getting www.fedoraproject.org listed as participant on isoc.org 15:30
jlaska anyone want to volunteer to send an event reminder to test-announce@ ? 15:30
tgr__ it's currently only listed as IPv6 enabled website 15:30
jlaska tgr__: nice! 15:30
adamw jlaska: i can do it 15:31
jlaska adamw: thank you 15:31
jlaska Anyone object if I move the different setup procedures out into unique wiki pages? 15:32
jlaska just to clean up the main page a little? 15:32
jlaska or is that not really needed 15:32
j_dulaney jlaska: Good idea 15:32
tgr__ i think that's a good idea 15:32
jlaska okay, I'll make a minor adjustment after the meeting 15:32
adamw yeah sounds great 15:32
tgr__ i will add instructions how to do setup if isp provides native ipv6 connectivity 15:32
adamw there's some boilerplate text still in there too which we should remove 15:32
j_dulaney +1 15:33
jlaska adamw: like the test results stuff? 15:33
adamw "Provide a list of test areas or test cases that you'd like contributors to execute. For other examples, see Category:Test_Cases. " 15:33
adamw and yes 15:33
adamw though we need to set up a proper table for that 15:33
jlaska okay ... I'll include that in my wiki cleanup 15:33
adamw thanks 15:33
jlaska #action adamw - send test-announce@ for IPv6 test day 15:33
jlaska #action jlaska - test day wiki cleanup (remove boilerplate) 15:33
jlaska #action tgr__ - provide wiki instructions for native ipv6 connectivity 15:34
jlaska feel free to grab any #action's that I missed 15:34
jlaska tgr__: thanks for joining today ... anything else you want to cover before we move on? 15:35
tgr__ jlaska: i think i'm done, thanks 15:35
jlaska tgr__: great, thank you! 15:35
jlaska #topic AutoQA Updates 15:35
* kparal goes on stage 15:36
jlaska it's time for a regular autoqa check-in! 15:36
kparal I have only one update today 15:36
* jlaska sees he has plenty of unread autoqa-devel mails to catch up on 15:36
kparal and that is the announcement of 'pretty patch' that was just posted into autoqa-devel 15:36
kparal #link https://fedorahosted.org/pipermail/autoqa-devel/2011-June/002344.html 15:36
jlaska woah, that knocks out quite a few tickets :) 15:37
kparal this patch should allow us to create pretty html logs 15:37
* j_dulaney was just looking at that 15:37
jlaska yay! ... 15:37
jlaska #link http://kparal.fedorapeople.org/autoqa/upgradepath2.html 15:37
j_dulaney Shiny 15:37
kparal they should be more concise and readable than the previous logs 15:37
adamw ooooooh pretty 15:38
j_dulaney More shiny 15:38
vhumpa Thus the name :) 15:38
* j_dulaney likes shiny 15:38
adamw now people will break their packages just to see the failure 15:38
kparal now we need to review the patch and merge into master. but the most of the work should be done already 15:38
kparal adamw: let's hope not :) 15:38
jlaska #link http://kparal.fedorapeople.org/autoqa/depcheck.html 15:38
jlaska that's awesome stuff 15:39
jlaska I think I can understand depcheck output now :) 15:39
j_dulaney Wow, the shiny just keeps piling up 15:39
jlaska hopefully I can stop bugging tflink for help with that! 15:39
kparal this patch should be the core of 0.5.0 release, hopefully to come really soon 15:39
kparal together with email reduction patch from tflink 15:39
j_dulaney How's that one going? 15:40
tflink pretty much done, other than a little bit more of cleanup and testing 15:40
* j_dulaney keeps getting distracted; cheerleaders 15:40
tflink I'm planning to send out a patch email to autoqa-devel today 15:40
kparal tflink: great 15:40
vhumpa tflink: nice! 15:41
jlaska tflink: I still haven't heard back yet on the email notification for all passed results 15:41
j_dulaney +1 15:41
tflink jlaska: I'll make sure that the configuration works so that we can change it later 15:41
tflink without changing code 15:41
kparal jlaska: I have talked to some developers and they liked the idea of not getting bothered when everything works fine 15:41
jlaska tflink: but I now see my lucky ping recipient online ... so I'll see if we can get some more info 15:41
jlaska kparal: okay, good to know ... sounds like this will be tunable (without patching) based on how tflink is implementing 15:42
kparal well, and that was the big announcement of today. I have no further updates 15:43
jlaska #info tflink finalizing test result email reduction patchset - expecting patch out for review later today 15:43
jlaska With help from lmr, I've been packaging what will become autotest-0.13.0 15:43
jlaska finding a few bugs here and there (nothing major), but so far it's working okay 15:44
jlaska note, those changes are in the autoqa fedora-15-testing repo ... so make sure you *arent* using that when you are testing for the next autoqa release 15:44
vhumpa Need to run, bye for now everybody. 15:44
jlaska vhumpa: cya! 15:44
jlaska #info Packaging for soon-to-be-released autotest-0.13.0 almost complete 15:45
jlaska kparal: tflink: anything else to cover on AutoQA? I guess it depends on patch review for when we'll start the packaging machine for autoqa-0.5.0 ? 15:45
kparal jlaska: no. yes. :) 15:46
tflink nothing I can think of. review and testing for this week, yes 15:46
jlaska heh, okay ... thanks for the autoqa updates all 15:46
jlaska #topic Open Discussion - <your topic here> 15:46
* rbergeron raises her hand 15:47
jlaska I've got just a quick status update if there are no other open discussion topics 15:47
jlaska rbergeron: what's up? 15:47
rbergeron jlaska: go first, i have a few minor things 15:47
jlaska s/I've got/I have/ 15:47
jlaska #topic Open Discussion - fedora-qa F15 TRAC tickets 15:47
jlaska I'm doing some TRAC ticket maintenance to prepare for the retrospective tickets 15:48
* Viking-Ice points out we need to start looking at potential features being introduced and if we need to cover that ( grub2 and btrfs pop up to my mind ) 15:48
jlaska #link https://fedorahosted.org/fedora-qa/query?status=new&status=assigned&status=reopened&milestone=Fedora+15 15:48
rbergeron Viking-Ice: +1 15:48
jlaska Viking-Ice: good point ... I believe grub2 is in TRAC already, we'll need something for btrfs I believe 15:48
jlaska there are still some open tickets in the 'Fedora 15' TRAC milestone ... I closed out all the completed test events already 15:48
jlaska and I'll likely start annoying ticket owners to find the most suitable outcome for any remaining tickets 15:49
jlaska prepare to be annoyed! 15:49
jlaska #chair rbergeron 15:49
zodbot Current chairs: jlaska rbergeron 15:49
jlaska rbergeron: #topic away 15:49
rbergeron Woot. thanks 15:50
j_dulaney jlaska: Since I'm already using btrfs, I can start on test cases for it 15:50
rbergeron #topic Schedule 15:50
rbergeron #link Releases/16/Schedule 15:50
rbergeron #info schedule is posted, feedback is welcome, please. 15:50
jlaska rbergeron: is there any *easy* way to diff the F15 and F16 schedules? 15:50
rbergeron I know you guys have a retrospective; if there are things to be converted into schedule changes, let me know. 15:50
rbergeron jlaska: ahahahahaha. 15:50
jlaska okay, I'll be bugging you about any schedule topics that come out of the retrospective 15:51
rbergeron I assume you mean the "original" schedule vs. schedule as it turned out? 15:51
jlaska rbergeron: I should clarify ... a human-readable diff :) 15:51
rbergeron I haven't added anything *new* for you guys. 15:51
rbergeron I'd speculate that the easiest way would be this: 15:51
adamw are any of the windows noticeably different? 15:51
rbergeron http://rbergero.fedorapeople.org/schedules/f-15/f-15-quality-tasks.html vs. http://rbergero.fedorapeople.org/schedules/f-16/f-16-quality-tasks.html 15:52
rbergeron adamw: they shouldn't be. 15:52
rbergeron Other than - the dates showing in *that* F15 schedule are the slipped dates. 15:52
Viking-Ice you might want to compose any previous schedules as in what they where and how they turned out to be 15:52
jlaska ah, okay 15:52
rbergeron This schedule is more or less as the original f15 schedule was. 15:52
rbergeron Just, 6 months later. 15:53
jlaska I'll try to come up with more focused feedback after finishing the retrospective ... but the branch timing and Alpha still lend to slippage 15:54
jlaska I don't have any great ideas at the moment 15:54
jlaska will try to process 15:54
* rbergeron nods 15:54
rbergeron happy to have a brainstorming meeting with you / whoever else is interested. 15:54
rbergeron (or should be there, lol) 15:54
* jlaska notes ... there isn't an option to "Create a new month" in the schedule 15:54
* Viking-Ice is not foreseeing any slips this release cycle.. 15:55
rbergeron any other schedule q's/comments? 15:55
rbergeron #topic Fixing features 15:55
rbergeron I'll keep this brief: 15:56
rbergeron Basically some folks have mentioned that the feature process is perhaps not quite as robust as it could be, or could account for "different types of features" better (aka: marketing-ish features vs. stuff that is going to break the universe features) 15:56
rbergeron Fixing_features <--- your feedback is welcome. 15:56
rbergeron #info if you have any thoughts on the good, the bad, the ugly in the feature process, feel free to add your commentary to wiki page. 15:57
rbergeron And that's all on that. 15:57
* jlaska queues for reading 15:57
* rbergeron looks around before continuing 15:57
Viking-Ice features aren't mandadory process afaik .. 15:57
adamw yes 15:58
rbergeron well, i think that depends. and I think that's part of the problem. 15:58
rbergeron but not going to open pandora's box at the moment. :) 15:58
rbergeron Just wnated to give a heads-up to that, if you're interested. 15:59
jlaska yes, save that for #pandora :) 15:59
rbergeron #topic Cloud stuff 15:59
rbergeron You may notice that there are a boatload of cloud features for f16, we're already talking about test-day stuff, possibly breaking into two test days. 15:59
rbergeron ke4qqq posted something to the cloud list for anyone who might be interested in helping us work that stuff out. 15:59
rbergeron http://lists.fedoraproject.org/pipermail/cloud/2011-June/000632.html 15:59
rbergeron (basically, we haz lots of stuff, we should start planning now rather than last second like last time.) 16:00
adamw awesome 16:00
rbergeron because there is going to be a lotta stuff. :) 16:00
adamw it's definitely a good idea to hash out a clear test day topic 16:00
adamw 'cloud test day' is pretty vague, so splitting it like last time is good\ 16:00
j_dulaney Are there going to be any clouds setup specifically for us to test on? 16:00
adamw we can always make room for more test days, so don't worry about having too many 16:00
jlaska yeah, I think that worked pretty well 16:00
jlaska wasn't too vague 16:00
rbergeron yeah, and we can group them by different types of cloud apps. 16:00
jlaska cloud test week :) 16:00
rbergeron j_dulaney: unknown. that's part of what we need to solve ahead of time, so we can get that kind of thing set up for folks without it being a nightmare. 16:01
jlaska anyway ... will have to see how the features fall out 16:01
Viking-Ice cloud test week sounds like a good way to proceed 16:01
jlaska s/fall/pan/ 16:01
j_dulaney +1 16:01
rbergeron But: would appreciate any feedback if you're on the cloud list. :) 16:01
jlaska Viking-Ice: I know you like the test week idea ... assuming we have a series of clear topics, that might work 16:01
jlaska rbergeron: okay 16:01
rbergeron And would like to invite folks to come to a meeting maybe in 2 weeks or so, but will update on that next week. :) 16:02
rbergeron That's it. :) 16:02
j_dulaney Sweet 16:02
* j_dulaney is getting hungry 16:02
jlaska #topic Open Discussion - Last call for topics 16:02
Viking-Ice jlaska, cloud test week which would cover Aeolus,CloudFS,CloudStactk, Sheepdog testing.. 16:03
* jlaska sets the fuse for 2 minutes 16:03
jlaska Viking-Ice: yeah, could be ... will see what comes out of that thread 16:03
jlaska 1 minute until #endmeeting ... 16:04
* j_dulaney wanders off in search of food and to start thinking about btrfs test case 16:04
j_dulaney Peace, y'all 16:04
rbergeron Viking-Ice: yeah, and all the other ones I know of in the pipeline but aren't posted yet (openstack, pacemaker-cloud, $others) 16:04
jlaska cya j_dulaney 16:04
jlaska 30 seconds until #endmeeting ... 16:04
jlaska Thanks everyone for your time today!! ... I'll follow-up with minutes to the list 16:05
jlaska #endmeeting 16:05

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