Units API.

See the Weblate's Web API documentation for detailed description of the API.

GET /api/units/171648/?format=api
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": [
        "For releases of the -STABLE-branch, the release process starts 45 days before the anticipated release date. During the first phase, the first 15 days, the developers merge what changes they have had in -CURRENT that they want to have in the release to the release branch. When this period is over, the code enters a 15 day code freeze in which only bug fixes, documentation updates, security-related fixes and minor device driver changes are allowed. These changes must be approved by the release engineer in advance. At the beginning of the last 15 day period a release candidate is created for widespread testing. Updates are less likely to be allowed during this period, except for important bug fixes and security updates. In this final period, all releases are considered release candidates. At the end of the release process, a release is created with the new version number, including binary distributions on web sites and the creation of CD-ROM images. However, the release is not considered \"really released\" until a <xref linkend=\"tool-pgp\"/>-signed message stating exactly that, is sent to the mailing list freebsd-announce; anything labelled as a \"release\" before that may well be in-process and subject to change before the PGP-signed message is sent. <_:footnote-1/>."
    ],
    "previous_source": "For releases of the -STABLE-branch, the release process starts 45 days before the anticipated release date. During the first phase, the first 15 days, the developers merge what changes they have had in -CURRENT that they want to have in the release to the release branch. When this period is over, the code enters a 15 day code freeze in which only bug fixes, documentation updates, security-related fixes and minor device driver changes are allowed. These changes must be approved by the release engineer in advance. At the beginning of the last 15 day period a release candidate is created for widespread testing. Updates are less likely to be allowed during this period, except for important bug fixes and security updates. In this final period, all releases are considered release candidates. At the end of the release process, a release is created with the new version number, including binary distributions on web sites and the creation of a CD-ROM images. However, the release is not considered \"really released\" until a <xref linkend=\"tool-pgp\"/>-signed message stating exactly that, is sent to the mailing list freebsd-announce; anything labelled as a \"release\" before that may well be in-process and subject to change before the PGP-signed message is sent. <_:footnote-1/>.",
    "target": [
        "Para releases da branch -STABLE, o processo de release inicia 45 dias antes da data de lançamento prevista. Durante a primeira fase, os primeiros 15 dias, os desenvolvedores aplicam as alterações que tiveram no -CURRENT e que desejam ter na versão para a branch do release. Quando esse período terminar, o código entra em um congelamento de código de 15 dias, no qual apenas correções de bugs, atualizações de documentação, correções relacionadas à segurança e pequenas alterações de driver de dispositivo são permitidas. Essas alterações devem ser aprovadas pelo engenheiro de release com antecedência. No início do último período de 15 dias, um candidato a reçease é criado para testes generalizados. É menos provável que as atualizações sejam permitidas durante esse período, exceto por importantes correções de bugs e atualizações de segurança. Neste período final, todos os releases são considerados candidatos a release. No final do processo de release, uma release é criada com o novo número da versão, incluindo distribuições binárias em sites e a criação de imagens em CD-ROM. No entanto, a release não é considerado \"realmente liberado\" até que uma mensagem <xref linkend=\"tool-pgp\"/>-assinada afirmando exatamente isso, seja enviada para a lista de discussão freebsd-announce; Qualquer coisa rotulada como \"release\" antes disso pode estar em processo e sujeita a alterações antes do envio da mensagem assinada pelo PGP. <_:footnote-1/>."
    ],
    "id_hash": 187832634361497890,
    "content_hash": 187832634361497890,
    "location": "book.translate.xml:2243",
    "context": "",
    "note": "(itstool) path: section/para",
    "flags": "",
    "labels": [],
    "state": 10,
    "fuzzy": true,
    "translated": false,
    "approved": false,
    "position": 316,
    "has_suggestion": false,
    "has_comment": false,
    "has_failing_check": false,
    "num_words": 204,
    "source_unit": "https://translate-dev.freebsd.org/api/units/171647/?format=api",
    "priority": 100,
    "id": 171648,
    "web_url": "https://translate-dev.freebsd.org/translate/freebsd-doc/boooks_dev-model/pt_BR/?checksum=829b50c92857c922",
    "url": "https://translate-dev.freebsd.org/api/units/171648/?format=api",
    "explanation": "",
    "extra_flags": "",
    "pending": false,
    "timestamp": "2020-06-06T14:21:30.224268Z"
}