From Fedora Project Wiki

< QA‎ | Meetings

m (Updated previous TODO list)
m (internal link cleaning)
 
(6 intermediate revisions by one other user not shown)
Line 5: Line 5:
* James Laska (jlaska)
* James Laska (jlaska)
* Jóhann Guðmundsson (viking_ice)
* Jóhann Guðmundsson (viking_ice)
* Jesse Keating (f13)


= Previous meeting follow-up =
= Previous meeting follow-up =
Line 10: Line 11:
* [jlaska+adamw] mediawiki semantic update (packaging and hosting)
* [jlaska+adamw] mediawiki semantic update (packaging and hosting)
** ''REVIEWED'' - [[rhbug:490001|490001]] -  Review Request: mediawiki-semantic - The semantic extension to mediawiki  
** ''REVIEWED'' - [[rhbug:490001|490001]] -  Review Request: mediawiki-semantic - The semantic extension to mediawiki  
** ''NEEDS REVIEW'' - [[rhbug:490171|490171]] -  Review Request: mediawiki-semantic-forms - An extension to MediaWiki that adds support for web-based forms
** ''UNDER REVIEW'' - [[rhbug:490171|490171]] -  Review Request: mediawiki-semantic-forms - An extension to MediaWiki that adds support for web-based forms
** Packages installed in a test instance, next steps involve:
*** [[User:tibbs]] posted some additional concerns for ''mediawiki-semantic-forms'' around licensing which I haven't followed up on yet
*** understanding the framework and wiki linkage
*** request live data dump from infrastructure for testing
*** developing some howto docs/guides
*** request infrastructure hosting
*** request infrastructure hosting


