| Key: |
CIB-1555
|
| Type: |
Improvement
|
| Status: |
Resolved
|
| Resolution: |
Fixed
|
| Priority: |
Minor
|
| Assignee: |
jason
|
| Reporter: |
Stephen Nesbitt
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
Pulse
Created: 21/Jul/08 09:17 PM
Updated: 25/Jul/08 01:50 PM
|
|
| Component/s: |
Scm
|
| Affects Version/s: |
2.0.8
|
| Fix Version/s: |
2.0.9
|
|
|
As part of configuring the Perforce SCM, Pulse requests a value for the field "spec:" As a Perforce user I find this confusing since there really is no concept of "spec" within Perforce. A more Perforce specific term would be "client"
|
|
Description
|
As part of configuring the Perforce SCM, Pulse requests a value for the field "spec:" As a Perforce user I find this confusing since there really is no concept of "spec" within Perforce. A more Perforce specific term would be "client"
|
Show » |
|
Perforce Configuration - label "spec:" is confusing.
Thanks for the report. I agree that the term is confusing. Perforce variously uses 'client', 'client workspace' and 'client specification' when talking in this area. I think labelling this field 'template client' may be the ideal: as client is better known and more accurate, and because we use the client as a template, not directly.