Bug 2172188

Summary:	[hammer_cli_foreman_kubevirt] [rubygem-hammer_cli_foreman_kubevirt] Pull 100% completed translations from the Phrase (a.k.a Memsource), and package them into installable build, to determine readiness for Sat-6.13 L10N QA
Product:	Red Hat Satellite	Reporter:	sandeep shedmake <sshedmak>
Component:	Compute Resources - CNV	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED MIGRATED	QA Contact:	sandeep shedmake <sshedmak>
Severity:	low	Docs Contact:
Priority:	low
Version:	6.13.0	CC:	ehelms, ekohlvan, lstejska, mhulan, rlavi, satellite6-bugs
Target Milestone:	Unspecified	Keywords:	i18n, MigratedToJIRA, Translation, Triaged
Target Release:	Unused
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-06 16:08:32 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2162325

Comment 6 Leos Stejskal 2023-06-05 06:39:59 UTC

Hi,
I propose to remove the BZ from 6.14. Due to other work on other tasks, we didn't manage to fix it in time
and there is little chance we can make it into the 6.14. All translations for hammer plugins (under the Rocket team) will be done in the upcoming release.

Comment 7 Brad Buckingham 2023-10-30 11:29:29 UTC

Bulk setting Target Milestone = 6.15.0 where sat-6.15.0+ is set.

Comment 14 Ewoud Kohl van Wijngaarden 2024-01-24 11:45:57 UTC

All the translations are in git master (https://github.com/theforeman/hammer-cli-foreman-kubevirt/commit/d677a5302e16b0b79377662b8b5a932f8a8c7485) but a release needs to be made and then packaged.

Comment 15 Eric Helms 2024-06-06 16:08:32 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.