Some time in late March or early April each team will make its first sourceforge release - an alpha version of the final product.

• Your project web page should advertise now when that release will be available, and should advertise the actual availability when that release happens (as scheduled, of course).

• When the release has been made, send email to the class.

• When you receive an announcement of a release from another team, your team must test that release within four days. Imagine that you are a potential customer (user) who has stumbled on the web page and decided to try the software.

  • Read and follow the download instructions.

  • Read the release notes.

  • Install the product and try it out - just simple-mindedly starting the application and doing what comes naturally, hoping it will work.

  • Read the documentation, looking for help at places where you are confused or stuck.

  • Report back to the development team, in writing, with a copy to me. Be sure to praise the things you liked, and thank them for tricks you learned that you can incorporate in your own product. Be sure to criticize things you didn't like, but do it kindly. Make sure you don't complain about things that you have been warned in advance (in the documentation) are still under construction. (This isn't the Big Dig.) If you find new bugs, be sure to report them - in your report, and by submitting a bug report through sourceforge if possible.

Back to the cs681 home page.