Changes between Version 15 and Version 16 of AlphaInstructions

Timestamp:

Oct 17, 2011, 3:45:30 PM (13 years ago)

Author:

davea

Comment:

--

AlphaInstructions

@@ +1 @@
+[[PageOutline]]
 = Instructions for alpha testers =
 
@@ -14 +15 @@
 send email to [ProjectPeople David Anderson or Rom Walton],
 and we'll give you an account in the BOINC Alpha test project
-
-== The BOINC Alpha project ==
-
-Testers must log in to the [http://isaac.ssl.berkeley.edu/alpha/ BOINC Alpha project]
-to report test results.
-It's also a BOINC project, but usually it doesn't have any jobs, and you don't need to attach your client to it.
-
-== The BOINC Alpha email list ==
+(this is a BOINC project but it never has jobs; don't attach your client to it).
 
 Testers must subscribe to the [mlist:boinc_alpha boinc_alpha email list].
@@ -31 +25 @@
 asking alpha testers to download and test a specific new release of BOINC.
 You can find these releases on the [//download_all.php?dev=1 BOINC download page].
-Please try to report test results within two days of receiving the email.
+Please try to report test results within 3-4 days of receiving the email.
 
 == How to test ==
@@ -48 +42 @@
 
 Report results through the [http://isaac.ssl.berkeley.edu/alpha/test_form.php web-based interface].
+You must log in to the [http://isaac.ssl.berkeley.edu/alpha/ BOINC Alpha project]
+to report test results.
 
-If you find a bug or unexpected behavior in the BOINC client,
-it will help us a lot if you can tell BOINC to generate more detailed
-messages, and then post a message to boinc_alpha describing the problem
-and including the message log.
-To do this, use a text editor like Notepad to create a file
-'''cc_config.xml''' in your BOINC data directory.
-It has the following form:
-{{{
-<cc_config>
-   <log_flags>
-       <work_fetch_debug>1</work_fetch_debug>
-   </log_flags>
-</cc_config>
-}}}
-The '''work_fetch_debug''' flag tells BOINC to generate detailed
-messages about how it decides when to ask projects for jobs.
-There are  [userw:Client_configuration#Logging_flags lots of other flags] for other types of problems.
+== How to report bugs ==
 
-
-For more details on reporting bugs, see [ReportBugs Reporting Hard Bugs].
+In addition to reporting negative test results,
+we strongly encourage you to 
+[ReportBugs submit detailed bug reports].
 
 If you're not sure whether something is a problem, post to the boinc_alpha@ssl.berkeley.edu email list.
@@ -76 +57 @@
 or send email to the relevant [DevProcess area owner].
 
-
 == Resources ==