As always, wiki version (along with irc transcript) available at
https://fedoraproject.org/wiki/QA/Meetings/20100118.
= Attendees =
People present (lines said)
* jlaska (141)
* wwoods (30)
* adamw (22)
* kparal (21)
* Viking-Ice (8)
* nirik (5)
* cwickert (5)
* zodbot (4)
* RodrigoPadula (3)
* buggbot (1)
* abadger1999 (1)
* tk009 (1)
Regrets:
* [[User:liam]]
* [[User:rhe]]
= Agenda =
*
[
http://lists.fedoraproject.org/pipermail/test/2010-January/088008.html
Proposed meeting agenda]
*
[
http://meetbot.fedoraproject.org/fedora-meeting/2010-01-18/qa.2010-01-18-...
meetbot summary]
== Previous meeting follow-up ==
* maxamillion bring back conversation about Xfce 4.8 updato on
xfce(a)lists.fp.o and inform about conclusion
** No updates, save for next week
* Viking-Ice write lxde tests and find a date for the test day
** Created [
https://fedorahosted.org/fedora-qa/ticket/46 ticket#46],
agreed to move future discussion to the ticket
* cwickert to file an infrastruture ticket for the lxde mailing list
**
https://admin.fedoraproject.org/mailman/listinfo/lxde
* adamw and rhe to discuss ways to add install testing as a QA activity
** [[User:rhe|Hurry]] created a new install test home at
[[QA/Installation_Test]]. The idea is to have that big explanatory
page, and a bit in the 'joining' page which would link to it
** Adamw would look for possibilities to propose integrating the new
home with the existing [[QA:Fedora_13_Install_Test_Plan]].
* jlaska to reach out to beland for guidance/ideas on how to document
the process (or point to existing documentation) for how bugs are noted
(common_bugs, release notes, install guide etc...) How to determine
which bugs land in which place?
** Yuck, no traction on this task, jlaska will get things rolling with
this task.
== Security Policy Update ==
On Friday's FESCO Meeting, Adam and Will responded to questions
concerning building project-wide consensus around a security policy for
Fedora (see FESCO [
https://fedorahosted.org/fesco/ticket/297
ticket#297]).
Adam informed the group that FESCO kicked it back to the QA team with a
promise that if we come up with some kind of draft policy, people who
have a clue about security will be gracious enough to review it. So as
far as FESCo is concerned the next thing that happens is I come back
with a draft privilege escalation policy in hand.
Adam noted he would draft something quick'n'dirty using
[
http://spot.livejournal.com/312216.html Spot's famous blog post] as a
foundation, then seek QA team review before approaching FESCO.
== fedora-release-rawhide ==
[[User:wwoods|wwoods]] noted that a new fedora-release-rawhide package
may impact how we document opting into (and out of) testing rawhide via
yum (see [[Releases/Rawhide#Testing_Rawhide]]).
Nirik offered updates to [[Releases/Rawhide]] to help explain how to
activate the rawhide repos. Jlaska suggested that testers on
test(a)l.fp.org would no doubt be able to help review the recommendations.
== AutoQA project update ==
=== rpmguard package comparison ===
* Milestone -
https://fedorahosted.org/autoqa/milestone/Package%20update
%20tests
* Owner - [[User:kparal]]
''Last week''
* the small task ahead is to start sending output to autoqa-results and
address any issues that surface
''This week''
* Test results are now sent to autoqa-results, the next large step
is ...
* Continue discussing and start requirements gathering for a more formal
method for collecting and presenting package update test results (see
https://fedorahosted.org/pipermail/autoqa-devel/2010-January/000120.html)
=== Deps/conflicts prevention ===
* Milestone -
https://fedorahosted.org/autoqa/milestone/autoqa%
20depcheck
* Owner - [[User:wwoods]]
''Last week''
* working w/ lmacken to figure out how to gather information for a
''post-bodhi-update'' trigger
''This week''
* lmacken working an API change into the next release of bodhi
* A close to working depsolv test case (see
[
http://git.fedorahosted.org/git/?p=autoqa.git;a=blob;f=tests/depcheck/dep...]) is
available. Further clean-up needed.
=== install automation ===
* Milestone -
https://fedorahosted.org/autoqa/milestone/Automate%
20installation%20test%20plan
* Owner - [[User:lili]], [[User:rhe]]
''Last week''
* [[User:lili]] and [[User:rhe]] have started exploring test design
using the rats_install/install.py test as a starting point.
''This week''
* Continue working towards a single python test that will automate a DVD
install
* Publish test code using either a public git branch, code on a people
page, just a local git checkout
=== packaging/deployment ===
* Milestone -
https://fedorahosted.org/autoqa/milestone/Packaging%20and%
20Review
* Owner - [[User:jlaska]]
''Last week''
* Looking for autotest-client help with reviewing the package
* Scope out effort required to package autotest, gwt (BuildRequires) and
all of it's BuildRequires - see [[User:Jlaska/gwt]]
''This week''
* Continue to harden the next-steps for JARs in the ''uncertain'' (see
[[User:Jlaska/gwt#Status_uncertain]])
* Attempt to rework some directory permissions as requested in
autotest-client review
Current status on packaging:
* autotest-client - undergoing review - {{bz|548522}}
* autoqa - packaged (see
[
http://jlaska.fedorapeople.org/autoqa/autoqa-0.3-2.fc12.src.rpm
autoqa-0.3-2.fc12.src.rpm]), will submit once autotest-client is
accepted
* gwt-* - Still scoping out packaging needs (see [[User:Jlaska/gwt]])
* autotest - packaged (see
[
http://jlaska.fedorapeople.org/autoqa/autotest-0.11.0-4.el5.src.rpm
autotest-0.11.0-4.el5.src.rpm], will submit for review after gwt*
accepted
== Open discussion - <Your topic here> ==
=== When is the next F-13 milestone? ===
Wwoods asked when the next scheduled rawhide install image drop was
(see [[#Upcoming QA events]] below (2010-01-21 - Pre-Alpha Rawhide
Acceptance Test Plan #1). See
[
https://fedorahosted.org/rel-eng/ticket/3277 rel-eng ticket#3277] for
details.
Jlaska also noted that anaconda-13.16 (plus
http://clumens.fedorapeople.org/updates.img) had recently gone through
an automated rats_install test run. For results, see
http://jlaska.fedorapeople.org/rats.png.
= Upcoming QA events =
* 2010-01-21 - Pre-Alpha Rawhide Acceptance Test Plan #1
* 2010-01-28 - Pre-Alpha Rawhide Acceptance Test Plan #2
* 2010-02-04 - Pre-Alpha Rawhide Acceptance Test Plan #3
* 2010-02-05 - Alpha Blocker Meeting (F13Alpha) #1
* 2010-02-11 - Test Alpha 'Test Compose' (boot media testing)
* 2010-02-12 - Alpha Blocker Meeting (F13Alpha) #2
= Action items =
* jlaska - reach out to beland for guidance/ideas on how to document the
process for how bugs bubble through different release documents
* adamw to build on the famous spot security blog post and draft
something quick'n'dirty for QA review
* nirik intends to update the [[Releases/Rawhide]] wiki page to reflect
the changes (help appreciated)