Bug 807500

Summary:	RFE: Use Title and Version for Project Directory Name
Product:	[Community] PressGang CCMS	Reporter:	Joshua Wulf <jwulf>
Component:	CSProcessor	Assignee:	Nobody <nobody>
Status:	NEW ---	QA Contact:
Severity:	medium	Docs Contact:
Priority:	low
Version:	1.x
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
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:	---	Target Upstream Version:
Embargoed:

Description Joshua Wulf 2012-03-28 01:18:18 UTC

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-28 01:42:10 UTC

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.