From Fedora Project Wiki
< Changes
m (→Summary) |
|||
| (9 intermediate revisions by the same user not shown) | |||
| Line 25: | Line 25: | ||
== Summary == | == Summary == | ||
<!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. --> | <!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. --> | ||
A taskotron task to check packaged translations with respective translation platform about whether they are latest? | |||
== Owner == | == Owner == | ||
| Line 58: | Line 58: | ||
== Detailed Description == | == Detailed Description == | ||
Often even after 100% translation | Often even after 100% translation, few packages do not get build with latest translations in Fedora. Transdiff would be a taskotron check about the same. Starting with [https://fedora.zanata.org/ fedora zanata] looks feasible. | ||
<!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. --> | <!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. --> | ||
== Benefit to Fedora == | == Benefit to Fedora == | ||
* | * Automated testing about latest translations for Fedora packagers. | ||
<!-- What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?--> | <!-- What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?--> | ||
| Line 110: | Line 107: | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
* Run script with libtaskotron. | |||
* Run script with | |||
* More details TBD | * More details TBD | ||
| Line 117: | Line 113: | ||
<!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. --> | <!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. --> | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
Package maintainers may appreciate a translation check in build system. | |||
== Dependencies == | == Dependencies == | ||
Latest revision as of 07:09, 25 January 2017
Transdiff
Summary
A taskotron task to check packaged translations with respective translation platform about whether they are latest?
Owner
- Name: Sundeep Anand
- Email: suanand@redhat.com
- Release notes owner:
Current status
Detailed Description
Often even after 100% translation, few packages do not get build with latest translations in Fedora. Transdiff would be a taskotron check about the same. Starting with fedora zanata looks feasible.
Benefit to Fedora
- Automated testing about latest translations for Fedora packagers.
Scope
- Proposal owners: Complete script and package it for Fedora.
- Other developers: N/A (not a System Wide Change)
- Release engineering: N/A (not a System Wide Change)
- List of deliverables: N/A (not a System Wide Change)
- Policies and guidelines: N/A (not a System Wide Change)
- Trademark approval: N/A (not needed for this Change)
Upgrade/compatibility impact
N/A (not a System Wide Change)
How To Test
- Run script with libtaskotron.
- More details TBD
User Experience
Package maintainers may appreciate a translation check in build system.
Dependencies
N/A
Contingency Plan
- Contingency mechanism: N/A
- Contingency deadline: N/A
- Blocks release? N/A
- Blocks product? N/A
Documentation
Will provide later.