Issues

UI implementation for MT editor

Internal server error (500) when the backend fails

Suspected memory leak in PersistentTranslationService/GoogleTranslatorBackend

Eliminate EJB usage

Support null media type in TypeString (auto-detect XML/HTML/TXT)

Use recursive algorithm for HTML/XML nodes in MT

Concurrent request on same content slows down response time

Increase font size in master

UI mockups for MT editor

Basic editor for MT

Handle XML link tags

Blank content breaks Machine Translation merge

MT should accept locale aliases (eg de-de) for translation requests

REST: Add BackendResource.getAttributionText(backendId) for use in Zanata's revisionComments

Custom change log causes exception in prod

Use explicit version in Managed Platform

Combine the gitlab repo with github repo

Track number of strings, words and characters sent for translation

Upgrade MS translators to V3

Setup centralized logging for MT server

duplicate key value violation exception

Migrate MT to external network app

Allow 'fuzzy' access to Magpie translation cache

Smarter default for back-end

Failed to build with Pipeline: Supporting APIs v 2.18

Document release process

Migration to Managed PaaS

Initial password is not distributed in the cluster

Use open paas for PR testing

Allow user to specify default backend as property

Run liquibase as mid life cycle event

Failed to download postgre because of curl exit 28 (timeout)

Use latest release +1 as new version instead of using Jenkins build number

Set up frontend build

admin user can create service account

Create User table and concept of admin users

User should not be redirected back to 404 or error page after successful sign in

Implement google backend for MT

ReactJS frontend for editing translations

Data model to support translations update

REST API to update translations

User management

DEV mode for MT service

ZanataMT - Ability to update translations served by MT (Portal)

ZanataMT - fine grained locking - based on doc url and locale