Mime-Version: 1.0
Message-Id: <p05001902b62763167ca8@[10.128.16.193]>
Date: Fri, 3 Nov 2000 16:53:43 +0100
To: p4dti-staff@ravenbrook.com
From: Gareth Rees <gdr@ravenbrook.com>
Subject: Alpha testing at Quokka, 2000-11-02
Content-Type: text/plain; charset="us-ascii" ; format="flowed"

This is a report on issues arising during alpha testing at Quokka 
Sports, 2000-11-02.

1. We read the SELECTIONS table twice (once to look up type prefixes, 
once to look up single-select mappings).  Can we avoid this?

2. Various initializations happen only when we replicate for the 
first time.  This shows up as a long delay for the first replication.

3. Rob could set up a filter of the form Owner=rob, but not
Owner=rob_jxxx.  Is there a problem with underscores in the filter? 
[Surname elided at request of Quokka Sports.  RB 2000-11-08]

4. The tooltip for the "Delete Perforce Fix" icon in the "Version 
Control History" section in TeamTrack says "Delete filespec" by 
mistake.

5. Replication didn't go ahead when we closed a job.  The user didn't 
get an e-mail.  Why not?  Was there a conflict?  Could we be updating 
things too often so that it thinks there's a conflict when there's 
none?  Could this be a fallout from an incorrect hack I made today?

Analysis: apparently not.  Rob was working too fast for the 
replicator.  The replicator replicated the issue (in state new), then 
Rob assigned the issue.  Then the replicator woke up and saw that the 
issue had changed (because Rob had changed it) and that the job had 
changed (because it had just replicated it and because it can't rely 
on the P4DTI-user field).  This was a conflict.

So I think this will be solved when we can accurately tell who edited 
the job in Perforce.

6. If you have a check-in comment with an apostrophe in it, it 
doesn't show up properly.  Probably a bug in TeamTrack's parsing of 
the compound structures in the FILENAME field in the VCACTIONS table.

7. Could there be a button in Perforce that takes you to the 
TeamTrack page?  (Put it on the Tools menu?)  Could it actually go to 
the page showing the corresponding job.

8. Francis P. is keen on enforcement of association of a bug with each
Perforce submission.  For example, at code freeze time (or at a release
branch) you could enforce the rule "each code change must be associated
with a bug of high priority".  [Surname elided at request of Quokka
Sports.  RB 2000-11-08]

9. In the Perforce Windows interface, "Add new job" gives you a 
different layout from "edit job".  Why is that?

10. Jason M. is keen on being able to submit new jobs in Perforce. He
often finds bugs during development and doesn't want to switch to
TeamTrack to submit them.  [Surname elided at request of Quokka Sports. 
RB 2000-11-08]