Subject: Re: [RELEASE] 0.9.3 schedule ?
From: Randy Kramer (rhkramer@fast.net)
Date: Mon Aug 27 2001 - 06:38:09 CDT
Paul Rohr wrote:
> 5. Then, of course, the big trick is just to make sure that we get
> reasonably quick turnaround from the testers for each package. My belief is
> that, so long as each tester knows far enough in advance to make their time
> available, that shouldn't be too hard.
I think I'm almost willing to volunteer to be a tester (probably with a
binary for Win32, as I am not real confident about installing stuff on
Linux), but I'd like to know more about how to test or what you expect
from a tester.
Is there a specific set of documents to test with, or a test procedure?
Or do you pick a document (at random) and then, for example, try
something with every option on the menu? Or does it depend on the
"focus" of the release (the features to be emphasized)?
How much time would be involved in testing a given "release candidate",
and how often would "release candidates" be released?
Would you expect bugs to be filed in bugzilla, or just a report issued
back to the appropriate developer(s) (or list)?
Other?
Randy Kramer
This archive was generated by hypermail 2b25 : Mon Aug 27 2001 - 06:37:48 CDT