Call for Community Testing: [version #] [component]

Draft: 26 October 2004
Target readers: Developers, Sysadmins, End users

What is a "Call for Community Testing"?

A Call for Community Testing is a mechanism to notify our users that new Globus code is available for testing in the field. Through these calls, the Globus Alliance hopes to expose its code to a wide variety of usage scenarios early in its development process. The ultimate goals are to catch bugs that have historically been found only after final releases, and to elicit feedback from the community on ways our software can be improved.

Participating in the [component] Testing Call is easy!

  1. Optional: Consider sending mail to testing@globus.org to let us know that you're helping out and describing what you intend to test.
  2. Install the software in a non-production environment. Use the [version #] distribution from http://www-unix.globus.org/toolkit/downloads/development/; the code can also be retrieved directly from CVS using the tag [tag].
  3. Exercise the software.
  4. Log your experiences in http://bugzilla.globus.org/globus/ under the "[component]" product. Please mention [version #] explicitly in the body of the report.
  5. Optional: Consider sending descriptions of your tests to testing@globus.org so that we might use them to build standard tests in the future.
  6. If you have any questions are comments about the process, send an email to testing@globus.org.

Testing period

The testing period for this call is [date range].

About [component]

[cristina will embed Brief Overview frag]

Reasons for testing [component]

[describe why volunteers are needed]

Components affected by [component]

[cristina will embed Technology Dependencies frag]

Environment/build parameters and other special conditions to test

  1. [example #1: Various security policies on resource/service/client]
  2. ...
  3. [example #n: The use of different JVMs]