Unit Instance

HTTP 200 OK
Allow: GET, PUT, PATCH, DELETE, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "translation": "https://translate-dev.freebsd.org/api/translations/freebsd-doc/boooks_dev-model/pt_BR/?format=api",
    "source": [
        "When a release is coming, the FreeBSD project changes shape somewhat. A release schedule is made containing feature- and code-freezes, release of interim releases and the final release. A feature-freeze means no new features are allowed to be committed to the branch without the release engineers' explicit consent. Code-freeze means no changes to the code (like bugs-fixes) are allowed to be committed without the release engineers' explicit consent. This feature- and code-freeze is known as stabilising. During the release process, the release engineer has the full authority to revert to older versions of code and thus \"back out\" changes should they find that the changes are not suitable to be included in the release."
    ],
    "previous_source": "When a release is coming, the FreeBSD project changes shape somewhat. A release schedule is made containing feature- and code-freezes, release of interim releases and the final release. A feature-freeze means no new features are allowed to be committed to the branch without the release engineers' explicit consent. Code-freeze means no changes to the code (like bugs-fixes) are allowed to be committed without the release engineers explicit consent. This feature- and code-freeze is known as stabilising. During the release process, the release engineer has the full authority to revert to older versions of code and thus \"back out\" changes should he find that the changes are not suitable to be included in the release.",
    "target": [
        "Quando uma versão está chegando, o projeto do FreeBSD muda de forma um pouco. Um cronograma de lançamento é feito contendo congelamentos de recursos e códigos, liberação de versões intermediárias e a versão final. Um congelamento de recursos significa que nenhum novo recurso pode ser aplicado na branch sem o consentimento explícito dos engenheiros de release. O congelamento de código significa que nenhuma alteração no código (como bugs-fixes) pode ser aplicada sem o consentimento explícito dos engenheiros de release. Esse congelamento de recurso e código é conhecido como estabilização. Durante o processo de lançamento, o engenheiro de release tem a autoridade total para reverter para versões mais antigas de código e, assim, \"desfazer\" as alterações, caso ache que as alterações não são adequadas para serem incluídas na versão."
    ],
    "id_hash": -3757699395677407282,
    "content_hash": -3757699395677407282,
    "location": "book.translate.xml:2202",
    "context": "",
    "note": "(itstool) path: section/para",
    "flags": "",
    "labels": [],
    "state": 10,
    "fuzzy": true,
    "translated": false,
    "approved": false,
    "position": 310,
    "has_suggestion": false,
    "has_comment": false,
    "has_failing_check": false,
    "num_words": 114,
    "source_unit": "https://translate-dev.freebsd.org/api/units/171645/?format=api",
    "priority": 100,
    "id": 171646,
    "web_url": "https://translate-dev.freebsd.org/translate/freebsd-doc/boooks_dev-model/pt_BR/?checksum=4bd9f84f0bf2b7ce",
    "url": "https://translate-dev.freebsd.org/api/units/171646/?format=api",
    "explanation": "",
    "extra_flags": "",
    "pending": false,
    "timestamp": "2020-06-06T14:21:30.133957Z"
}