Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1287319 - Usage of Promote to describe moving content view versions through lifecycle environments
Summary: Usage of Promote to describe moving content view versions through lifecycle e...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Views
Version: 6.1.4
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1317008
TreeView+ depends on / blocked
 
Reported: 2015-12-01 23:34 UTC by Stuart Auchterlonie
Modified: 2020-04-15 14:18 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-09 17:38:04 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Stuart Auchterlonie 2015-12-01 23:34:50 UTC
Description of problem:

The wording used to describe moving content view versions between
different environment is "promote", yet the activity that takes
place is more of a publication/presentation/association of the 
version with an environment.

For example, if you have a CV with versions 1, 2 and 3 in the
following environments

version 3 - env A
version 2 - env B
version 2 - env C
version 1 - env D

First you promote version 3 to environment B, which leaves you with

version 3 - env A & B
version 2 - env C
version 1 - env D

if you identify an issue with version 3 in env B, you have to rollback
to the previous version, which is done by "promoting" version 2 back to
env B. The change from version 3 -> 2 in env B, is not strictly speaking
a "promotion"

This bugzilla is to request consideration of an alternative way of
naming "promote" of CV's to better align with what actually happens

Version-Release number of selected component (if applicable):

6.1.2 - 6.1.4

Comment 3 Bryan Kearney 2016-07-08 20:46:24 UTC
Per 6.3 planning, moving out non acked bugs to the backlog

Comment 5 Bryan Kearney 2017-02-09 17:38:04 UTC
Thank you for this bug request. I do no see us addressing this in the next few releases. I am therefore closing this out. If you believe this was done in error, please feel free to re-open with additional information.


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