Received: from martin.ravenbrook.com (martin.ravenbrook.com [193.112.141.241]) by raven.ravenbrook.com (8.9.3/8.9.3) with ESMTP id PAA15982 for ; Tue, 28 Nov 2000 15:07:17 GMT Received: from [193.112.141.252] (skylark.ravenbrook.com [193.112.141.252]) by martin.ravenbrook.com (8.8.8/8.8.7) with ESMTP id PAA14798 for ; Tue, 28 Nov 2000 15:00:58 GMT (envelope-from rb@ravenbrook.com) Mime-Version: 1.0 X-Sender: rb@pop3-ravenbrook Message-Id: Date: Tue, 28 Nov 2000 14:24:32 +0000 To: Perforce Defect Tracking Integration Project staff From: Richard Brooksby Subject: Case of state names Content-Type: text/plain; charset="us-ascii" ; format="flowed" This is a record of a design decision made by RB and GDR while working on automatic configuration generation from TeamTrack. We decided that Perforce users should not see TeamTrack states like "Closed" and "CLOSED" as different states. This might occur when two projects have different sets of state names with inconsistent cases, and both projects replicate to Perforce. Instead, all TeamTrack state names are normalized to lower case in all internal data structures in the replicator. This decision is applied consistently so that future developers of the replicator don't get confused when they get states from different maps. This creates a limitation that case can't be used to distinguish states within a project in TeamTrack, because the replicator can't then deduce transitions from state changes in Perforce. References to this document needs to be inserted in the sources where GDR has today written an approximate reference (to "Case of state names").