[Fedora QA] #141: proventester for pcfe?

[Fedora QA]

#141: proventester for pcfe?
------------------------------------------+---------------------------------
  Reporter:  pcfe                         |       Owner:  jlaska  
      Type:  proventester request         |      Status:  assigned
  Priority:  major                        |   Milestone:          
 Component:  Proventester Mentor Request  |     Version:          
Resolution:                               |    Keywords:          
------------------------------------------+---------------------------------
Comment (by pcfe):

 Hi James,

 Replying to [comment:1 jlaska]:
 [...]
 > Once you have read the instructions, please confirm that you ...

 Yupp, read them before requesting the proventester flag and figured most
 of it applies to what I do anyway ;-)

 >  1. have read and understand the instructions, and intend to follow the
 instructions when testing Fedora critical path updates

 Not to the letter, my testmachines sit in a disconnected segment of the
 lab here. Their software source is an internal server that mirrors it's
 Fedora trees from funet (I get well over 10MB/s from that mirror, viva
 Finland's modern infrastructure) once a day. So in general I lag by a day
 or two. On single packages I can pull manually, but most of my testing
 will have the 2 day lag until I have the packages. Is that OK?

 Secondly, 'you should perform a full system update from this repository at
 least once a day.' does not apply to my situation, all my test machines
 get frequently re-installed (while I have a few tens of test boxes at my
 disposal, I have many more test cases than machines, so all my tests are
 kickstart based. Meaning, if a package needs testing, I'll happily
 kickstart the Fedora version required and hoover in updates-testing from
 the local mirror, but said test machine may be running a completely
 different distro later in the day and is almost guaranteed to have been
 re-installed after a couple days). Again, if this does not fit the
 proventester requirement, no hard feelings if you turn my application
 down. The aim is to help Fedora and RHEL, not to brag about the
 proventester flag ;-)

 >  2. understand how to enable the update-testing repository

 yeah, my kickstart files drop in repofiles in %post, dropping one with
 updates-testing enabled is no issue.

 >  3. are familiar with providing test feedback using either the Bodhi web
 interface, or the fedora-easy-karma utility

 Yeah, I used Bodhi in the past when feedback was requested in a BZ. Can't
 use the easy-karma tool from the lab (the test boxes can only connect to
 the install server to hoover ks and RPMs from there)

 RU

 PCFE

-- 
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/141#comment:2>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance