*** empty log message ***

svn path=/trunk/boinc/; revision=2325

doc/backend_programs.php

@@ -151,17 +151,14 @@ when they are no longer needed.</td>
             if all results are OVER
                 wu.file_delete_state = ready
 
-                // we can delete the canonical result output files
-                // if all successful results have been validated
-                if have canonical result and canonical_result.file_delete_state == INIT:
-                    if all results are != SUCCESS or (VALID or INVALID):
-                        canonical_result.file_delete_state = READY
-
             // outputs of error results can be deleted immediately;
             // outputs of successful results can be deleted when validated
-            for results outcome = CLIENT_ERROR or (SUCCESS and (VALID or INVALID))
-                if file_delete_state = INIT
-                    result.file_delete_state = READY
+            for results of WU
+                if canonical result and not all results OVER
+                    continue
+                if outcome = CLIENT_ERROR or (SUCCESS and (VALID or INVALID))
+                    if file_delete_state = INIT
+                        result.file_delete_state = READY
 
         // get next result timeout if any
         transition_time = MAX_INT

doc/credit.php

@@ -18,7 +18,7 @@ BOINC's credit system is based on a 'reference computer' that does
 <li>4 billion bytes per second of traffic to and from main memory
 (sequential, half reads and half writes)
 </ul>
-BOINC's unit of credit, the <b>Cobblestone</b>,
+BOINC's unit of credit, the <b>Cobblestone</b> <sup>1</sup>,
 is one day of CPU time on the reference computer.
 
 <p>
@@ -62,6 +62,8 @@ projects supply their own benchmarking functions.
 This will also handle the situation where a project's
 application does e.g. all integer arithmetic.
 </ul>
+<hr noshade size=1>
+<sup>1</sup> Named after Jeff Cobb of SETI@home
 ";
 page_tail();
 ?>

doc/index.html

@@ -67,12 +67,27 @@ Help debug and enhance the BOINC software.
 </td>
 <td valign=top bgcolor=d8f4ff>
 <center>
-<h3>Status and news</h3>
+<h3>Status</h3>
+</center>
+<p>
+BOINC is under development.
+The <a href=source/>source code</a> is available.
+We are currently conducting a beta test of BOINC
+using the SETI@home and
+<a href=http://maggie.ssl.berkeley.edu/ap/>Astropulse</a> applications
+(thanks, but we don't need more beta testers at this point).
+The public release will be announced on the
+<a href=http://setiathome.berkeley.edu>SETI@home</a> web site.
+Several other distributed computing projects are evaluating BOINC.
+
+<center>
+<h3>News</h3>
 </center>
 <b>September 4, 2003</b>
 <br>
-We've incremented the major version number of BOINC to 2.  All BOINC
-components must follow the major version number: we've upgraded the <a
+We've incremented the major version number of BOINC to 2.
+All BOINC components must follow the major version number.
+We've upgraded the <a
 href=http://maggie.ssl.Berkeley.edu/ap/>Astropulse</a> server to 2.01 and
 released <a href=http://setiboinc.ssl.Berkeley.edu/ap/download.php>BOINC core
 client 2.01</a>.  This was due to an architecture and protocol change in

doc/source/HEADER.html

@@ -1,5 +1,6 @@
 <h2>BOINC Source Code</h2>
 
 <p>
-The BOINC source code is available in the following formats.  Its use is
-subject to the <a href=../license_1.0.txt>BOINC public license</a>.
+The BOINC source code is available here.
+Its use is subject to the <a href=../license_1.0.txt>BOINC public license</a>.
+The "nightly" directory contains the most recent tarballs.

doc/tool_update_versions.php

@@ -1,13 +1,51 @@
 <? // -*- html -*-
    // $Id$
    require_once("docutil.php");
-   page_head("<code>update_versions</code> Tool");
-?>
+   page_head("update_versions");
+   echo "
 
-   TODO: document update_versions
+<code>update_versions</code>
+releases new core client and application versions.
+Core client versions will be visible to participants
+on the 'Download BOINC' web page.
+Application versions will be distributed to participants.
+Make sure to test versions before releasing them!
+<p>
+To use:
+<ul>
+<li> Create an 'apps directory' under the project directory.
+Add an
+";
+echo htmlspecialchars("<app_dir>");
+echo "
+element to config.xml giving the path of the apps directory.
+<li> Create a subdirectory 'boinc' in the apps directory.
+Put new core client versions here.
+<li> Create a subdirectory for each application,
+with the same name as the application.
+Put new application versions here.
+</ul>
+<p>
+<code>update_versions</code>
+scans these directories for new core client and application versions,
+copies them to the download directory,
+and updates the database as appropriate.
+
+<p>
+
+File names must be of the form <code>NAME_VERSION_PLATFORM[.ext]</code>, e.g.:
+<pre>
+boinc_3.17_i686-pc-linux-gnu.gz
+astropulse_7.17_windows_intelx86.exe
+</pre>
+The prefix name and extensions .gz, .exe, .sit are ignored.
+Platform strings must match the names of platforms in the database.
+
+<p>
+TO DO: check for code signature files.
 
 
-<?
+";
    page_tail();
 ?>