Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1350822 - [RFE][Rebrand] change landing page from RHEV to RHV
[RFE][Rebrand] change landing page from RHEV to RHV
Status: CLOSED ERRATA
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: rhevm-branding-rhev (Show other bugs)
4.0.0
Unspecified Unspecified
high Severity high
: ovirt-4.0.1
: 4.0.0
Assigned To: Alexander Wels
Pavel Novotny
: FutureFeature
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-06-28 09:18 EDT by Moran Goldboim
Modified: 2016-08-23 17:14 EDT (History)
14 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-08-23 17:14:18 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: UX
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1687 normal SHIPPED_LIVE rhevm-branding-rhev bug fix and enhancement update for RHV 4.0 2016-09-02 17:03:56 EDT

  None (edit)
Description Moran Goldboim 2016-06-28 09:18:06 EDT
Description of problem:
landing page currently indicates "Red Hat Enterprise Virtualization". following product rebranding,each indication of it should be changed to "Red Hat Virtualization". same goes for RHEV to RHV and RHEV-M to RHV-M
Comment 2 Michal Skrivanek 2016-06-29 09:57:25 EDT
so you say this blocks beta2? I don't think it's reasonable to rename all locations in couple days
Comment 3 Oved Ourfali 2016-06-30 03:57:18 EDT
Reducing severity/priority to high.
We'll do our best.
Comment 5 Pavel Novotny 2016-07-14 14:01:53 EDT
FailedQA in rhevm-branding-rhev-4.0.0-3.el7ev.noarch

Occurrences of "RHEV" and "Enterprise" have been replaced in logos and en_US messages,
but are still present in other language translations:

# egrep "RHEV|Enterprise" --count --include=*.properties -o -r ./50-rhev-2.brand/*
...
...
./50-rhev-2.brand/branding.properties:1
./50-rhev-2.brand/external_resources.properties:1
./50-rhev-2.brand/messages_de_DE.properties:9
./50-rhev-2.brand/messages_es_ES.properties:3
./50-rhev-2.brand/messages_fr_FR.properties:9
./50-rhev-2.brand/messages_ja_JP.properties:9
./50-rhev-2.brand/messages_ko_KR.properties:9
./50-rhev-2.brand/messages_pt_BR.properties:9
./50-rhev-2.brand/messages_zh_CN.properties:9
./50-rhev-2.brand/resources.properties:1

Applies also for bug 1350854, bug 1351470 and bug 1351472.
Comment 6 Oved Ourfali 2016-07-14 14:30:42 EDT
This will only land in the next translation phase. 
I don't think this bug should cover that. 
Not sure there needs to be a bud other than the next translation cycle. 
If verified on English then please mark this as verified.
Comment 7 Greg Sheremeta 2016-07-14 14:46:05 EDT
Yeah, I had the same thoughts. As a rule we don't hand-edit those translated properties files. We just wait for them to get re-translated.

But I could see making an exception for this.
Comment 8 Oved Ourfali 2016-07-14 15:11:50 EDT
This shouldn't be an exception, unless we edit the translated files in Zanata and pull them from there. We shouldn't edit translated files manually.
Comment 9 Pavel Novotny 2016-07-15 08:33:33 EDT
(In reply to Oved Ourfali from comment #6)
> This will only land in the next translation phase. 
> I don't think this bug should cover that. 
> Not sure there needs to be a bud other than the next translation cycle. 
> If verified on English then please mark this as verified.

Ok, fine with me, I didn't know about the R&D workflow for translations.
Moving back to ON_QA a verifying for English only.
Comment 10 Pavel Novotny 2016-07-15 13:10:06 EDT
Verified in
rhevm-4.0.2-0.2.rc1.el7ev.noarch
rhevm-branding-rhev-4.0.0-3.el7ev.noarch

The logo and title now say "Red Hat Virtualization ...".
The page title is "Red Hat | RHVM".

No occurrence of words "Enterprise" or "RHEV" on the page.
Comment 12 errata-xmlrpc 2016-08-23 17:14:18 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-1687.html

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