Content translation/Release criteria round 1

Phabricator board Note: this will be prepared in the next few weeks to align with the objectives outlined below

Data Loss
Issues causing loss of data will be triaged to appropriate level of severity and fixed based on the following consideration:
 * Is a workaround available?
 * Is it caused by a problem in CX or by individual user preferences or wiki-wide setting?
 * Can it be solved by the CX developers? (e.g. network issues are beyond the development team’s control)
 * What is the extent of loss: a few words, paragraphs, whole translation?

Expected outcome: While using Content Translation if users are informed that their translations have been saved then it must be saved and users must be able to restore the the saved version at any time.

Saving and Publishing failures
Issues that prevent users from saving and publishing articles are fixed based on the task priority

Expected Outcome: Existing bugs are fixed. For saving and publishing failures that occur at a later period, a stated timeline for bug resolution will be determined based on the task priority guidelines.

Basic Content Translation workflow
The core workflows of Content Translation beginning from the Entry points and completing when an article is published does not have any regressions.

Core workflows include the following three core test workflows (full details):
 * Publishing a draft of a missing page through grey interlanguage links
 * Publishing a suggested article in two steps
 * Publishing a draft with the corresponding warnings

Expected outcome: The core workflows are thoroughly tested for regressions and any gaps in the expected workflow are appropriately triaged and corrected.

Mark-up and post-edit overhead
Issues that produce mark-up when publishing and that need post-edit clean-up will be triaged to appropriate levels of severity and fixed based on the following criteria:
 * Feasibility of resolution by Content Translation developers
 * Frequency of occurrence
 * Valid adaptation of templates without markup failure

Expected outcome: (To be determined based on existing bug reports and CX feature limitations)

Editing tools
No new features to be integrated but existing bugs of the following classification are to be triaged to an appropriate level of severity and fixed:
 * Automatic Translation card
 * Template Editor
 * Alignment issues
 * Issues that prevent typing or editing of any kind

Expected outcome: (To be determined based on existing bug reports and CX feature limitations)

Prevention of disruption for users who don't use Content Translation
Issues within Content Translation that affect the workflow of users who are not using the tool should be analysed for impact and fixed according to appropriate severity. Tracking ticket

Expected outcome: Minimal to no impact on expected user workflows outside the Content Translation special pages

Performance
Performance fixes for the Content Translation features that are exposed in all pages. This includes:
 * Gray interlanguage links
 * Contributions pop-up menu
 * Contributions page

Expected outcome: a stated timeline for bug resolution will be determined based on the task priority guidelines and WMF infrastructure requirements

Testing and pre-deployment preparation
The following sections will be filled in after consultation with other departments in WMF and/or relevant user groups

Also see

 * Feedback from the community consultation
 * July-September 2016 objectives