From Fedora Project Wiki
< Changes
m (→Summary) |
|||
| 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 translation platform about whether they are latest? | A taskotron task to check packaged translations with respective translation platform about whether they are latest? | ||
== Owner == | == Owner == | ||
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.