Bug 807500 - RFE: Use Title and Version for Project Directory Name
RFE: Use Title and Version for Project Directory Name
Status: NEW
Product: PressGang CCMS
Classification: Community
Component: CSProcessor (Show other bugs)
1.x
Unspecified Unspecified
low Severity medium
: ---
: ---
Assigned To: pressgang-ccms-dev
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-03-27 21:18 EDT by Joshua Wulf
Modified: 2014-10-26 21:13 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Joshua Wulf 2012-03-27 21:18:18 EDT
I'm working on version 2 of an existing book.

I'm checking in this new version as a separate, distinct content spec, so now we have two content specs with different IDs, different version numbers, but the same name.

When I check out either of these content specs, it attempts to create the same project directory.

So, perhaps it's best to construct the project directory name using both the title and the version of the content specification, so that I can check out both versions of the book at the same time, and be clear about which is which.

I can think of two possiblities:

<title>-<version>

or 

<title>/<version>/
Comment 1 Lee Newson 2012-03-27 21:42:10 EDT
I believe the <title>/<version> approach is the better way to handle this because that way it provides a very clear hierarchy of different content specifications and their different versions.

Note You need to log in before you can comment on or make changes to this bug.