From Fedora Project Wiki
< Changes
m (→How To Test) |
|||
| Line 113: | 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 might appreciate a translation check in build system. | |||
== Dependencies == | == Dependencies == | ||
Revision as of 07:07, 25 January 2017
Transdiff
Summary
A taskotron task to check packaged translations with 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 might 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.