Hello, On Thu, Apr 09, 2009 at 08:47:37AM +0200, Holger Sickenberg wrote:
Anyway, we should really discuss on how to proceed in setting things up. Ideally it would be nice to start with alphas, but being the first time we try to do something like this, anytime is OK.
As far as I know there will not be any alpha and beta versions but something like milestones with 11.2 - so yes: starting to test with the first milestone make sense.
one of the main problems is (excuse my french) the management of it. As in what needs to be tested, how it should be tested or how it was tested, what has already been tested, how can we organize who tests what, how do test results make it back into Suse? How is the time line for opening Testopia to the outside, perhaps (initially) only for a selected "openSUSE test group"? Then we would have a test plan, would be able to avoid unneccessary double testing, and results would automatically find their way back to Suse QA.
I volunteered to take over the action item of the Testing/QA section of the CommunityWeek (http://en.opensuse.org/CommunityWeek). So maybe we can use that as kind of kick-off for the testing team.
That's a good idea. I'm particularly interested in the questions above, the organisation. Just doing isolated, random testing is not going to be very efficient. Regards, Rasmus -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org