Bug 988625 - RFE: Provide a standardize way of producing Beta content
RFE: Provide a standardize way of producing Beta content
Status: CLOSED NOTABUG
Product: PressGang CCMS
Classification: Community
Component: CSProcessor (Show other bugs)
1.1
Unspecified Unspecified
unspecified Severity low
: ---
: ---
Assigned To: pressgang-ccms-dev
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-07-25 22:32 EDT by lcarlon
Modified: 2015-03-12 07:26 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-03-12 07:26:38 EDT
Type: Bug
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 lcarlon 2013-07-25 22:32:57 EDT
Description of problem:

ECS is often required to publish beta content on access.redhat.com. When a guide is released as beta content, there are several things that need to be changed: 

The version number has -beta appended to it
A beta disclaimer should be added to the guide explaining what the purpose of the beta and stating that the beta is not supported. (Could be a single topic automatically added to the beginning of the guide i.e, topic 21349).

If we have a standardized way of generating the beta guides, it could simplify the process and ensure we're delivering a consistent message around the purposes of beta products and the accompanying beta guides.

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