Bug 1328105 - Product page is not updated with 6.1.8 release
Summary: Product page is not updated with 6.1.8 release
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Documentation
Version: Unspecified
Hardware: Unspecified
OS: Unspecified
high
medium vote
Target Milestone: Unspecified
Assignee: Andrew Dahms
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-18 13:14 UTC by Tomer Brisker
Modified: 2019-09-26 18:42 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-20 06:33:55 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1328711 0 medium CLOSED Customer portal should be automatically updated on new z-stream releases 2021-02-22 00:41:40 UTC

Internal Links: 1328711

Description Tomer Brisker 2016-04-18 13:14:51 UTC 
Document URL: 
https://access.redhat.com/products/red-hat-satellite/

Section Number and Name: 
News

Describe the issue: 
The latest release listed is 6.1.7. However, 6.1.8 has been released since.

Suggestions for improvement: 
Update the news with the 6.1.8 announcement and release notes.

Additional information:
Comment 1 Andrew Dahms 2016-04-19 21:34:06 UTC 
Taking this bug to add an announcement and news links.
Comment 2 Andrew Dahms 2016-04-19 22:31:20 UTC 
Hi Tomer,

Thank you for raising this bug.

An announcement has now been created and posted on the product page. Does this meet your requirements for this bug?

Going forward, I will coordinate updates to the product page to match further updates as well.

Kind regards,

Andrew
Comment 3 Bryan Kearney 2016-04-19 23:49:35 UTC 
tomer.. can you close/current release once you have reviewed?
Comment 4 Tomer Brisker 2016-04-20 06:33:55 UTC 
Thanks for the update Andrew.
Looks just fine.
Going forward, I think we should look into automatically creating an announcement as part of the new version release process so we don't run into these kind of issues again. I will open a new bug to handle this.
Closing this bug.
Note You need to log in before you can comment on or make changes to this bug.