* [f13+wwoods] - autoqa status update  
* [f13+wwoods] - autoqa status update  
** wwoods checked in an initial verifytree test case
** f13 hoping to make a watcher for post-tree-compose
** Next steps ...
**# focus on the tree based tests
**# figuring out better reporting for the existing tests
* [adamw] - schedule radeon test day
* [adamw] - schedule radeon test day
** Schedule and happening today!  - [[Test_Day:Radeon_2009-04-01]]
* [jlaska] - copy F11 beta test results wiki changes into the wiki template (several test case additions)
* [jlaska] - copy F11 beta test results wiki changes into the wiki template (several test case additions)
** Template updated ([[QA:Fedora_11_Install_Results_Template)]] with help from wwoods and jlaska
* [wwoods] - to add some upgrade test cases to the beta results page (and template)
* [wwoods] - to add some upgrade test cases to the beta results page (and template)
** No upgrade cases added yet
* [jlaska] - add Beta known issues for previous disk contents, kickstart issues, KVM NAT networking problems (use static ip)
* [jlaska] - add Beta known issues for previous disk contents, kickstart issues, KVM NAT networking problems (use static ip)
** Met Friday to discuss and add issues to the release notes ... [[Fedora_11_Beta_release_notes#Anaconda_installer_issues]]
* [wwoods] - document any upgrade issues in the Beta release notes
* [wwoods] - document any upgrade issues in the Beta release notes
** Bug#492516 added to release notes
* [jlaska] - setup meeting to review RC test results for Friday afternoon to include release engineering (JesseKeating) and anaconda-devel and any RC testers.
* [jlaska] - setup meeting to review RC test results for Friday afternoon to include release engineering (JesseKeating) and anaconda-devel and any RC testers.
** We met on Friday @ noon EDT in #fedora-qa and hashed out the bug list currently listed in [[Fedora_11_Beta_release_notes#Anaconda_installer_issues]]


= F-11-Beta - who/what/when/where/why? =
= F-11-Beta - who/what/when/where/why? =
The beta was released!  See announcement from Jesse Keating - https://www.redhat.com/archives/fedora-test-list/2009-March/msg01262.html


* Useful links:
* Useful links:
** '''F-11 Schedule''' - https://fedoraproject.org/wiki/Releases/11/Schedule
** '''F-11 Schedule''' - [[Releases/11/Schedule]]
** '''Where to record test results''' - https://fedoraproject.org/wiki/QA:Fedora_11_Beta_Install_Test_Results
** '''Where to record test results''' - [[QA:Fedora_11_Beta_Install_Test_Results]]
** '''Current list of open Beta blockers''' - https://bugzilla.redhat.com/showdependencytree.cgi?id=476774&hide_resolved=1
** '''Current list of open Beta blockers''' - https://bugzilla.redhat.com/showdependencytree.cgi?id=476774&hide_resolved=1
** '''Beta release notes''' - https://fedoraproject.org/wiki/Fedora_11_Beta_release_notes
** '''Beta release notes''' - [[Fedora_11_Beta_release_notes]]


* AdamW confirmed with JesseKeating that the F11Beta bug triage efforts were effective
= Open discussion =
 
== F11Beta blocking bugs ==
 
* Much of the last week was spent
 
== Building the Beta Known issues ==
* Main issues so far include:
*# Previous disk partition layout problems
*# Upgrade testing issues
*# Kickstart installs fragile
 
* AdamW noted that we might not be communicating the known issues effectively since a lot of Alpha testers didn't know about the rpm issue
** Make each known issue a unique section header in the wiki
** Should anaconda display release notes again (or pull down release notes from an html page)?
** Perhaps a desktop menu link for release notes (see fedora-release-notes package)
** Does firefox include the release notes link? (see fedora-release-notes package)
** Result - QA team must internally reference the Beta release notes known issues in all IRC and email communication.


== The Beta RC Process ==
== F10 syslinux package ==


* Jlaska asked to discuss the Beta RC build, test and release process
Adamw noted that livecd-iso-to-disk is failing on F10 systems when trying to create F11 live images.  A lot of Test Day testers are writing their live images only to find the systems are not bootable due to a bug in the F10 syslinux package.
** What information does JesseKeating need to release the bits to the mirrors - confirmation of the anaconda-devel beta readiness criteria
** When do we have to get that feedback in? - Meet Friday around noon in #fedora-qa to provide test feedback


* AdamW asked if it's possible to open up RC testing to a wider audience?
== Schedule Change proposal ==
** we tried in the past, but it flooded the download site and no one could test
Wwoods provided an update on the initial schedule proposal raised in the previous meeting.  After discussion and research, concluded this effort is not worth continuing.  Instead, time should be spent on better tools for testing and reporting, so we can do more efficient testing.
** Would be good to engage people, perhaps time better spent engaging during Rawhide cycle for testing Rawhide


* Jlaska suggested we gather in #fedora-qa on Friday afternoon to discuss RC test feedback
== Communication of Beta Known Issues ==
** JesseKeating recommended we invite the anaconda-devel team


= Open discussion =
* jlaska asked how well we are holding up with our conclusion from the [[QA/Meetings/20090325#Building_the_Beta_Known_issues|previous week]]. 
* Adamw suggested that while the announcement links to the release notes, it doesn't specify the Known issues.  Perhaps this could change for future milestones (check-in with Rahul)?
* Wwoods reminded us about Warren Togami's rawhide status blog - http://rawhidewatch.wordpress.com/


== Development Schedule Proposal ==
== Fedora Calendaring System ==
Wwoods introduced a new Fedora release schedule concept - lengthen the development/test cycle beyond 6 months


** introduce a two-month beta period after the normal 6-month development cycle --> rawhide branch
Adamw noted that the infrastructure team is moving closer to infrastructure hosted calendaring systemMore details on fedora-infrastructure-list (https://www.redhat.com/archives/fedora-infrastructure-list/2009-March/msg00266.html).
** AdamW reminded that the reason we have stable releases at all is to have 'checkpoints' for major changes like the rpm checksum issue, hence our release schedule should match the heckpoints
** Several ideas/concerns were raisedWWoods will review current proposal and open up for feedback post-beta.
*** http://wwoods.fedorapeople.org/schedule.html
*** http://wwoods.fedorapeople.org/images/fedora-ideal-schedules.png


= Upcoming QA events =
= Upcoming QA events =
* 2009-03-26 - [[QA/Test_Days/2009-03-26|Nouveau Test Day]]
* 2009-03-31 - [[BugZappers/Triage_days|BugZapper Triage Day]]
* 2009-04-02 - [[QA/Test_Days/2009-04-02|Power Management Test Day]]
* 2009-04-02 - [[QA/Test_Days/2009-04-02|Power Management Test Day]]
* 2009-04-07 - [[Test_Day:2009-04-07|Anaconda Storage Rewrite Part#2]]
* 2009-04-09 - [[Test_Day:2009-04-09_UEFI|UEFI]]


= Action items =
= Action items =
* [f13+wwoods] - autoqa status update
* [wwoods] - autoqa: work on better (clearer) reporting from existing tests
* [adamw] - schedule radeon test day
* [f13] - autoqa: work on monitor for post-tree-compose
* [jlaska] - copy F11 beta test results wiki changes into the wiki template (several test case additions)
* [adamw] - will file a F10 bug for the syslinux issue, initiate discussion with pjones or jeremy for building a updated F10 package
* [wwoods] - to add some upgrade test cases to the beta results page (and template)
* [jlaska] - check-in with Warren Togami on the rawhidewatch blog ... can Fedora QA help ... what is his vision?
* [jlaska] - add Beta known issues for previous disk contents, kickstart issues, KVM NAT networking problems (use static ip)
* [jlaska+wwoods] - discuss integration between lab-in-a-box and autoqa
* [wwoods] - document any upgrade issues in the Beta release notes
* [jlaska] - setup meeting to review RC test results for Friday afternoon to include release engineering (JesseKeating) and anaconda-devel and any RC testers.


= Next QA meeting =
= Next QA meeting =


The next meeting will be held on [http://www.timeanddate.com/worldclock/meetingdetails.html?year=2009&month=4&day=1&hour=16&min=0&sec=0&p1=207&p2=204 2009-04-01 16:00 UTC]
The next meeting will be held on [http://www.timeanddate.com/worldclock/meetingdetails.html?year=2009&month=4&day=8&hour=16&min=0&sec=0&p1=207&p2=204 2009-04-08 16:00 UTC]


= IRC Transcript =
= IRC Transcript =
{|
|- id="tApr 01 12:00:53"
| colspan="2" | --- | jlaska has changed the topic to: Fedora QA meeting | gathering people
|| [[#tApr 01 12:00:53|Apr 01 12:00]]
|- id="tApr 01 12:01:55"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | Fedora QA meeting starting shortly, we'll get things moving shortly ...
|| [[#tApr 01 12:01:55|Apr 01 12:01]]
|- id="tApr 01 12:02:16"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | show of hands if you're around
|| [[#tApr 01 12:02:16|Apr 01 12:02]]
|- id="tApr 01 12:04:24"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | ping adamw: wwoods: f13: viking_ice ... and any other QA meeting attendees I've missed :)
|| [[#tApr 01 12:04:24|Apr 01 12:04]]
|- id="tApr 01 12:04:50"
! style="background-color: #42427e" | viking_ice
| style="color: #42427e" | | hellú..
|| [[#tApr 01 12:04:50|Apr 01 12:04]]
|- id="tApr 01 12:05:32"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | viking_ice: Ahoj :)
|| [[#tApr 01 12:05:32|Apr 01 12:05]]
|- id="tApr 01 12:05:38"
! style="background-color: #818144" | adamw
| style="color: #818144" | | yo
|| [[#tApr 01 12:05:38|Apr 01 12:05]]
|- id="tApr 01 12:05:44"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | adamw: heyo!
|| [[#tApr 01 12:05:44|Apr 01 12:05]]
|- id="tApr 01 12:06:05"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | wwoods: is back!
|| [[#tApr 01 12:06:05|Apr 01 12:06]]
|- id="tApr 01 12:06:19"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | WITH A VENGEANCE
|| [[#tApr 01 12:06:19|Apr 01 12:06]]
|- id="tApr 01 12:06:22"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | wait, no, just back
|| [[#tApr 01 12:06:22|Apr 01 12:06]]
|- id="tApr 01 12:06:31"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | jlaska: you logging?
|| [[#tApr 01 12:06:31|Apr 01 12:06]]
|- id="tApr 01 12:06:32"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | heh, no bruce willis please :)
|| [[#tApr 01 12:06:32|Apr 01 12:06]]
|- id="tApr 01 12:06:37"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | wwoods: indeed ... go for it
|| [[#tApr 01 12:06:37|Apr 01 12:06]]
|- id="tApr 01 12:06:52"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | we've got viking_ice, adamw  and myself so far
|| [[#tApr 01 12:06:52|Apr 01 12:06]]
|- id="tApr 01 12:07:49"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | well, first things - review last week's minutes/actions
|| [[#tApr 01 12:07:49|Apr 01 12:07]]
|- id="tApr 01 12:07:58"
| colspan="2" | --- | wwoods has changed the topic to: Fedora QA Meeting | review
|| [[#tApr 01 12:07:58|Apr 01 12:07]]
|- id="tApr 01 12:08:52"
| colspan="2" | * | wwoods trying to find the log
|| [[#tApr 01 12:08:52|Apr 01 12:08]]
|- id="tApr 01 12:09:00"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | https://www.redhat.com/archives/fedora-test-list/2009-March/msg01142.html
|| [[#tApr 01 12:09:00|Apr 01 12:09]]
|- id="tApr 01 12:09:01"
| colspan="2" | * | viking_ice does yet another manual install test of beta..
|| [[#tApr 01 12:09:01|Apr 01 12:09]]
|- id="tApr 01 12:09:06"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | [[QA/Meetings/20090325]]
|| [[#tApr 01 12:09:06|Apr 01 12:09]]
|- id="tApr 01 12:09:25"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | first - mediawiki plugin fun. any updates?
|| [[#tApr 01 12:09:25|Apr 01 12:09]]
|- id="tApr 01 12:10:04"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | wwoods: no updates there I'm afraid.  tibbs|h posted an update in the mediawiki-semantic-forms review with some additional licensing concerns
|| [[#tApr 01 12:10:04|Apr 01 12:10]]
|- id="tApr 01 12:10:15"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | I need to follow-up on that and then continue with the review for that package
|| [[#tApr 01 12:10:15|Apr 01 12:10]]
|- id="tApr 01 12:11:24"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | I'll follow-up with the infrastructure guys to get a live dump of the database ... it was requested that we hold off on that until post-beta
|| [[#tApr 01 12:11:24|Apr 01 12:11]]
|- id="tApr 01 12:12:31"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | 'kay
|| [[#tApr 01 12:12:31|Apr 01 12:12]]
|- id="tApr 01 12:12:33"
! style="background-color: #818144" | adamw
| style="color: #818144" | | nothing further from me there either
|| [[#tApr 01 12:12:33|Apr 01 12:12]]
|- id="tApr 01 12:12:34"
! style="background-color: #488888" | f13
| style="color: #488888" | | I'm here, sorry for the delay
|| [[#tApr 01 12:12:34|Apr 01 12:12]]
|- id="tApr 01 12:12:41"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | f13: no worries
|| [[#tApr 01 12:12:41|Apr 01 12:12]]
|- id="tApr 01 12:12:47"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | next, radeon test day. it's happening RIGHT NOW OMG
|| [[#tApr 01 12:12:47|Apr 01 12:12]]
|- id="tApr 01 12:13:36"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | next, open installer bugs -&gt; F11Beta. Well, Beta's out, so we don't need to worry about maintaining that as much
|| [[#tApr 01 12:13:36|Apr 01 12:13]]
|- id="tApr 01 12:13:55"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | we *do* need to be sure that F11Beta blocks F11Blocker so we get those weeded out for Final.
|| [[#tApr 01 12:13:55|Apr 01 12:13]]
|- id="tApr 01 12:14:08"
| colspan="2" | --- | stickster is now known as stickster_afk
|| [[#tApr 01 12:14:08|Apr 01 12:14]]
|- id="tApr 01 12:14:08"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | we spent some time on that Friday ... and a few more additions this week
|| [[#tApr 01 12:14:08|Apr 01 12:14]]
|- id="tApr 01 12:14:10"
| colspan="2" | &lt;-- | mcepl [n=mcepl@49-117-207-85.strcechy.adsl-llu.static.bluetone.cz] has left #fedora-meeting ( )
|| [[#tApr 01 12:14:10|Apr 01 12:14]]
|- id="tApr 01 12:14:21"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | specifically ... [[Fedora_11_Beta_release_notes#Anaconda_installer_issues]]
|| [[#tApr 01 12:14:21|Apr 01 12:14]]
|- id="tApr 01 12:14:45"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | next was adding stuff to the test result template
|| [[#tApr 01 12:14:45|Apr 01 12:14]]
|- id="tApr 01 12:15:02"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | I haven't added upgrade cases. jlaska, anything from the Beta page you need to add back to the template?
|| [[#tApr 01 12:15:02|Apr 01 12:15]]
|- id="tApr 01 12:15:14"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | I took that action item from last week ... but with help from wwoods, I've carried my changes from the Beta wiki into the template
|| [[#tApr 01 12:15:14|Apr 01 12:15]]
|- id="tApr 01 12:16:07"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | next was adding known install/upgrade issues to the release notes
|| [[#tApr 01 12:16:07|Apr 01 12:16]]
|- id="tApr 01 12:16:16"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | jlaska already covered that
|| [[#tApr 01 12:16:16|Apr 01 12:16]]
|- id="tApr 01 12:16:35"
! style="background-color: #818144" | adamw
| style="color: #818144" | | how about the thing about live CD -&gt; usb creation
|| [[#tApr 01 12:16:35|Apr 01 12:16]]
|- id="tApr 01 12:16:48"
! style="background-color: #42427e" | viking_ice
| style="color: #42427e" | | that should really be fixed..
|| [[#tApr 01 12:16:48|Apr 01 12:16]]
|- id="tApr 01 12:16:51"
! style="background-color: #42427e" | viking_ice
| style="color: #42427e" | | asap
|| [[#tApr 01 12:16:51|Apr 01 12:16]]
|- id="tApr 01 12:17:06"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | everything I'm aware of wrt. upgrades is already in the release notes
|| [[#tApr 01 12:17:06|Apr 01 12:17]]
|- id="tApr 01 12:17:16"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | wwoods: we have the blurb about preupgrade iirc
|| [[#tApr 01 12:17:16|Apr 01 12:17]]
|- id="tApr 01 12:17:21"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | yeah, someone should add a release note about doing livecd-iso-to-disk
|| [[#tApr 01 12:17:21|Apr 01 12:17]]
|- id="tApr 01 12:17:27"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | jlaska: right
|| [[#tApr 01 12:17:27|Apr 01 12:17]]
|- id="tApr 01 12:17:39"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | "Upgrading to Fedora 11 Beta from Fedora 10 using preupgrade will fail"
|| [[#tApr 01 12:17:39|Apr 01 12:17]]
|- id="tApr 01 12:17:41"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | pretty clear
|| [[#tApr 01 12:17:41|Apr 01 12:17]]
|- id="tApr 01 12:17:46"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | what's the release note around livecd-iso-to-disk ... the syslinux issue?
|| [[#tApr 01 12:17:46|Apr 01 12:17]]
|- id="tApr 01 12:18:05"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | yeah - it won't boot if you create it in F10 or earlier
|| [[#tApr 01 12:18:05|Apr 01 12:18]]
|- id="tApr 01 12:18:05"
! style="background-color: #818144" | adamw
| style="color: #818144" | | yep
|| [[#tApr 01 12:18:05|Apr 01 12:18]]
|- id="tApr 01 12:18:12"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | installing new syslinux is a workaround
|| [[#tApr 01 12:18:12|Apr 01 12:18]]
|- id="tApr 01 12:18:16"
! style="background-color: #818144" | adamw
| style="color: #818144" | | for now a note to upgrade syslinux from rawhide
|| [[#tApr 01 12:18:16|Apr 01 12:18]]
|- id="tApr 01 12:18:22"
! style="background-color: #818144" | adamw
| style="color: #818144" | | probably we should ship a syslinux upgrade for f10 or something
|| [[#tApr 01 12:18:22|Apr 01 12:18]]
|- id="tApr 01 12:18:28"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | indeed
|| [[#tApr 01 12:18:28|Apr 01 12:18]]
|- id="tApr 01 12:18:46"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | is there a bz on this against F10?
|| [[#tApr 01 12:18:46|Apr 01 12:18]]
|- id="tApr 01 12:19:30"
! style="background-color: #818144" | adamw
| style="color: #818144" | | not sure, i can file one if needed
|| [[#tApr 01 12:19:30|Apr 01 12:19]]
|- id="tApr 01 12:20:43"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | looks like spot, f13, and jeremy are the most recent folks to touch syslinux in f11
|| [[#tApr 01 12:20:43|Apr 01 12:20]]
|- id="tApr 01 12:21:40"
! style="background-color: #488888" | f13
| style="color: #488888" | | only by accident (:
|| [[#tApr 01 12:21:40|Apr 01 12:21]]
|- id="tApr 01 12:21:43"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | f13: do you know what would be in the way of buildinga new syslinux package for F10 that lets testers use F10 livecd-iso-to-disk with Rawhide images?
|| [[#tApr 01 12:21:43|Apr 01 12:21]]
|- id="tApr 01 12:21:54"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | f13: heh, yeah I know what you mean ;)
|| [[#tApr 01 12:21:54|Apr 01 12:21]]
|- id="tApr 01 12:22:55"
! style="background-color: #488888" | f13
| style="color: #488888" | | I don't now of anything standing in the way
|| [[#tApr 01 12:22:55|Apr 01 12:22]]
|- id="tApr 01 12:23:00"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | okay
|| [[#tApr 01 12:23:00|Apr 01 12:23]]
|- id="tApr 01 12:23:02"
! style="background-color: #488888" | f13
| style="color: #488888" | | but I'm not really familiar with the package itself.
|| [[#tApr 01 12:23:02|Apr 01 12:23]]
|- id="tApr 01 12:23:19"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | f13: would spot or jeremy be good contacts?
|| [[#tApr 01 12:23:19|Apr 01 12:23]]
|- id="tApr 01 12:23:34"
! style="background-color: #488888" | f13
| style="color: #488888" | | more like peter or jeremy
|| [[#tApr 01 12:23:34|Apr 01 12:23]]
|- id="tApr 01 12:23:45"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | okay
|| [[#tApr 01 12:23:45|Apr 01 12:23]]
|- id="tApr 01 12:24:09"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | adamw: would you mind getting a bz in for that?
|| [[#tApr 01 12:24:09|Apr 01 12:24]]
|- id="tApr 01 12:24:16"
! style="background-color: #818144" | adamw
| style="color: #818144" | | will do
|| [[#tApr 01 12:24:16|Apr 01 12:24]]
|- id="tApr 01 12:24:52"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | we'll get that bug id into the release notes, document the workaround, and talk to pjones/jeremy about updating F10 (and F9?) syslinux to fix the bug
|| [[#tApr 01 12:24:52|Apr 01 12:24]]
|- id="tApr 01 12:24:57"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | that should cover it
|| [[#tApr 01 12:24:57|Apr 01 12:24]]
|- id="tApr 01 12:25:25"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | finally, the review meeting happened and we pushed the big green button
|| [[#tApr 01 12:25:25|Apr 01 12:25]]
|- id="tApr 01 12:25:30"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | Beta went out, hurrah.
|| [[#tApr 01 12:25:30|Apr 01 12:25]]
|- id="tApr 01 12:25:53"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | wwoods/f13: did you guys also want to do an update on autoqa?
|| [[#tApr 01 12:25:53|Apr 01 12:25]]
|- id="tApr 01 12:26:02"
| colspan="2" | * | jlaska looking over previous minutes
|| [[#tApr 01 12:26:02|Apr 01 12:26]]
|- id="tApr 01 12:26:09"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | oh, sure
|| [[#tApr 01 12:26:09|Apr 01 12:26]]
|- id="tApr 01 12:26:11"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | let's do that
|| [[#tApr 01 12:26:11|Apr 01 12:26]]
|- id="tApr 01 12:26:13"
! style="background-color: #488888" | f13
| style="color: #488888" | | I haven't touched it since the beta rush, looking forward to touching it today
|| [[#tApr 01 12:26:13|Apr 01 12:26]]
|- id="tApr 01 12:26:17"
| colspan="2" | --- | wwoods has changed the topic to: Fedora QA Meeting | autoqa
|| [[#tApr 01 12:26:17|Apr 01 12:26]]
|- id="tApr 01 12:26:21"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | yeah, I poked at it yesterday
|| [[#tApr 01 12:26:21|Apr 01 12:26]]
|- id="tApr 01 12:26:29"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | and checked in an initial verifytree test case
|| [[#tApr 01 12:26:29|Apr 01 12:26]]
|- id="tApr 01 12:26:56"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | we don't have a watcher for post-tree-compose, but we have one test case for it
|| [[#tApr 01 12:26:56|Apr 01 12:26]]
|- id="tApr 01 12:26:59"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | heh
|| [[#tApr 01 12:26:59|Apr 01 12:26]]
|- id="tApr 01 12:27:11"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | is this something one can run manually now?
|| [[#tApr 01 12:27:11|Apr 01 12:27]]
|- id="tApr 01 12:27:14"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | I'm going to need to work on making tests interdependent, so we can stop testing if verifytree fails
|| [[#tApr 01 12:27:14|Apr 01 12:27]]
|- id="tApr 01 12:27:33"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | but the next thing to do would be some qemu-based boot smoketest
|| [[#tApr 01 12:27:33|Apr 01 12:27]]
|- id="tApr 01 12:27:40"
! style="background-color: #488888" | f13
| style="color: #488888" | | I'm hoping to make a watcher for post-tree-compose
|| [[#tApr 01 12:27:40|Apr 01 12:27]]
|- id="tApr 01 12:27:46"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | (i.e. the lab-in-a-box stuff we talked about at FUDCon)
|| [[#tApr 01 12:27:46|Apr 01 12:27]]
|- id="tApr 01 12:28:27"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | jlaska: sure, but you need to install autoqa and have a tree available at a local path
|| [[#tApr 01 12:28:27|Apr 01 12:28]]
|- id="tApr 01 12:28:38"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | "install" ... from a git checkout?
|| [[#tApr 01 12:28:38|Apr 01 12:28]]
|- id="tApr 01 12:28:48"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | yeah. git clone and make install
|| [[#tApr 01 12:28:48|Apr 01 12:28]]
|- id="tApr 01 12:29:34"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | cool, what are the tests that you guys have now?
|| [[#tApr 01 12:29:34|Apr 01 12:29]]
|- id="tApr 01 12:30:04"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | at the moment there's two hooks - post-repo-update and post-tree-compose
|| [[#tApr 01 12:30:04|Apr 01 12:30]]
|- id="tApr 01 12:30:20"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | each has one test - repoclosure and verifytree, respectively
|| [[#tApr 01 12:30:20|Apr 01 12:30]]
|- id="tApr 01 12:30:49"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | very nice
|| [[#tApr 01 12:30:49|Apr 01 12:30]]
|- id="tApr 01 12:31:25"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | okay, is there anything you guys want to check-in on next week wrt autoqa ... or should we just leave as a general update again?
|| [[#tApr 01 12:31:25|Apr 01 12:31]]
|- id="tApr 01 12:31:54"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | general update should be fine - with a little luck we should able to be running both hooks regularly by next week
|| [[#tApr 01 12:31:54|Apr 01 12:31]]
|- id="tApr 01 12:31:57"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | but don't hold me to that
|| [[#tApr 01 12:31:57|Apr 01 12:31]]
|- id="tApr 01 12:32:10"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | what if we just focus on repoclosure?
|| [[#tApr 01 12:32:10|Apr 01 12:32]]
|- id="tApr 01 12:32:17"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | getting feature parity with the emails that go out now?
|| [[#tApr 01 12:32:17|Apr 01 12:32]]
|- id="tApr 01 12:32:26"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | is that easier/harder/interesting?
|| [[#tApr 01 12:32:26|Apr 01 12:32]]
|- id="tApr 01 12:32:37"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | f13: didn't we have that running on a host somewhere?
|| [[#tApr 01 12:32:37|Apr 01 12:32]]
|- id="tApr 01 12:32:59"
! style="background-color: #488888" | f13
| style="color: #488888" | | qa1
|| [[#tApr 01 12:32:59|Apr 01 12:32]]
|- id="tApr 01 12:33:08"
! style="background-color: #488888" | f13
| style="color: #488888" | | its a tad... verbose
|| [[#tApr 01 12:33:08|Apr 01 12:33]]
|- id="tApr 01 12:33:26"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | would it be easier to focus on ironing out the quirks with tests that don't require installs just yet
|| [[#tApr 01 12:33:26|Apr 01 12:33]]
|- id="tApr 01 12:33:29"
! style="background-color: #488888" | f13
| style="color: #488888" | | we may want to re-think how it works.
|| [[#tApr 01 12:33:29|Apr 01 12:33]]
|- id="tApr 01 12:33:35"
! style="background-color: #488888" | f13
| style="color: #488888" | | combining output into single mails or not
|| [[#tApr 01 12:33:35|Apr 01 12:33]]
|- id="tApr 01 12:34:00"
! style="background-color: #488888" | f13
| style="color: #488888" | | yeah, I think willl and I could focus on the tree based tests
|| [[#tApr 01 12:34:00|Apr 01 12:34]]
|- id="tApr 01 12:34:01"
| colspan="2" | * | jlaska suspects that adding cobbler/kvm/lab-in-a-box to the mix won't make things tremendously easier
|| [[#tApr 01 12:34:01|Apr 01 12:34]]
|- id="tApr 01 12:34:07"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | right
|| [[#tApr 01 12:34:07|Apr 01 12:34]]
|- id="tApr 01 12:34:09"
! style="background-color: #488888" | f13
| style="color: #488888" | | in parallel with lab-in-a-box work
|| [[#tApr 01 12:34:09|Apr 01 12:34]]
|- id="tApr 01 12:34:31"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | I'd really like to plug in the lab-in-a-box stuff to what you guys are doing ... but there are a few "missing links" for me right now
|| [[#tApr 01 12:34:31|Apr 01 12:34]]
|- id="tApr 01 12:34:55"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | well, we're designing the test system around the tests we have available
|| [[#tApr 01 12:34:55|Apr 01 12:34]]
|- id="tApr 01 12:35:16"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | so you can't design the tests around the test system
|| [[#tApr 01 12:35:16|Apr 01 12:35]]
|- id="tApr 01 12:35:30"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | or else: infinite recursion
|| [[#tApr 01 12:35:30|Apr 01 12:35]]
|- id="tApr 01 12:35:47"
| colspan="2" | * | jlaska is convinced life is about infinite recursion
|| [[#tApr 01 12:35:47|Apr 01 12:35]]
|- id="tApr 01 12:36:11"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | wwoods: yeah I see what you're saying ... I'll try to get in the loop with you guys to see how I can wedge what I've got into your framework
|| [[#tApr 01 12:36:11|Apr 01 12:36]]
|- id="tApr 01 12:36:12"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | yeah, I'm joking, that'll work fine
|| [[#tApr 01 12:36:12|Apr 01 12:36]]
|- id="tApr 01 12:36:37"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | but I'll need to talk to you about how we can make sure the autoqa stuff can launch (and process the results of) lab-in-a-box tests
|| [[#tApr 01 12:36:37|Apr 01 12:36]]
|- id="tApr 01 12:36:51"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | we don't need to set that up, just need to make sure the framework can handle it
|| [[#tApr 01 12:36:51|Apr 01 12:36]]
|- id="tApr 01 12:36:55"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | wwoods: okay, I see a sync-up with us in the week :)
|| [[#tApr 01 12:36:55|Apr 01 12:36]]
|- id="tApr 01 12:36:56"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | yeah
|| [[#tApr 01 12:36:56|Apr 01 12:36]]
|- id="tApr 01 12:37:00"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | cool, nice work guys!
|| [[#tApr 01 12:37:00|Apr 01 12:37]]
|- id="tApr 01 12:37:17"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | but figuring out better reporting for the existing tests is the first thing on the agenda for me
|| [[#tApr 01 12:37:17|Apr 01 12:37]]
|- id="tApr 01 12:37:35"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | and I think f13 will be assisting with that and working on a monitor script for post-tree-compose
|| [[#tApr 01 12:37:35|Apr 01 12:37]]
|- id="tApr 01 12:37:45"
| colspan="2" | * | wwoods worries about re-inventing gridtrees.py
|| [[#tApr 01 12:37:45|Apr 01 12:37]]
|- id="tApr 01 12:38:02"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | meh, if it works ... who cares what it looks like for now :)
|| [[#tApr 01 12:38:02|Apr 01 12:38]]
|- id="tApr 01 12:38:15"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | just call it gridtrees2.py
|| [[#tApr 01 12:38:15|Apr 01 12:38]]
|- id="tApr 01 12:38:18"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | :D
|| [[#tApr 01 12:38:18|Apr 01 12:38]]
|- id="tApr 01 12:38:24"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | yeah, but we have to learn from our (old, non-public) mistakes
|| [[#tApr 01 12:38:24|Apr 01 12:38]]
|- id="tApr 01 12:38:33"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | definitely!
|| [[#tApr 01 12:38:33|Apr 01 12:38]]
|- id="tApr 01 12:39:06"
! style="background-color: #42427e" | viking_ice
| style="color: #42427e" | | for the record the lab-in-the-box some thing that the end user execute or is the plan to being able to remotely execute the tests
|| [[#tApr 01 12:39:06|Apr 01 12:39]]
|- id="tApr 01 12:39:32"
! style="background-color: #42427e" | viking_ice
| style="color: #42427e" | | ( basically just leaving the end user up to supplying hw )
|| [[#tApr 01 12:39:32|Apr 01 12:39]]
|- id="tApr 01 12:39:32"
! style="background-color: #488888" | f13
| style="color: #488888" | | we won't be watching a .py file to be updated, we'll watch a path (:
|| [[#tApr 01 12:39:32|Apr 01 12:39]]
|- id="tApr 01 12:39:47"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | viking_ice: wwoods or f13 can correct me, but my thinking was the same stuff we'd run in an automated fashion, could be installed and run by users
|| [[#tApr 01 12:39:47|Apr 01 12:39]]
|- id="tApr 01 12:40:00"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | viking_ice: the idea is that the lab-in-a-box stuff should allow automated install testing on any machine capable of virtualization
|| [[#tApr 01 12:40:00|Apr 01 12:40]]
|- id="tApr 01 12:40:13"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | f13: haha :)
|| [[#tApr 01 12:40:13|Apr 01 12:40]]
|- id="tApr 01 12:40:17"
! style="background-color: #42427e" | viking_ice
| style="color: #42427e" | | and the test que.. setup..
|| [[#tApr 01 12:40:17|Apr 01 12:40]]
|- id="tApr 01 12:40:30"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | right - so users could run it, but we'll be most interested in having it running somewhere inside the fedora infrastructure - or at someone's desk
|| [[#tApr 01 12:40:30|Apr 01 12:40]]
|- id="tApr 01 12:40:47"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | whatever, so long as we get testing
|| [[#tApr 01 12:40:47|Apr 01 12:40]]
|- id="tApr 01 12:40:49"
! style="background-color: #42427e" | viking_ice
| style="color: #42427e" | | as in the user fetches test cases ( kickstarts file etc ) and executes them..
|| [[#tApr 01 12:40:49|Apr 01 12:40]]
|- id="tApr 01 12:41:00"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | viking_ice: that's a great plan for the future
|| [[#tApr 01 12:41:00|Apr 01 12:41]]
|- id="tApr 01 12:41:35"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | we're not there yet, though
|| [[#tApr 01 12:41:35|Apr 01 12:41]]
|- id="tApr 01 12:42:09"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | but yeah, that's a good plan for the future stuff
|| [[#tApr 01 12:42:09|Apr 01 12:42]]
|- id="tApr 01 12:42:36"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | the only other thing I had on my mind was the schedule proposal I mentioned last week
|| [[#tApr 01 12:42:36|Apr 01 12:42]]
|- id="tApr 01 12:43:01"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | I did some research and talked to people and did some planning and whatnot and decided.. it's probably not worth the effort
|| [[#tApr 01 12:43:01|Apr 01 12:43]]
|- id="tApr 01 12:43:38"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | It'd be much better spent on the stuff we've already got planned - better tools for testing and reporting, so we can do more efficient testing
|| [[#tApr 01 12:43:38|Apr 01 12:43]]
|- id="tApr 01 12:44:05"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | at least that's how I see it for the near future.
|| [[#tApr 01 12:44:05|Apr 01 12:44]]
|- id="tApr 01 12:44:39"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | so that idea is on Indefinite Hold.
|| [[#tApr 01 12:44:39|Apr 01 12:44]]
|- id="tApr 01 12:45:03"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | okay. what else do we need to discuss?
|| [[#tApr 01 12:45:03|Apr 01 12:45]]
|- id="tApr 01 12:45:15"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | can  I touch on something adamw raised last week?
|| [[#tApr 01 12:45:15|Apr 01 12:45]]
|- id="tApr 01 12:45:44"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | we're sort of discussed it already, so I don't want to spend a lot of time ... but adamw hilighted that we might not be communicating the known issues effectively
|| [[#tApr 01 12:45:44|Apr 01 12:45]]
|- id="tApr 01 12:46:06"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | from ... [[QA/Meetings/20090325#Building_the_Beta_Known_issues]]
|| [[#tApr 01 12:46:06|Apr 01 12:46]]
|- id="tApr 01 12:46:30"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | we spent some time building out the known issues list ... are we happy with the result?
|| [[#tApr 01 12:46:30|Apr 01 12:46]]
|- id="tApr 01 12:46:42"
! style="background-color: #818144" | adamw
| style="color: #818144" | | linky?
|| [[#tApr 01 12:46:42|Apr 01 12:46]]
|- id="tApr 01 12:46:44"
| colspan="2" | --- | wwoods has changed the topic to: Fedora QA Meeting | Known issues
|| [[#tApr 01 12:46:44|Apr 01 12:46]]
|- id="tApr 01 12:46:48"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | does the consensus from last week still hold?
|| [[#tApr 01 12:46:48|Apr 01 12:46]]
|- id="tApr 01 12:46:57"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | known issues - [[Fedora_11_Beta_release_notes#Anaconda_installer_issues]]
|| [[#tApr 01 12:46:57|Apr 01 12:46]]
|- id="tApr 01 12:47:02"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | [[Fedora_11_Beta_release_notes#Known_Issues]]
|| [[#tApr 01 12:47:02|Apr 01 12:47]]
|- id="tApr 01 12:47:05"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | out consensus from last week - [[QA/Meetings/20090325#Building_the_Beta_Known_issues]]
|| [[#tApr 01 12:47:05|Apr 01 12:47]]
|- id="tApr 01 12:47:14"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | Consensus was ... "#  Result - QA team must internally reference the Beta release notes known issues in all IRC and email communication. "
|| [[#tApr 01 12:47:14|Apr 01 12:47]]
|- id="tApr 01 12:47:20"
| colspan="2" | --- | dwmw2 is now known as dwmw2_gone
|| [[#tApr 01 12:47:20|Apr 01 12:47]]
|- id="tApr 01 12:47:27"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | it's early still ... but "how's our driving"?
|| [[#tApr 01 12:47:27|Apr 01 12:47]]
|- id="tApr 01 12:48:11"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | seems pretty good, anecdotally at least - everyone I've asked about bugs has said things like "I didn't see that in the release notes, so ..."
|| [[#tApr 01 12:48:11|Apr 01 12:48]]
|- id="tApr 01 12:48:17"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | i.e. it seems like people are reading 'em
|| [[#tApr 01 12:48:17|Apr 01 12:48]]
|- id="tApr 01 12:48:32"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | how much longer do we spend adding issues to the list ... a few things came up today
|| [[#tApr 01 12:48:32|Apr 01 12:48]]
|- id="tApr 01 12:48:35"
! style="background-color: #818144" | adamw
| style="color: #818144" | | the public announcements i've seen at least referenced the release notes
|| [[#tApr 01 12:48:35|Apr 01 12:48]]
|- id="tApr 01 12:48:35"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | mainly syslinux I guess
|| [[#tApr 01 12:48:35|Apr 01 12:48]]
|- id="tApr 01 12:48:36"
! style="background-color: #818144" | adamw
| style="color: #818144" | | e.g. http://www.osnews.com/story/21232/Fedora_11_Beta_Released
|| [[#tApr 01 12:48:36|Apr 01 12:48]]
|- id="tApr 01 12:49:06"
! style="background-color: #818144" | adamw
| style="color: #818144" | | it doesn't specifically link to the known issues as we discussed, though
|| [[#tApr 01 12:49:06|Apr 01 12:49]]
|- id="tApr 01 12:49:16"
! style="background-color: #818144" | adamw
| style="color: #818144" | | perhaps i could poke rahul and suggest that to him for future release announcements
|| [[#tApr 01 12:49:16|Apr 01 12:49]]
|- id="tApr 01 12:49:22"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | also on this topic: so warren started up a blog for rawhide issues: http://rawhidewatch.wordpress.com/
|| [[#tApr 01 12:49:22|Apr 01 12:49]]
|- id="tApr 01 12:49:30"
! style="background-color: #818144" | adamw
| style="color: #818144" | | oh, yes, that's an AWESOME idea
|| [[#tApr 01 12:49:30|Apr 01 12:49]]
|- id="tApr 01 12:49:33"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | ++
|| [[#tApr 01 12:49:33|Apr 01 12:49]]
|- id="tApr 01 12:50:01"
! style="background-color: #488888" | f13
| style="color: #488888" | | I've lost my right click...
|| [[#tApr 01 12:50:01|Apr 01 12:50]]
|- id="tApr 01 12:50:25"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | we should coordinate with him - either send him updates, or see if he needs/wants help maintaining it
|| [[#tApr 01 12:50:25|Apr 01 12:50]]
|- id="tApr 01 12:50:29"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | it's already on fedora planet, which is great
|| [[#tApr 01 12:50:29|Apr 01 12:50]]
|- id="tApr 01 12:50:39"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | we might want to get it into the default bookmarks, at least for prereleases
|| [[#tApr 01 12:50:39|Apr 01 12:50]]
|- id="tApr 01 12:51:34"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | (he's not on IRC right now or I'd just bring him in so we can talk about it)
|| [[#tApr 01 12:51:34|Apr 01 12:51]]
|- id="tApr 01 12:51:54"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | that's a really good idea, perhaps checking in with him on how we can add issues to his list?
|| [[#tApr 01 12:51:54|Apr 01 12:51]]
|- id="tApr 01 12:53:00"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | yeah, the first post sez "Please submit notable news to Warren Togami and it may appear here."
|| [[#tApr 01 12:53:00|Apr 01 12:53]]
|- id="tApr 01 12:53:17"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | and there we have it
|| [[#tApr 01 12:53:17|Apr 01 12:53]]
|- id="tApr 01 12:53:32"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | for the moment let's try to ping him on IRC (or, failing that, email him) with notable rawhide stuff
|| [[#tApr 01 12:53:32|Apr 01 12:53]]
|- id="tApr 01 12:53:51"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | I'll talk to him about whether he wants/needs help from QA maintaining that page
|| [[#tApr 01 12:53:51|Apr 01 12:53]]
|- id="tApr 01 12:53:56"
! style="background-color: #8c4a4a" | skvidal
| style="color: #8c4a4a" | | or ask him if he can add poster to it
|| [[#tApr 01 12:53:56|Apr 01 12:53]]
|- id="tApr 01 12:54:07"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | skvidal: so others can contribute you mean?
|| [[#tApr 01 12:54:07|Apr 01 12:54]]
|- id="tApr 01 12:54:18"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | skvidal: right. also I hear rumors that the infrastructure team might be thinking about setting up wordpress for fedora
|| [[#tApr 01 12:54:18|Apr 01 12:54]]
|- id="tApr 01 12:54:32"
! style="background-color: #8c4a4a" | skvidal
| style="color: #8c4a4a" | | jlaska: yes
|| [[#tApr 01 12:54:32|Apr 01 12:54]]
|- id="tApr 01 12:54:41"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | skvidal: roger
|| [[#tApr 01 12:54:41|Apr 01 12:54]]
|- id="tApr 01 12:54:42"
! style="background-color: #8c4a4a" | skvidal
| style="color: #8c4a4a" | | wwoods: yah - not sure of the last status on that, though
|| [[#tApr 01 12:54:42|Apr 01 12:54]]
|- id="tApr 01 12:54:48"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | so we might want a plan to migrate over.. so it might be prudent to figure that out before we go putting this link all over the place
|| [[#tApr 01 12:54:48|Apr 01 12:54]]
|- id="tApr 01 12:55:04"
! style="background-color: #8c4a4a" | skvidal
| style="color: #8c4a4a" | | which is why having it on the planet is fine
|| [[#tApr 01 12:55:04|Apr 01 12:55]]
|- id="tApr 01 12:55:14"
! style="background-color: #8c4a4a" | skvidal
| style="color: #8c4a4a" | | or ask infrastructure to setup a redirect
|| [[#tApr 01 12:55:14|Apr 01 12:55]]
|- id="tApr 01 12:55:22"
! style="background-color: #8c4a4a" | skvidal
| style="color: #8c4a4a" | | rawhidebabyeating.fedoraproject.org
|| [[#tApr 01 12:55:22|Apr 01 12:55]]
|- id="tApr 01 12:55:38"
! style="background-color: #8c4a4a" | skvidal
| style="color: #8c4a4a" | | nomnombabies.fedoraproject.org
|| [[#tApr 01 12:55:38|Apr 01 12:55]]
|- id="tApr 01 12:55:53"
! style="background-color: #8c4a4a" | skvidal
| style="color: #8c4a4a" | | then you can give out that address
|| [[#tApr 01 12:55:53|Apr 01 12:55]]
|- id="tApr 01 12:55:56"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | does someone want to checkin with warren before next meeting just to see what his plans were and if/how we can engage?
|| [[#tApr 01 12:55:56|Apr 01 12:55]]
|- id="tApr 01 12:56:00"
! style="background-color: #8c4a4a" | skvidal
| style="color: #8c4a4a" | | and when/if it moves...
|| [[#tApr 01 12:56:00|Apr 01 12:56]]
|- id="tApr 01 12:57:47"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | I don't mind chatting with Warren if there are no takers
|| [[#tApr 01 12:57:47|Apr 01 12:57]]
|- id="tApr 01 12:58:32"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | and he arrives!
|| [[#tApr 01 12:58:32|Apr 01 12:58]]
|- id="tApr 01 12:59:06"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | wwoods: adamw: viking_ice: f13: any other discussion topics ... or should we start wrapping up?
|| [[#tApr 01 12:59:06|Apr 01 12:59]]
|- id="tApr 01 12:59:18"
! style="background-color: #818144" | adamw
| style="color: #818144" | | just to note that infrastructure is working on my calendaring proposal
|| [[#tApr 01 12:59:18|Apr 01 12:59]]
|- id="tApr 01 12:59:25"
! style="background-color: #488888" | f13
| style="color: #488888" | | not much, just a lot of catch up to do post-bet arush
|| [[#tApr 01 12:59:25|Apr 01 12:59]]
|- id="tApr 01 12:59:27"
! style="background-color: #818144" | adamw
| style="color: #818144" | | sounds like they're about to come up with a system that would do the job right
|| [[#tApr 01 12:59:27|Apr 01 12:59]]
|- id="tApr 01 12:59:31"
! style="background-color: #42427e" | viking_ice
| style="color: #42427e" | | sorry was away speaking to the dbadmin
|| [[#tApr 01 12:59:31|Apr 01 12:59]]
|- id="tApr 01 12:59:35"
! style="background-color: #818144" | adamw
| style="color: #818144" | | keep an eye on posts from susmit on infrastructure-list if you're interested
|| [[#tApr 01 12:59:35|Apr 01 12:59]]
|- id="tApr 01 12:59:49"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | adamw: I saw that ... sounds like 2 candidates being reviewed?
|| [[#tApr 01 12:59:49|Apr 01 12:59]]
|- id="tApr 01 13:00:07"
! style="background-color: #818144" | adamw
| style="color: #818144" | | jlaska: it's moved on from there, neither of those did caldav, but susmit now says he's thought up a system which would work out
|| [[#tApr 01 13:00:07|Apr 01 13:00]]
|- id="tApr 01 13:00:13"
! style="background-color: #818144" | adamw
| style="color: #818144" | | combination of zicula and phpical
|| [[#tApr 01 13:00:13|Apr 01 13:00]]
|- id="tApr 01 13:00:38"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | adamw: very nice, thank you for following that
|| [[#tApr 01 13:00:38|Apr 01 13:00]]
|- id="tApr 01 13:01:53"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | wwoods: any other topics on your end?
|| [[#tApr 01 13:01:53|Apr 01 13:01]]
|- id="tApr 01 13:02:10"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | none from me. jlaska, if you want to be the official Warren Liason then we'll review that next week
|| [[#tApr 01 13:02:10|Apr 01 13:02]]
|- id="tApr 01 13:02:22"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | so let's try to sum up the actions planned:
|| [[#tApr 01 13:02:22|Apr 01 13:02]]
|- id="tApr 01 13:02:29"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | wwoods: will do
|| [[#tApr 01 13:02:29|Apr 01 13:02]]
|- id="tApr 01 13:03:06"
! style="background-color: #4b904b" | warren
| style="color: #4b904b" | | huh?
|| [[#tApr 01 13:03:06|Apr 01 13:03]]
|- id="tApr 01 13:03:07"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | [wwoods] autoqa: work on better (clearer) reporting from existing tests
|| [[#tApr 01 13:03:07|Apr 01 13:03]]
|- id="tApr 01 13:03:14"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | (test, really: just repoclosure atm)
|| [[#tApr 01 13:03:14|Apr 01 13:03]]
|- id="tApr 01 13:03:24"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | err, oops
|| [[#tApr 01 13:03:24|Apr 01 13:03]]
|- id="tApr 01 13:03:27"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | warren: I'll catch up with you later with some questions on your rawhidewatch blog
|| [[#tApr 01 13:03:27|Apr 01 13:03]]
|- id="tApr 01 13:03:35"
| colspan="2" | --- | wwoods has changed the topic to: Fedora QA | Action summary!
|| [[#tApr 01 13:03:35|Apr 01 13:03]]
|- id="tApr 01 13:03:52"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | [f13] autoqa: work on monitor for post-tree-compose
|| [[#tApr 01 13:03:52|Apr 01 13:03]]
|- id="tApr 01 13:04:15"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | [wwoods, jlaska] autoqa: discuss lab-in-a-box integration
|| [[#tApr 01 13:04:15|Apr 01 13:04]]
|- id="tApr 01 13:05:00"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | [jlaska] talk to warren and see if he needs/wants help with http://rawhidewatch.wordpress.com/
|| [[#tApr 01 13:05:00|Apr 01 13:05]]
|- id="tApr 01 13:05:09"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | that's all I can remember off the top of me head
|| [[#tApr 01 13:05:09|Apr 01 13:05]]
|- id="tApr 01 13:05:12"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | [adamw] - will file a F10 bug for the syslinux issue, initiate discussion with pjones or jeremy for building a updated F10 package
|| [[#tApr 01 13:05:12|Apr 01 13:05]]
|- id="tApr 01 13:05:13"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | what else?
|| [[#tApr 01 13:05:13|Apr 01 13:05]]
|- id="tApr 01 13:05:22"
! style="background-color: #4b904b" | warren
| style="color: #4b904b" | | syslinux issue?
|| [[#tApr 01 13:05:22|Apr 01 13:05]]
|- id="tApr 01 13:05:44"
! style="background-color: #818144" | adamw
| style="color: #818144" | | warren: you can't build a usb image of the f11 beta live CDs without an updated syslinux
|| [[#tApr 01 13:05:44|Apr 01 13:05]]
|- id="tApr 01 13:06:07"
! style="background-color: #42427e" | viking_ice
| style="color: #42427e" | | so I guess if fedora is going to put up an wp instance we wont need the announcement one right?
|| [[#tApr 01 13:06:07|Apr 01 13:06]]
|- id="tApr 01 13:06:44"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | should we take the action out of meeting for syslinux?
|| [[#tApr 01 13:06:44|Apr 01 13:06]]
|- id="tApr 01 13:08:30"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | jlaska: not sure what you mean
|| [[#tApr 01 13:08:30|Apr 01 13:08]]
|- id="tApr 01 13:08:50"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | if that's all the actions we got from this meeting, let's call it done and get to work on that syslinux thing
|| [[#tApr 01 13:08:50|Apr 01 13:08]]
|- id="tApr 01 13:08:57"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | yeah that's what I wanted :)
|| [[#tApr 01 13:08:57|Apr 01 13:08]]
|- id="tApr 01 13:08:59"
! style="background-color: #818144" | adamw
| style="color: #818144" | | i'll do the bug
|| [[#tApr 01 13:08:59|Apr 01 13:08]]
|- id="tApr 01 13:09:00"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | thanks ;)
|| [[#tApr 01 13:09:00|Apr 01 13:09]]
|- id="tApr 01 13:10:14"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | | thanks wwoods, I'll post minutes to the list shortly
|| [[#tApr 01 13:10:14|Apr 01 13:10]]
|- id="tApr 01 13:10:32"
! style="background-color: #854685" | wwoods
| style="color: #854685" | | cool. thanks, all
|| [[#tApr 01 13:10:32|Apr 01 13:10]]
|- id="tApr 01 13:10:38"
| colspan="2" | --- | wwoods has changed the topic to: Channel is used by various Fedora groups and committees for their regular meetings | Note that meetings often get logged | For questions about using Fedora please ask in #fedora | See http://fedoraproject.org/wiki/Meeting_channel for meeting schedule
|| [[#tApr 01 13:10:38|Apr 01 13:10]]
|}
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 08:55, 18 September 2016

Attendees

  • Will Woods (wwoods)
  • Adam Williamson (adamw)
  • James Laska (jlaska)
  • Jóhann Guðmundsson (viking_ice)
  • Jesse Keating (f13)

Previous meeting follow-up

  • [jlaska+adamw] mediawiki semantic update (packaging and hosting)
    • REVIEWED - 490001 - Review Request: mediawiki-semantic - The semantic extension to mediawiki
    • UNDER REVIEW - 490171 - Review Request: mediawiki-semantic-forms - An extension to MediaWiki that adds support for web-based forms
      • User:tibbs posted some additional concerns for mediawiki-semantic-forms around licensing which I haven't followed up on yet
      • request infrastructure hosting
  • [f13+wwoods] - autoqa status update
    • wwoods checked in an initial verifytree test case
    • f13 hoping to make a watcher for post-tree-compose
    • Next steps ...
      1. focus on the tree based tests
      2. figuring out better reporting for the existing tests
  • [jlaska] - copy F11 beta test results wiki changes into the wiki template (several test case additions)
  • [wwoods] - to add some upgrade test cases to the beta results page (and template)
    • No upgrade cases added yet
  • [wwoods] - document any upgrade issues in the Beta release notes
    • Bug#492516 added to release notes
  • [jlaska] - setup meeting to review RC test results for Friday afternoon to include release engineering (JesseKeating) and anaconda-devel and any RC testers.

F-11-Beta - who/what/when/where/why?

The beta was released! See announcement from Jesse Keating - https://www.redhat.com/archives/fedora-test-list/2009-March/msg01262.html

Open discussion

F10 syslinux package

Adamw noted that livecd-iso-to-disk is failing on F10 systems when trying to create F11 live images. A lot of Test Day testers are writing their live images only to find the systems are not bootable due to a bug in the F10 syslinux package.

Schedule Change proposal

Wwoods provided an update on the initial schedule proposal raised in the previous meeting. After discussion and research, concluded this effort is not worth continuing. Instead, time should be spent on better tools for testing and reporting, so we can do more efficient testing.

Communication of Beta Known Issues

  • jlaska asked how well we are holding up with our conclusion from the previous week.
  • Adamw suggested that while the announcement links to the release notes, it doesn't specify the Known issues. Perhaps this could change for future milestones (check-in with Rahul)?
  • Wwoods reminded us about Warren Togami's rawhide status blog - http://rawhidewatch.wordpress.com/

Fedora Calendaring System

Adamw noted that the infrastructure team is moving closer to infrastructure hosted calendaring system. More details on fedora-infrastructure-list (https://www.redhat.com/archives/fedora-infrastructure-list/2009-March/msg00266.html).

Upcoming QA events

Action items

  • [wwoods] - autoqa: work on better (clearer) reporting from existing tests
  • [f13] - autoqa: work on monitor for post-tree-compose
  • [adamw] - will file a F10 bug for the syslinux issue, initiate discussion with pjones or jeremy for building a updated F10 package
  • [jlaska] - check-in with Warren Togami on the rawhidewatch blog ... can Fedora QA help ... what is his vision?
  • [jlaska+wwoods] - discuss integration between lab-in-a-box and autoqa

Next QA meeting

The next meeting will be held on 2009-04-08 16:00 UTC

IRC Transcript

--- | jlaska has changed the topic to: Fedora QA meeting | gathering people Apr 01 12:00
jlaska | Fedora QA meeting starting shortly, we'll get things moving shortly ... Apr 01 12:01
jlaska | show of hands if you're around Apr 01 12:02
jlaska | ping adamw: wwoods: f13: viking_ice ... and any other QA meeting attendees I've missed :) Apr 01 12:04
viking_ice | hellú.. Apr 01 12:04
jlaska | viking_ice: Ahoj :) Apr 01 12:05
adamw | yo Apr 01 12:05
jlaska | adamw: heyo! Apr 01 12:05
jlaska | wwoods: is back! Apr 01 12:06
wwoods | WITH A VENGEANCE Apr 01 12:06
wwoods | wait, no, just back Apr 01 12:06
wwoods | jlaska: you logging? Apr 01 12:06
jlaska | heh, no bruce willis please :) Apr 01 12:06
jlaska | wwoods: indeed ... go for it Apr 01 12:06
jlaska | we've got viking_ice, adamw and myself so far Apr 01 12:06
wwoods | well, first things - review last week's minutes/actions Apr 01 12:07
--- | wwoods has changed the topic to: Fedora QA Meeting | review Apr 01 12:07
* | wwoods trying to find the log Apr 01 12:08
jlaska | https://www.redhat.com/archives/fedora-test-list/2009-March/msg01142.html Apr 01 12:09
* | viking_ice does yet another manual install test of beta.. Apr 01 12:09
wwoods | QA/Meetings/20090325 Apr 01 12:09
wwoods | first - mediawiki plugin fun. any updates? Apr 01 12:09
jlaska | wwoods: no updates there I'm afraid. tibbs|h posted an update in the mediawiki-semantic-forms review with some additional licensing concerns Apr 01 12:10
jlaska | I need to follow-up on that and then continue with the review for that package Apr 01 12:10
jlaska | I'll follow-up with the infrastructure guys to get a live dump of the database ... it was requested that we hold off on that until post-beta Apr 01 12:11
wwoods | 'kay Apr 01 12:12
adamw | nothing further from me there either Apr 01 12:12
f13 | I'm here, sorry for the delay Apr 01 12:12
wwoods | f13: no worries Apr 01 12:12
wwoods | next, radeon test day. it's happening RIGHT NOW OMG Apr 01 12:12
wwoods | next, open installer bugs -> F11Beta. Well, Beta's out, so we don't need to worry about maintaining that as much Apr 01 12:13
wwoods | we *do* need to be sure that F11Beta blocks F11Blocker so we get those weeded out for Final. Apr 01 12:13
--- | stickster is now known as stickster_afk Apr 01 12:14
jlaska | we spent some time on that Friday ... and a few more additions this week Apr 01 12:14
<-- | mcepl [n=mcepl@49-117-207-85.strcechy.adsl-llu.static.bluetone.cz] has left #fedora-meeting ( ) Apr 01 12:14
jlaska | specifically ... Fedora_11_Beta_release_notes#Anaconda_installer_issues Apr 01 12:14
wwoods | next was adding stuff to the test result template Apr 01 12:14
wwoods | I haven't added upgrade cases. jlaska, anything from the Beta page you need to add back to the template? Apr 01 12:15
jlaska | I took that action item from last week ... but with help from wwoods, I've carried my changes from the Beta wiki into the template Apr 01 12:15
wwoods | next was adding known install/upgrade issues to the release notes Apr 01 12:16
wwoods | jlaska already covered that Apr 01 12:16
adamw | how about the thing about live CD -> usb creation Apr 01 12:16
viking_ice | that should really be fixed.. Apr 01 12:16
viking_ice | asap Apr 01 12:16
wwoods | everything I'm aware of wrt. upgrades is already in the release notes Apr 01 12:17
jlaska | wwoods: we have the blurb about preupgrade iirc Apr 01 12:17
wwoods | yeah, someone should add a release note about doing livecd-iso-to-disk Apr 01 12:17
wwoods | jlaska: right Apr 01 12:17
wwoods | "Upgrading to Fedora 11 Beta from Fedora 10 using preupgrade will fail" Apr 01 12:17
wwoods | pretty clear Apr 01 12:17
jlaska | what's the release note around livecd-iso-to-disk ... the syslinux issue? Apr 01 12:17
wwoods | yeah - it won't boot if you create it in F10 or earlier Apr 01 12:18
adamw | yep Apr 01 12:18
wwoods | installing new syslinux is a workaround Apr 01 12:18
adamw | for now a note to upgrade syslinux from rawhide Apr 01 12:18
adamw | probably we should ship a syslinux upgrade for f10 or something Apr 01 12:18
wwoods | indeed Apr 01 12:18
jlaska | is there a bz on this against F10? Apr 01 12:18
adamw | not sure, i can file one if needed Apr 01 12:19
jlaska | looks like spot, f13, and jeremy are the most recent folks to touch syslinux in f11 Apr 01 12:20
f13 | only by accident (: Apr 01 12:21
jlaska | f13: do you know what would be in the way of buildinga new syslinux package for F10 that lets testers use F10 livecd-iso-to-disk with Rawhide images? Apr 01 12:21
jlaska | f13: heh, yeah I know what you mean ;) Apr 01 12:21
f13 | I don't now of anything standing in the way Apr 01 12:22
jlaska | okay Apr 01 12:23
f13 | but I'm not really familiar with the package itself. Apr 01 12:23
jlaska | f13: would spot or jeremy be good contacts? Apr 01 12:23
f13 | more like peter or jeremy Apr 01 12:23
jlaska | okay Apr 01 12:23
jlaska | adamw: would you mind getting a bz in for that? Apr 01 12:24
adamw | will do Apr 01 12:24
wwoods | we'll get that bug id into the release notes, document the workaround, and talk to pjones/jeremy about updating F10 (and F9?) syslinux to fix the bug Apr 01 12:24
wwoods | that should cover it Apr 01 12:24
wwoods | finally, the review meeting happened and we pushed the big green button Apr 01 12:25
wwoods | Beta went out, hurrah. Apr 01 12:25
jlaska | wwoods/f13: did you guys also want to do an update on autoqa? Apr 01 12:25
* | jlaska looking over previous minutes Apr 01 12:26
wwoods | oh, sure Apr 01 12:26
wwoods | let's do that Apr 01 12:26
f13 | I haven't touched it since the beta rush, looking forward to touching it today Apr 01 12:26
--- | wwoods has changed the topic to: Fedora QA Meeting | autoqa Apr 01 12:26
wwoods | yeah, I poked at it yesterday Apr 01 12:26
wwoods | and checked in an initial verifytree test case Apr 01 12:26
wwoods | we don't have a watcher for post-tree-compose, but we have one test case for it Apr 01 12:26
wwoods | heh Apr 01 12:26
jlaska | is this something one can run manually now? Apr 01 12:27
wwoods | I'm going to need to work on making tests interdependent, so we can stop testing if verifytree fails Apr 01 12:27
wwoods | but the next thing to do would be some qemu-based boot smoketest Apr 01 12:27
f13 | I'm hoping to make a watcher for post-tree-compose Apr 01 12:27
wwoods | (i.e. the lab-in-a-box stuff we talked about at FUDCon) Apr 01 12:27
wwoods | jlaska: sure, but you need to install autoqa and have a tree available at a local path Apr 01 12:28
jlaska | "install" ... from a git checkout? Apr 01 12:28
wwoods | yeah. git clone and make install Apr 01 12:28
jlaska | cool, what are the tests that you guys have now? Apr 01 12:29
wwoods | at the moment there's two hooks - post-repo-update and post-tree-compose Apr 01 12:30
wwoods | each has one test - repoclosure and verifytree, respectively Apr 01 12:30
jlaska | very nice Apr 01 12:30
jlaska | okay, is there anything you guys want to check-in on next week wrt autoqa ... or should we just leave as a general update again? Apr 01 12:31
wwoods | general update should be fine - with a little luck we should able to be running both hooks regularly by next week Apr 01 12:31
wwoods | but don't hold me to that Apr 01 12:31
jlaska | what if we just focus on repoclosure? Apr 01 12:32
jlaska | getting feature parity with the emails that go out now? Apr 01 12:32
jlaska | is that easier/harder/interesting? Apr 01 12:32
wwoods | f13: didn't we have that running on a host somewhere? Apr 01 12:32
f13 | qa1 Apr 01 12:32
f13 | its a tad... verbose Apr 01 12:33
jlaska | would it be easier to focus on ironing out the quirks with tests that don't require installs just yet Apr 01 12:33
f13 | we may want to re-think how it works. Apr 01 12:33
f13 | combining output into single mails or not Apr 01 12:33
f13 | yeah, I think willl and I could focus on the tree based tests Apr 01 12:34
* | jlaska suspects that adding cobbler/kvm/lab-in-a-box to the mix won't make things tremendously easier Apr 01 12:34
wwoods | right Apr 01 12:34
f13 | in parallel with lab-in-a-box work Apr 01 12:34
jlaska | I'd really like to plug in the lab-in-a-box stuff to what you guys are doing ... but there are a few "missing links" for me right now Apr 01 12:34
wwoods | well, we're designing the test system around the tests we have available Apr 01 12:34
wwoods | so you can't design the tests around the test system Apr 01 12:35
wwoods | or else: infinite recursion Apr 01 12:35
* | jlaska is convinced life is about infinite recursion Apr 01 12:35
jlaska | wwoods: yeah I see what you're saying ... I'll try to get in the loop with you guys to see how I can wedge what I've got into your framework Apr 01 12:36
wwoods | yeah, I'm joking, that'll work fine Apr 01 12:36
wwoods | but I'll need to talk to you about how we can make sure the autoqa stuff can launch (and process the results of) lab-in-a-box tests Apr 01 12:36
wwoods | we don't need to set that up, just need to make sure the framework can handle it Apr 01 12:36
jlaska | wwoods: okay, I see a sync-up with us in the week :) Apr 01 12:36
jlaska | yeah Apr 01 12:36
jlaska | cool, nice work guys! Apr 01 12:37
wwoods | but figuring out better reporting for the existing tests is the first thing on the agenda for me Apr 01 12:37
wwoods | and I think f13 will be assisting with that and working on a monitor script for post-tree-compose Apr 01 12:37
* | wwoods worries about re-inventing gridtrees.py Apr 01 12:37
jlaska | meh, if it works ... who cares what it looks like for now :) Apr 01 12:38
jlaska | just call it gridtrees2.py Apr 01 12:38
jlaska | :D Apr 01 12:38
wwoods | yeah, but we have to learn from our (old, non-public) mistakes Apr 01 12:38
jlaska | definitely! Apr 01 12:38
viking_ice | for the record the lab-in-the-box some thing that the end user execute or is the plan to being able to remotely execute the tests Apr 01 12:39
viking_ice | ( basically just leaving the end user up to supplying hw ) Apr 01 12:39
f13 | we won't be watching a .py file to be updated, we'll watch a path (: Apr 01 12:39
jlaska | viking_ice: wwoods or f13 can correct me, but my thinking was the same stuff we'd run in an automated fashion, could be installed and run by users Apr 01 12:39
wwoods | viking_ice: the idea is that the lab-in-a-box stuff should allow automated install testing on any machine capable of virtualization Apr 01 12:40
jlaska | f13: haha :) Apr 01 12:40
viking_ice | and the test que.. setup.. Apr 01 12:40
wwoods | right - so users could run it, but we'll be most interested in having it running somewhere inside the fedora infrastructure - or at someone's desk Apr 01 12:40
wwoods | whatever, so long as we get testing Apr 01 12:40
viking_ice | as in the user fetches test cases ( kickstarts file etc ) and executes them.. Apr 01 12:40
jlaska | viking_ice: that's a great plan for the future Apr 01 12:41
wwoods | we're not there yet, though Apr 01 12:41
wwoods | but yeah, that's a good plan for the future stuff Apr 01 12:42
wwoods | the only other thing I had on my mind was the schedule proposal I mentioned last week Apr 01 12:42
wwoods | I did some research and talked to people and did some planning and whatnot and decided.. it's probably not worth the effort Apr 01 12:43
wwoods | It'd be much better spent on the stuff we've already got planned - better tools for testing and reporting, so we can do more efficient testing Apr 01 12:43
wwoods | at least that's how I see it for the near future. Apr 01 12:44
wwoods | so that idea is on Indefinite Hold. Apr 01 12:44
wwoods | okay. what else do we need to discuss? Apr 01 12:45
jlaska | can I touch on something adamw raised last week? Apr 01 12:45
jlaska | we're sort of discussed it already, so I don't want to spend a lot of time ... but adamw hilighted that we might not be communicating the known issues effectively Apr 01 12:45
jlaska | from ... QA/Meetings/20090325#Building_the_Beta_Known_issues Apr 01 12:46
jlaska | we spent some time building out the known issues list ... are we happy with the result? Apr 01 12:46
adamw | linky? Apr 01 12:46
--- | wwoods has changed the topic to: Fedora QA Meeting | Known issues Apr 01 12:46
jlaska | does the consensus from last week still hold? Apr 01 12:46
jlaska | known issues - Fedora_11_Beta_release_notes#Anaconda_installer_issues Apr 01 12:46
wwoods | Fedora_11_Beta_release_notes#Known_Issues Apr 01 12:47
jlaska | out consensus from last week - QA/Meetings/20090325#Building_the_Beta_Known_issues Apr 01 12:47
jlaska | Consensus was ... "# Result - QA team must internally reference the Beta release notes known issues in all IRC and email communication. " Apr 01 12:47
--- | dwmw2 is now known as dwmw2_gone Apr 01 12:47
jlaska | it's early still ... but "how's our driving"? Apr 01 12:47
wwoods | seems pretty good, anecdotally at least - everyone I've asked about bugs has said things like "I didn't see that in the release notes, so ..." Apr 01 12:48
wwoods | i.e. it seems like people are reading 'em Apr 01 12:48
jlaska | how much longer do we spend adding issues to the list ... a few things came up today Apr 01 12:48
adamw | the public announcements i've seen at least referenced the release notes Apr 01 12:48
jlaska | mainly syslinux I guess Apr 01 12:48
adamw | e.g. http://www.osnews.com/story/21232/Fedora_11_Beta_Released Apr 01 12:48
adamw | it doesn't specifically link to the known issues as we discussed, though Apr 01 12:49
adamw | perhaps i could poke rahul and suggest that to him for future release announcements Apr 01 12:49
wwoods | also on this topic: so warren started up a blog for rawhide issues: http://rawhidewatch.wordpress.com/ Apr 01 12:49
adamw | oh, yes, that's an AWESOME idea Apr 01 12:49
jlaska | ++ Apr 01 12:49
f13 | I've lost my right click... Apr 01 12:50
wwoods | we should coordinate with him - either send him updates, or see if he needs/wants help maintaining it Apr 01 12:50
wwoods | it's already on fedora planet, which is great Apr 01 12:50
wwoods | we might want to get it into the default bookmarks, at least for prereleases Apr 01 12:50
wwoods | (he's not on IRC right now or I'd just bring him in so we can talk about it) Apr 01 12:51
jlaska | that's a really good idea, perhaps checking in with him on how we can add issues to his list? Apr 01 12:51
wwoods | yeah, the first post sez "Please submit notable news to Warren Togami and it may appear here." Apr 01 12:53
jlaska | and there we have it Apr 01 12:53
wwoods | for the moment let's try to ping him on IRC (or, failing that, email him) with notable rawhide stuff Apr 01 12:53
wwoods | I'll talk to him about whether he wants/needs help from QA maintaining that page Apr 01 12:53
skvidal | or ask him if he can add poster to it Apr 01 12:53
jlaska | skvidal: so others can contribute you mean? Apr 01 12:54
wwoods | skvidal: right. also I hear rumors that the infrastructure team might be thinking about setting up wordpress for fedora Apr 01 12:54
skvidal | jlaska: yes Apr 01 12:54
jlaska | skvidal: roger Apr 01 12:54
skvidal | wwoods: yah - not sure of the last status on that, though Apr 01 12:54
wwoods | so we might want a plan to migrate over.. so it might be prudent to figure that out before we go putting this link all over the place Apr 01 12:54
skvidal | which is why having it on the planet is fine Apr 01 12:55
skvidal | or ask infrastructure to setup a redirect Apr 01 12:55
skvidal | rawhidebabyeating.fedoraproject.org Apr 01 12:55
skvidal | nomnombabies.fedoraproject.org Apr 01 12:55
skvidal | then you can give out that address Apr 01 12:55
jlaska | does someone want to checkin with warren before next meeting just to see what his plans were and if/how we can engage? Apr 01 12:55
skvidal | and when/if it moves... Apr 01 12:56
jlaska | I don't mind chatting with Warren if there are no takers Apr 01 12:57
jlaska | and he arrives! Apr 01 12:58
jlaska | wwoods: adamw: viking_ice: f13: any other discussion topics ... or should we start wrapping up? Apr 01 12:59
adamw | just to note that infrastructure is working on my calendaring proposal Apr 01 12:59
f13 | not much, just a lot of catch up to do post-bet arush Apr 01 12:59
adamw | sounds like they're about to come up with a system that would do the job right Apr 01 12:59
viking_ice | sorry was away speaking to the dbadmin Apr 01 12:59
adamw | keep an eye on posts from susmit on infrastructure-list if you're interested Apr 01 12:59
jlaska | adamw: I saw that ... sounds like 2 candidates being reviewed? Apr 01 12:59
adamw | jlaska: it's moved on from there, neither of those did caldav, but susmit now says he's thought up a system which would work out Apr 01 13:00
adamw | combination of zicula and phpical Apr 01 13:00
jlaska | adamw: very nice, thank you for following that Apr 01 13:00
jlaska | wwoods: any other topics on your end? Apr 01 13:01
wwoods | none from me. jlaska, if you want to be the official Warren Liason then we'll review that next week Apr 01 13:02
wwoods | so let's try to sum up the actions planned: Apr 01 13:02
jlaska | wwoods: will do Apr 01 13:02
warren | huh? Apr 01 13:03
wwoods | [wwoods] autoqa: work on better (clearer) reporting from existing tests Apr 01 13:03
wwoods | (test, really: just repoclosure atm) Apr 01 13:03
wwoods | err, oops Apr 01 13:03
jlaska | warren: I'll catch up with you later with some questions on your rawhidewatch blog Apr 01 13:03
--- | wwoods has changed the topic to: Fedora QA | Action summary! Apr 01 13:03
wwoods | [f13] autoqa: work on monitor for post-tree-compose Apr 01 13:03
wwoods | [wwoods, jlaska] autoqa: discuss lab-in-a-box integration Apr 01 13:04
wwoods | [jlaska] talk to warren and see if he needs/wants help with http://rawhidewatch.wordpress.com/ Apr 01 13:05
wwoods | that's all I can remember off the top of me head Apr 01 13:05
jlaska | [adamw] - will file a F10 bug for the syslinux issue, initiate discussion with pjones or jeremy for building a updated F10 package Apr 01 13:05
wwoods | what else? Apr 01 13:05
warren | syslinux issue? Apr 01 13:05
adamw | warren: you can't build a usb image of the f11 beta live CDs without an updated syslinux Apr 01 13:05
viking_ice | so I guess if fedora is going to put up an wp instance we wont need the announcement one right? Apr 01 13:06
jlaska | should we take the action out of meeting for syslinux? Apr 01 13:06
wwoods | jlaska: not sure what you mean Apr 01 13:08
wwoods | if that's all the actions we got from this meeting, let's call it done and get to work on that syslinux thing Apr 01 13:08
jlaska | yeah that's what I wanted :) Apr 01 13:08
adamw | i'll do the bug Apr 01 13:08
jlaska | thanks ;) Apr 01 13:09
jlaska | thanks wwoods, I'll post minutes to the list shortly Apr 01 13:10
wwoods | cool. thanks, all Apr 01 13:10
--- | wwoods has changed the topic to: Channel is used by various Fedora groups and committees for their regular meetings | Note that meetings often get logged | For questions about using Fedora please ask in #fedora | See http://fedoraproject.org/wiki/Meeting_channel for meeting schedule Apr 01 13:10

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