2011-05-04 AutoQA Discussion Minutes

[Tim Flink]

While a little disorganized, I think that our phone meeting earlier
today was useful. Hopefully everyone else is of the same mind even
though it was a little longer than initially planned :)

Rather than regurgitating all of the information covered in the
discussion, I have started documenting our planning in Trac [1]. It's
not done but I will finish the initial pages later today or tomorrow and
start creating more tickets to reflect our discussion today.

Feedback on formatting and/or usefullness would be appreciated. The raw
etherpad document produced is also available [2].

Tim

Discussed:
 - What is the important feedback information for maintainers?
 - What could the test logs look like?
 - What are our design goals for test log output?
 - When should we be sending email notifications to maintainers?
 - What are our next steps?

General Agreed:
 1. Evaluate release ready-ness on a regular basis (every 2 weeks to
    start)
 2. Write code for email defaults with an eye towards configurability
     - Only as far as this makes sense to do
     - Per-user email configuration will not be a part of 0.5.x
 3. For log formatting, plaintext logs are a must-have. HTML logs would
    be nice to have, but will likely not be a part of 0.5.x

General Todo:
 1. Create mockups for plaintext logs (specifically the "pretty" logs)
 2. Determine timebox for mockups, planning

Action Items:
 1. tflink to reach out to lmacken, infra on deployment timeline for
    Bodhi enhancements for email notification control
 2. jlaska to reach out to dmalcolm and esantiago for thoughts on
    maintainer result notification frequency


[1] https://fedorahosted.org/autoqa/wiki/Planning050series
[2]
http://tflink.fedorapeople.org/autoqa/planning/05x/2011-05-04_meeting_ope...