Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1523000

Summary: [CodeChange][i18n] oVirt 4.2 translation cycle 2
Product: [oVirt] ovirt-engine Reporter: Scott Dickerson <sdickers>
Component: Frontend.CoreAssignee: Scott Dickerson <sdickers>
Status: CLOSED CURRENTRELEASE QA Contact: Lukas Svaty <lsvaty>
Severity: medium Docs Contact:
Priority: unspecified    
Version: futureCC: bugs, lsvaty, sdickers, ykatabam
Target Milestone: ovirt-4.2.2Keywords: CodeChange, i18n
Target Release: ---Flags: rule-engine: ovirt-4.2+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-29 11:16:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: UX RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Scott Dickerson 2017-12-07 00:22:31 UTC
This bug exists to track updates from the second translation cycle of oVirt 4.2.  

Any intl/translation bugs that need to be verified prior to being closed can set this bug as a blocker.

Comment 1 Scott Dickerson 2017-12-07 01:08:28 UTC
Ref BZ1523004 for the cycle 2 update for ovirt-engine-dashboard.

Comment 2 Yaniv Kaul 2017-12-07 08:13:52 UTC
Target milestone?

Comment 3 Scott Dickerson 2017-12-07 19:38:59 UTC
Translation cycle 2 is currently scheduled to take place 2018-01-03 through 2018-01-17.  I'm planning the Zanata pull and posting the translation update patch on Jan 18, 2018.  I'm not sure what the target milestone should be given those dates.  Best I can tell, it'll be 4.2.2.

Comment 4 Yuko Katabami 2018-01-14 03:50:56 UTC
Hi Scott,

Translation cycle #2 has been completed.
It is ready to pull from Zanata.
Thank you.

Comment 5 Sandro Bonazzola 2018-03-29 11:16:07 UTC
This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.2 release, it has been closed with a resolution of CURRENT RELEASE.

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