Daniel Goller wrote:
On Tue, 2006-04-11 at 09:36 -0400, Stephen P. Becker wrote:
Eldad Zack wrote:
Hello,
Sometimes it becomes a problem whenever a new release or a tricky bugfix comes
up for a certain package.
To improve QA we can let our userbase help, especially people who use certain
packages quite heavily - they can provide good or even superior QA than devs.
I think it would be a nice idea to keep a userlist for anyone who'd like to
volunteer testing packages they regularly use.
We can consider a web interface for enrolling users to specific packages, and
maybe even get a bug.g.o account for the list, this way a bug can be opened
for the testers to comment on whenever a change that requires testing or
maybe just aiding arch teams to stablize packages.
Maybe this was already pitched but it has just occured to me.
Comments?
Isn't this why we already have the arch tester position as described by
GLEP 41 (http://www.gentoo.org/proj/en/glep/glep-0041.html)?
Furthermore, are you saying that users would enroll themselves via this
hypothetical web interface, or that an arch team would do so for users
who have proven themselves to be worthy? If the former, this would be a
serious step back in terms of QA (think about sorting out all the crap
reports from ricer overlay users with OMGFAST CFLAGS from the decent
ones). If the latter, I think the arch tester position already covers
this sort of thing.
-Steve
didn't he ask for people who know a particular application very well?
i think there is a big difference between agreeing to test one
particular package since they know it very well and want to make sure
noone breaks it vs. being a full AT with all the things they get asked
to test
I understand the idea, and I like it. However inorder to really get this
to work smoothly and be useful some type of user-feedback tool that
would help report back the exact build environment with times dates and
warnings & errors + user notes would really make this type of system shine.
For example, package xyz-1.1 comes out, and user is on this hypothetical
list and gets notified of it.
package xyz-1.1 is ~arch (given), user decides they want to test it and
they emerge it the usual way.
After emerging version 1.1, user should (inorder to give his report) run
a tool that will send the ebuild's environment (CFLAGS, etc) and prompt
for the user to it a "rating" (value of whether or not the package
works) & give some notes (say, special requirments to make it work, or a
patch, or just simply , "Works".)
Anyways, I like the idea. +1
Regards,
Andrew
--
gentoo-dev@gentoo.org mailing list
