Difference between revisions of "Staging"
| Line 1: | Line 1: | ||
{{Github-migration-check}} |
|||
'''Staging''' is where language pairs go that have been extensively developed, but have not yet reached release readiness. They might be missing small portions of code, or some parts might need to be tweaked. They may also have quite advanced development, but low coverage. It should take around 1—4 weeks work to bring the pair to trunk level (release readiness). |
'''Staging''' is where language pairs go that have been extensively developed, but have not yet reached release readiness. They might be missing small portions of code, or some parts might need to be tweaked. They may also have quite advanced development, but low coverage. It should take around 1—4 weeks work to bring the pair to trunk level (release readiness). |
||
Revision as of 21:57, 7 March 2018
This page is out of date as a result of the migration to GitHub. Please update this page with new documentation and remove this warning. If you are unsure how to proceed, please contact the GitHub migration team.
Staging is where language pairs go that have been extensively developed, but have not yet reached release readiness. They might be missing small portions of code, or some parts might need to be tweaked. They may also have quite advanced development, but low coverage. It should take around 1—4 weeks work to bring the pair to trunk level (release readiness).
These pairs should build and have an advanced status of all modules (dictionaries with closed categories and decent coverage, an "ad hoc" PoS tagset and .prob (or CG), good coverage of main contrastive phenomena, testvoc clean, and a post-generator if needed). There should be a "PROBLEMS" (or "ISSUES") file saying status and major problems found while reading translations done with this pair (so, not a complete evaluation but a general compilation of big problems detected at the output).[1]
The staging pairs can be found here.
