Paul Rohr wrote:
> Thus, for each release we need to have a set of known people with fast net
> connections who'd be willing to test specific packages at release time. For
> an overview of the requirements, see:
My connection is not fast (shared 33.6 kbps modem). I expect under
normal circumstances I would download at most one package per day.
Close to a release, possibly a few. (And there will be days when
circumstances keep me from downloading any.)
> job description
> ---------------
> - work closely, in real-time, with the packager and/or the maintainer
> to figure out what's wrong, and
I like that statement, because it implies that I will not file every
problem in bugzilla, but only some which might be identified after
"close work" with the packager or maintainer.
Hmm, my original statement was:
> 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.
But I am willing to give it a try. ;-)
Randy Kramer
