Bug 1080577 - RHEV-M 3.4 beta 2 - integration with updates docs package - welcome page
Summary: RHEV-M 3.4 beta 2 - integration with updates docs package - welcome page
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: rhevm-branding-rhev
Version: 3.4.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 3.4.0
Assignee: Alexander Wels
QA Contact: Pavel Stehlik
URL:
Whiteboard: ux
Depends On:
Blocks: rhev3.4snap1
TreeView+ depends on / blocked
 
Reported: 2014-03-25 17:21 UTC by Einav Cohen
Modified: 2016-01-28 21:57 UTC (History)
6 users (show)

Fixed In Version: av4.2
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-12 14:03:55 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1072899 0 unspecified CLOSED [rhevm-doc] links are inaccessible due to wrong redirection 2021-02-22 00:41:40 UTC

Internal Links: 1072899

Description Einav Cohen 2014-03-25 17:21:51 UTC
Description of problem:
the docs package will be updated in rhev-m 3.4 beta 2; as it is expected to contain some structural changes, it may result in needed corresponding updates within the welcome page's link-URLs for the HTML/PDF documentation files. 
this bug is for tracking these changes.

Comment 1 Einav Cohen 2014-03-25 17:33:21 UTC
Jodi, for rhev-m 3.4 beta 2, we need an updated list of the documentation files that should be displayed in the welcome page. 

For each one of these documentation files, we need the following information:

1. The name of the document (this will be shown on the welcome page)
2. The path of the HTML document associated with that name.
3. The path of the PDF document associated with that name.

Thanks.

Comment 2 Jodi Biddle 2014-03-31 04:04:23 UTC
I believe this has been solved. Please advise if not.

Comment 4 Itamar Heim 2014-06-12 14:03:55 UTC
Closing as part of 3.4.0


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