Mime-Version: 1.0
Message-Id: <p05001912b656ba8cf53b@[193.112.141.254]>
Date: Fri, 8 Dec 2000 19:31:41 +0000
To: p4dti-staff@ravenbrook.com
From: Gareth Rees <gdr@ravenbrook.com>
Subject: Test report for release 0.4.2, 2000-12-08 (2)
Content-Type: text/plain; charset="us-ascii" ; format="flowed"

1. UG, 6: missing close parenthesis.

2. The UG should tell people that they need to upgrade their Perforce 
clients to 2000.2 for features like "change -s" to work.  A busy 
sysadmin may not get around to telling all her users to change their 
clients, or may simply miss that line in the AG.

3. The screenshot in section 12.1 comes out as a funny shade of 
grey/green on my monitor (the other screenshots are fine).

4. The integration reads the TeamTrack database much more often than 
it needs to.  This is because it creates one user_translator for each 
user field, and another for use in translating changes and fixes. 
Each user_translator has its own idea of what the user map is.  This 
has the potential for inconsistency.  There should be one user map 
per dt_teamtrack object.

One way to achieve this is to only create one user_translator object 
in configure_teamtrack.py and to use that in all places where one is 
needed (this is safe).  Similar remarks apply to the other 
translators, but user_translator is the one where this problem is 
most obvious.