Mime-Version: 1.0
Message-Id: <p0433013cb61367cbb3fa@[193.112.141.254]>
Date: Wed, 18 Oct 2000 16:28:56 +0100
To: p4dti-staff@ravenbrook.com
From: Richard Brooksby <rb@ravenbrook.com>
Subject: Test report for release 0.3.2
Content-Type: text/plain; charset="us-ascii" ; format="flowed"

1. The release directory and the unpacked installation need a README 
file to get people started.  I had to know to open sag/index.html.

2. In the SAG, section 3, it says that "the address and port number 
for the new Perforce repository will need to be entered into the 
replicator configuration".  This isn't true if the address is 0.0.0.0 
as shown.

3. Removed Python 1.5.2 and windows extensions this time, and 
re-installed them with all defaults.

4. Installed P4DTI in C:\Users\RB\P4DTI rather than the default location.

5. The description of how to use the TeamTrack database is 
incomplete.  You have to also select it after adding it to ODBC.

6. Twice I was asked whether I wanted to upgrade the database.  No 
guidance is given.

7. The database comes up blank (no licence?)  What do I do now?

8. Reference at the jobspec editing stage to the Perforce SAG.

9. Paragraph about changing Values-Status: needs to be clearer.

10. Typo: datavase.  (Check spelling.)

11. Idea: the default config_teamtrack.py shouldn't compile.  Put 
raises in for the important config parameters.  It should have a 
p4-port config item in as well, since we are telling them to run a 
special p4 server.

12. Bug when replication supposedly fails but fields are replicated 
anyway; see job000026.

13. Many other document changes to be done from last round (see 
report for 0.3.1).