[opensuse-factory] QA team proposal
I think we could benefit from a QA team. Our duty would be to check various packages to make sure they function, and to test reported bugs. Also to seek upstream bug reports and patches to determine if the issue is upstream, and if a patch is available and inform the maintainers. Another potential point would be to check the openFATE for package requests and see about getting them built and put in the appropriate repo. What do you think of this idea, and do you have any feedback regarding a process... a way to standardize. Also, will the package maintainers and developers be willing to respond to the findings of a QA team? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Mon, Jan 16, 2012 at 11:55 PM, Roger Luedecke
I think we could benefit from a QA team. Our duty would be to check various packages to make sure they function, and to test reported bugs. Also to seek upstream bug reports and patches to determine if the issue is upstream, and if a patch is available and inform the maintainers.
Another potential point would be to check the openFATE for package requests and see about getting them built and put in the appropriate repo.
What do you think of this idea, and do you have any feedback regarding a process... a way to standardize. Also, will the package maintainers and developers be willing to respond to the findings of a QA team?
Roger, How does that differ from the testing team? (See the opensuse-testing ML.) Both the automated testing harness and the manual testing fall under that team as far as I know (and I think it is a small team). If you're not familiar with http://openqa.opensuse.org/results/ it is simply amazing in my view. I'm sure Bernhard could use help expanding on that, but the basic concept is in place and the testing team exists. I'm sure they would welcome another smiling face on the team. Greg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 01/17/2012 06:11 AM, Greg Freemyer wrote:
On Mon, Jan 16, 2012 at 11:55 PM, Roger Luedecke
wrote: I think we could benefit from a QA team. Our duty would be to check various packages to make sure they function, and to test reported bugs. Also to seek upstream bug reports and patches to determine if the issue is upstream, and if a patch is available and inform the maintainers.
Another potential point would be to check the openFATE for package requests and see about getting them built and put in the appropriate repo.
What do you think of this idea, and do you have any feedback regarding a process... a way to standardize. Also, will the package maintainers and developers be willing to respond to the findings of a QA team?
Roger,
How does that differ from the testing team? (See the opensuse-testing ML.)
Both the automated testing harness and the manual testing fall under that team as far as I know (and I think it is a small team).
If you're not familiar with http://openqa.opensuse.org/results/ it is simply amazing in my view.
I'm sure Bernhard could use help expanding on that, but the basic concept is in place and the testing team exists.
I'm sure they would welcome another smiling face on the team.
Greg
I think, Roger was talking about a different thing. openQA is mostly about making sure that Factory's core packages are usable, but not about following every single bug. The first part sounds like a bugzilla-screening team. I think, we have some people there (who might also be on our opensuse-testing ML), but things could be improved (faster, getting more bugs to the right people, triage) The openFATE part might be missing atm, so that many fate requests just lie around without people that could be interested knowing. I could imagine that we make tools to help those tasks (could be hosted on the openQA server). Ciao Bernhard M. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 01/17/2012 06:11 AM, Greg Freemyer wrote:
On Mon, Jan 16, 2012 at 11:55 PM, Roger Luedecke
wrote: I think we could benefit from a QA team. Our duty would be to check various packages to make sure they function, and to test reported bugs. Also to seek upstream bug reports and patches to determine if the issue is upstream, and if a patch is available and inform the maintainers.
Another potential point would be to check the openFATE for package requests and see about getting them built and put in the appropriate repo.
What do you think of this idea, and do you have any feedback regarding a process... a way to standardize. Also, will the package maintainers and developers be willing to respond to the findings of a QA team?
Roger,
How does that differ from the testing team? (See the opensuse-testing ML.)
Both the automated testing harness and the manual testing fall under that team as far as I know (and I think it is a small team).
If you're not familiar with http://openqa.opensuse.org/results/ it is simply amazing in my view.
I'm sure Bernhard could use help expanding on that, but the basic concept is in place and the testing team exists.
I'm sure they would welcome another smiling face on the team.
Greg
I think, Roger was talking about a different thing. openQA is mostly about making sure that Factory's core packages are usable, but not about following every single bug.
The first part sounds like a bugzilla-screening team. I think, we have some people there (who might also be on our opensuse-testing ML), but things could be improved (faster, getting more bugs to the right people, triage)
The openFATE part might be missing atm, so that many fate requests just lie around without people that could be interested knowing.
I could imagine that we make tools to help those tasks (could be hosted on the openQA server).
Ciao Bernhard M. Thank you. Its good to see I may not have been entirely amiss. Basically yeah, a well structured bug testing and triaging team. With efficient
On Wed, 2012-01-18 at 18:01 +0100, Bernhard M. Wiedemann wrote: procedures and good organizational tools I think such a thing could be a huge asset. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 01/18/2012 06:47 PM, Roger Luedecke wrote:
On 01/17/2012 06:11 AM, Greg Freemyer wrote:
On Mon, Jan 16, 2012 at 11:55 PM, Roger Luedecke
wrote: I think we could benefit from a QA team. Our duty would be to check various packages to make sure they function, and to test reported bugs. Also to seek upstream bug reports and patches to determine if the issue is upstream, and if a patch is available and inform the maintainers.
Another potential point would be to check the openFATE for package requests and see about getting them built and put in the appropriate repo.
What do you think of this idea, and do you have any feedback regarding a process... a way to standardize. Also, will the package maintainers and developers be willing to respond to the findings of a QA team?
Roger,
How does that differ from the testing team? (See the opensuse-testing ML.)
Both the automated testing harness and the manual testing fall under that team as far as I know (and I think it is a small team).
If you're not familiar with http://openqa.opensuse.org/results/ it is simply amazing in my view.
I'm sure Bernhard could use help expanding on that, but the basic concept is in place and the testing team exists.
I'm sure they would welcome another smiling face on the team.
Greg
I think, Roger was talking about a different thing. openQA is mostly about making sure that Factory's core packages are usable, but not about following every single bug.
The first part sounds like a bugzilla-screening team. I think, we have some people there (who might also be on our opensuse-testing ML), but things could be improved (faster, getting more bugs to the right people, triage)
The openFATE part might be missing atm, so that many fate requests just lie around without people that could be interested knowing.
I could imagine that we make tools to help those tasks (could be hosted on the openQA server).
Ciao Bernhard M. Thank you. Its good to see I may not have been entirely amiss. Basically yeah, a well structured bug testing and triaging team. With efficient
On Wed, 2012-01-18 at 18:01 +0100, Bernhard M. Wiedemann wrote: procedures and good organizational tools I think such a thing could be a huge asset.
I agree. From what I read in the Forums, the user base is not happy with the speed at which bug reports are initially processed, and the efforts placed on clearing them. They also regard openFATE as a black hole for ideas. Anything that could be done to improve these areas would be a help. One other thing that could easily be done is to notify the maintainer of a driver whenever an oops is generated. The triage people at Fedora and Ubuntu do this, which keeps me informed about problems with the drivers that I maintain. Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thu, Jan 19, 2012 at 2:00 AM, Larry Finger
On 01/18/2012 06:47 PM, Roger Luedecke wrote:
On Wed, 2012-01-18 at 18:01 +0100, Bernhard M. Wiedemann wrote:
I think, Roger was talking about a different thing. openQA is mostly about making sure that Factory's core packages are usable, but not about following every single bug.
The first part sounds like a bugzilla-screening team. I think, we have some people there (who might also be on our opensuse-testing ML), but things could be improved (faster, getting more bugs to the right people, triage)
The openFATE part might be missing atm, so that many fate requests just lie around without people that could be interested knowing.
I could imagine that we make tools to help those tasks (could be hosted on the openQA server).
Ciao Bernhard M.
Thank you. Its good to see I may not have been entirely amiss. Basically yeah, a well structured bug testing and triaging team. With efficient procedures and good organizational tools I think such a thing could be a huge asset.
I agree. From what I read in the Forums, the user base is not happy with the speed at which bug reports are initially processed, and the efforts placed on clearing them. They also regard openFATE as a black hole for ideas. Anything that could be done to improve these areas would be a help.
One other thing that could easily be done is to notify the maintainer of a driver whenever an oops is generated. The triage people at Fedora and Ubuntu do this, which keeps me informed about problems with the drivers that I maintain.
Larry
One question is whether there should be a single team, or separate teams for openfate and bugzilla (or, perhaps, members of the team who should be primarily dedicated to one or the other). -Todd -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 01/19/2012 08:29 AM, todd rme wrote:
On Thu, Jan 19, 2012 at 2:00 AM, Larry Finger
wrote: On 01/18/2012 06:47 PM, Roger Luedecke wrote:
On Wed, 2012-01-18 at 18:01 +0100, Bernhard M. Wiedemann wrote:
I think, Roger was talking about a different thing. openQA is mostly about making sure that Factory's core packages are usable, but not about following every single bug.
The first part sounds like a bugzilla-screening team. I think, we have some people there (who might also be on our opensuse-testing ML), but things could be improved (faster, getting more bugs to the right people, triage)
The openFATE part might be missing atm, so that many fate requests just lie around without people that could be interested knowing.
I could imagine that we make tools to help those tasks (could be hosted on the openQA server).
Ciao Bernhard M.
Thank you. Its good to see I may not have been entirely amiss. Basically yeah, a well structured bug testing and triaging team. With efficient procedures and good organizational tools I think such a thing could be a huge asset.
I agree. From what I read in the Forums, the user base is not happy with the speed at which bug reports are initially processed, and the efforts placed on clearing them. They also regard openFATE as a black hole for ideas. Anything that could be done to improve these areas would be a help.
One other thing that could easily be done is to notify the maintainer of a driver whenever an oops is generated. The triage people at Fedora and Ubuntu do this, which keeps me informed about problems with the drivers that I maintain.
Larry
One question is whether there should be a single team, or separate teams for openfate and bugzilla (or, perhaps, members of the team who should be primarily dedicated to one or the other).
-Todd
But at least, if that kind of mission is mandatory for the project, then the booster team (those who should help the community to build the community) should schedule one or two milestone on that. -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Ambassador GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thursday, January 19, 2012 08:29:28 todd rme wrote:
On Thu, Jan 19, 2012 at 2:00 AM, Larry Finger
wrote: On 01/18/2012 06:47 PM, Roger Luedecke wrote:
On Wed, 2012-01-18 at 18:01 +0100, Bernhard M. Wiedemann wrote:
I think, Roger was talking about a different thing. openQA is mostly about making sure that Factory's core packages are usable, but not about following every single bug.
The first part sounds like a bugzilla-screening team. I think, we have some people there (who might also be on our opensuse-testing ML), but things could be improved (faster, getting more bugs to the right people, triage)
The openFATE part might be missing atm, so that many fate requests just lie around without people that could be interested knowing.
I could imagine that we make tools to help those tasks (could be hosted on the openQA server).
Ciao Bernhard M.
Thank you. Its good to see I may not have been entirely amiss. Basically yeah, a well structured bug testing and triaging team. With efficient procedures and good organizational tools I think such a thing could be a huge asset.
I agree. From what I read in the Forums, the user base is not happy with the speed at which bug reports are initially processed, and the efforts placed on clearing them. They also regard openFATE as a black hole for ideas. Anything that could be done to improve these areas would be a help.
One other thing that could easily be done is to notify the maintainer of a driver whenever an oops is generated. The triage people at Fedora and Ubuntu do this, which keeps me informed about problems with the drivers that I maintain.
Larry
One question is whether there should be a single team, or separate teams for openfate and bugzilla (or, perhaps, members of the team who should be primarily dedicated to one or the other).
I would say the first question is - who's volunteering to be on the team... If say 3 people have time for it (which would already be really great) it'd make litle sense to split anything ;-)
-Todd
participants (7)
-
Bernhard M. Wiedemann
-
Bruno Friedmann
-
Greg Freemyer
-
Jos Poortvliet
-
Larry Finger
-
Roger Luedecke
-
todd rme