Hello everyone,
As most of you will probably know there was a CentOS developers day last Friday (before the FOSDEM event). One of the things discussed during that day was the need/use for a QA coordinator. I think the best way to describe the job role is that this person should be between the developers and the QA team and make sure that QA testing is efficient and on time (as best as we can get). Also the coordinator is the single point of contact for the developers to talk to the QA team and the other way around.
I am the "lucky" person that will try to be this QA coordinator from now on. So I would like to make the following arrangements :
Towards the developers. Let me know as soon as possible when there is something in the pipeline that will need to tested by the QA team. The sooner as I know the sooner that I get can the testers mobilized and ready.
For the members of the QA team. If you are still interested in testing then make sure you are added to the QA Team page on the wiki (http://wiki.centos.org/QaTeam). During testing document all your findings on the wiki so we can keep track of things.
I will try to make a test plan and some sort of schedule on the wiki for each release that needs to go through QA as soon that I'm aware that a release is coming for testing, so everybody knows when there is a need for testing.
Alright, that is it for know I think. Let me know if you have any questions, comments, things I forgot, ...
Regards, Tim Your friendly neighborhood QA coordinator
On Wed, Feb 27, 2008 at 1:26 PM, Tim Verhoeven tim.verhoeven.be@gmail.com wrote:
Hello everyone,
As most of you will probably know there was a CentOS developers day last Friday (before the FOSDEM event). One of the things discussed during that day was the need/use for a QA coordinator. I think the best way to describe the job role is that this person should be between the developers and the QA team and make sure that QA testing is efficient and on time (as best as we can get). Also the coordinator is the single point of contact for the developers to talk to the QA team and the other way around.
I am the "lucky" person that will try to be this QA coordinator from now on. So I would like to make the following arrangements :
Congrats! Thanks for doing this.
Hi Tim,
Tim Verhoeven wrote:
I am the "lucky" person that will try to be this QA coordinator from now on. So I would like to make the following arrangements :
Thanks for stepping up for this task! and also for the excellent efforts you guys made for the 5.1 release.
There should be a wider scale announcement that will go out about this shortly.
Hi Tim,
On 2/27/08, Tim Verhoeven tim.verhoeven.be@gmail.com wrote:
I am the "lucky" person that will try to be this QA coordinator from now on. So I would like to make the following arrangements :
Thanks for picking this up. Your work on 5.1 QA was a terrific job, and bodes well for future QA cycles.
-- Daniel
On Wed, Feb 27, 2008 at 9:26 PM, Tim Verhoeven tim.verhoeven.be@gmail.com wrote:
best way to describe the job role is that this person should be between the developers and the QA team and make sure that QA testing
Hi! And also my thanks for taking this rather unglamorous (and unpaid) job.
Would you also be our point of contact when we run into issues like the last kernel-nfs problem?
Regards, Bent Terp
On Fri, Feb 29, 2008 at 8:19 AM, Bent Terp bent@nagstrup.dk wrote:
Hi! And also my thanks for taking this rather unglamorous (and unpaid) job.
Would you also be our point of contact when we run into issues like the last kernel-nfs problem?
Basically everything that comes up during QA and that needs to be fed back to the developers or upstream should go through me so we can make sure the issues are logged and followed up upon.
Regards, Tim
Tim Verhoeven wrote:
On Fri, Feb 29, 2008 at 8:19 AM, Bent Terp bent@nagstrup.dk wrote:
Hi! And also my thanks for taking this rather unglamorous (and unpaid) job.
Would you also be our point of contact when we run into issues like the last kernel-nfs problem?
Basically everything that comes up during QA and that needs to be fed back to the developers or upstream should go through me so we can make sure the issues are logged and followed up upon.
I suppose now would be a good time to also consider a Triage team for the bug tracker ....
how about a potential plan on how something like that could work ?
On Fri, 29 Feb 2008, Karanbir Singh wrote:
Tim Verhoeven wrote:
On Fri, Feb 29, 2008 at 8:19 AM, Bent Terp bent@nagstrup.dk wrote:
Hi! And also my thanks for taking this rather unglamorous (and unpaid) job.
Would you also be our point of contact when we run into issues like the last kernel-nfs problem?
Basically everything that comes up during QA and that needs to be fed back to the developers or upstream should go through me so we can make sure the issues are logged and followed up upon.
I suppose now would be a good time to also consider a Triage team for the bug tracker ....
how about a potential plan on how something like that could work ?
Like free goodies for the highest bug closer each month ? ;-)
(Would be an easy way to get rid of those expired CentOS DVDs ? :-D)
On Fri, Feb 29, 2008 at 5:35 PM, Dag Wieers dag@centos.org wrote:
On Fri, 29 Feb 2008, Karanbir Singh wrote:
I suppose now would be a good time to also consider a Triage team for the bug tracker ....
how about a potential plan on how something like that could work ?
Like free goodies for the highest bug closer each month ? ;-)
Thought I should nominate myself...
(Would be an easy way to get rid of those expired CentOS DVDs ? :-D)
But decided against it after seeing what I would get.. ;-)
-- dag wieers, dag@centos.org, http://dag.wieers.com/ -- [Any errors in spelling, tact or fact are transmission errors]
On Fri, 29 Feb 2008, Akemi Yagi wrote:
On Fri, Feb 29, 2008 at 5:35 PM, Dag Wieers dag@centos.org wrote:
On Fri, 29 Feb 2008, Karanbir Singh wrote:
I suppose now would be a good time to also consider a Triage team for the bug tracker ....
how about a potential plan on how something like that could work ?
Like free goodies for the highest bug closer each month ? ;-)
Thought I should nominate myself...
(Would be an easy way to get rid of those expired CentOS DVDs ? :-D)
But decided against it after seeing what I would get.. ;-)
You don't know what you are missing out on, though ! These are limited edition, real collectibles !
Pick up point is in Ghent, Belgium though ;-)
Dag Wieers wrote:
You don't know what you are missing out on, though ! These are limited edition, real collectibles !
Pick up point is in Ghent, Belgium though ;-)
And how do those get to Ghent? I thought I had all of them with me in Chemnitz at the moment?
:)
Cheers,
Ralph
Tim Verhoeven wrote:
On Fri, Feb 29, 2008 at 8:19 AM, Bent Terp bent@nagstrup.dk wrote:
Hi! And also my thanks for taking this rather unglamorous (and unpaid) job.
Would you also be our point of contact when we run into issues like the last kernel-nfs problem?
Basically everything that comes up during QA and that needs to be fed back to the developers or upstream should go through me so we can make sure the issues are logged and followed up upon.
Regards, Tim
I'm offering this snipped here in the off-chance the idea will be useful to the QA coordinator.
It's copied from fedora-test.
Jon Stanley and I were talking about other ways (besides have to query bugzilla in a web browser) to locate bugs needing to be triaged.
He created these as a test.
http://feeds.feedburner.com/f7-new-7days http://feeds.feedburner.com/f8-new-7days http://feeds.feedburner.com/rawhide-new-7days
I added them to my RSS reader and it works REALLY nice!
John
If not to the QA corrdinator, judging from the discussion that ensued it is likely to be handy to others here.
Bent Terp wrote:
On Wed, Feb 27, 2008 at 9:26 PM, Tim Verhoeven tim.verhoeven.be@gmail.com wrote:
best way to describe the job role is that this person should be between the developers and the QA team and make sure that QA testing
Hi! And also my thanks for taking this rather unglamorous (and unpaid) job.
Would you also be our point of contact when we run into issues like the last kernel-nfs problem?
It doesn't mean that you should stop filing bug reports now >:)
Cheers,
Ralph
-
Akemi Yagi -
Bent Terp -
Dag Wieers -
Daniel de Kok -
John Summerfield -
Karanbir Singh -
Ralph Angenendt -
Stephen John Smoogen -
Tim Verhoeven