fedora-docs-l10n/fesco/master/pages/Updates_Policy — Portuguese (Brazil) @ Fedora Weblate: All updates still go to https://fedoraproject.org/wiki/Repositories#updates-testing[_updates-testing

Zen

Translation

Source change

English type: Plain text

Portuguese (Brazil)

Needs editing

Skip

	English	Portuguese (Brazil)	Actions
	Before Updates-testing Activation	Antes da ativação do updates-testing
	For a short time after branching but before the <<beta-freeze>>, the Branched release works like Rawhide: builds submitted by packagers are considered _stable_ after passing through any gating tests via a Bodhi update, and are sent to the https://fedoraproject.org/wiki/Repositories#fedora[_fedora_] repository directly in the next nightly compose. There are no restrictions beyond those for Rawhide at this point, but maintainers SHOULD be thinking about stabilization from this point onward, and making sure their packages will be in good condition well in advance of the stable release.	Por um curto período de tempo após a ramificação, mas antes do <<beta-freeze>>, a versão ramificada funciona como Rawhide: as compilações enviadas por empacotadores são consideradas estáveis (_stable_) após passar por qualquer teste de _gating_ por meio de uma atualização Bodhi e são enviadas para o repositório link:https://fedoraproject.org/wiki/Repositories#fedora[_fedora_] diretamente na próxima composição noturna. Não há restrições além daquelas para Rawhide neste ponto, mas os mantenedores DEVEM pensar sobre a estabilização a partir deste ponto, e ter certeza de que seus pacotes estarão em boas condições antes do lançamento estável.
	Repos available: https://fedoraproject.org/wiki/Repositories#fedora[_fedora_]	Repositórios disponíveis: link:https://fedoraproject.org/wiki/Repositories#fedora[_fedora_]
	Updates-testing Activation	Ativação do updates-testing
	At this point, the Bodhi update system is changed for the branched release to behave as it does for stable releases (see below) instead of Rawhide. From this point onward maintainers must create updates before packages become available to users and updates pass through https://fedoraproject.org/wiki/QA:Updates_Testing[_updates-testing_] to allow for feedback. Updates are moved from https://fedoraproject.org/wiki/Repositories#updates-testing[_updates-testing_] repository to https://fedoraproject.org/wiki/Repositories#fedora[_fedora_] repository after appropriate karma requirements have been reached. Bodhi sets reasonable defaults for karma and enforces minimum requirements for updates. <<karma-requirements>> for updates are described below.	Neste ponto, o sistema de atualização Bodhi é alterado para a versão ramificada para se comportar como faz para versões estáveis (veja abaixo) em vez de Rawhide. Deste ponto em diante, os mantenedores devem criar atualizações antes que os pacotes se tornem disponíveis para os usuários e as atualizações passem pelo link:https://fedoraproject.org/wiki/QA:Updates_Testing[_updates-testing_] para permitir feedback. As atualizações são movidas do repositório link:https://fedoraproject.org/wiki/Repositories#updates-testing[_updates-testing_] para o repositório link:https://fedoraproject.org/wiki/Repositories#fedora[_fedora_] após os requisitos de carma (_karma_) apropriados serem alcançados. Bodhi define padrões razoáveis para o carma e impõe requisitos mínimos para atualizações. <<karma-requirements>> para atualizações são descritos abaixo.
	Repositories available: https://fedoraproject.org/wiki/Repositories#fedora[_fedora_], https://fedoraproject.org/wiki/Repositories#updates-testing[_updates-testing_]	Repositórios disponíveis: link:https://fedoraproject.org/wiki/Repositories#fedora[_fedora_], link:https://fedoraproject.org/wiki/Repositories#updates-testing[_updates-testing_]
	Maintainers SHOULD:	Os mantenedores DEVEM:
	Avoid ABI/API changes where possible. If unavoidable, use a side-tag to rebuild packages.	Evitar alterações de ABI/API sempre que possível. Se for inevitável, use uma tag lateral para reconstruir os pacotes.
	Avoid any change that breaks composes of Live media, install media or testing.	Evitar qualquer alteração que quebra composições de mídia Live, mídia de instalação ou teste.
	Land any packages required for Changes planned for that release.	Obter todos os pacotes necessários para as mudanças planejadas para esta versão.
	Beta Freeze	Congelamento beta
	This freeze is scheduled to run for the three weeks leading up to the release date, but lasts until the release is signed off, even if it is delayed. During the freeze builds will not be marked _stable_ and moved from https://fedoraproject.org/wiki/Repositories#updates-testing[_updates-testing_] to https://fedoraproject.org/wiki/Repositories#fedora[_fedora_] (and hence included in the milestone release composes) except for those approved under the Fedora QA team https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process[blocker bug process] or https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process[freeze exception bug process]. Once the beta release is made, the freeze is lifted. The https://fedoraproject.org/wiki/Milestone_freezes[Milestone freezes] page provides more details and is the canonical reference in case of any conflict.	Conhecido como _beta freeze_ em inglês, esse congelamento está programado para ocorrer pelas três semanas anteriores à data de lançamento, mas dura até que o lançamento seja assinado, mesmo se atrasado. Durante o congelamento, as compilações não serão marcadas como _stable_ e movidas do link:https://fedoraproject.org/wiki/Repositories#updates-testing[_updates-testing_] para o link:https://fedoraproject.org/wiki/Repositories#fedora[_fedora_] (e, portanto, incluídas nas composições de marco da versão), exceto para aqueles aprovados pelo link:https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process[processo de bug bloqueador] ou link:https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process[processo de bug de exceção de congelamento] da equipe de QA do Fedora. Uma vez que a versão beta é feita, o congelamento é levantado. A página link:https://fedoraproject.org/wiki/Milestone_freezes[Milestone freezes] fornece mais detalhes e é a referência canônica em caso de qualquer conflito.
	Once the Beta Freeze starts, we are attempting to stabilize the major versions of software that will be shipped with the final release of the OS. Major updates can be tolerated, but breaking things for early testers should be avoided if possible.	Assim que o congelamento beta começa, estamos tentando estabilizar as principais versões de software que serão enviadas com a versão final do sistema operacional. Grandes atualizações podem ser toleradas, mas quebrar coisas para os primeiros testadores deve ser evitado, se possível.
	During this period:	Durante este período:
	All updates pulled into the release MUST fix an accepted blocker or freeze exception bug.
	All updates still go to https://fedoraproject.org/wiki/Repositories#updates-testing[_updates-testing_].	Repositórios disponíveis: link:https://fedoraproject.org/wiki/Repositories#fedora[_fedora_], link:https://fedoraproject.org/wiki/Repositories#updates-testing[_updates-testing_]
	Beta to Final Freeze
	This is the time between the Beta release and the <<final-freeze>>. The branched tree should now be stabilized and prepared for release. Major changes should be avoided during this period. Bear in mind that in most cases, the state your package has reached in the stable link:https://fedoraproject.org/wiki/Repositories#fedora[_fedora_] repository at the time of the Final Freeze is the state it will be in for the final release.
	Final Freeze
	This freeze leads to the creation of the final release. It is similar to the <<beta-freeze>> described above and follows the same update rules.
	The link:https://fedoraproject.org/wiki/Repositories#updates[_updates_] repository is enabled at some point during this time, and packages other than freeze exception / blocker fixes are queued for so called "zero day" updates, meaning they will be available in the _updates_ repository at the time of the release (day zero).
	Repositories available: https://fedoraproject.org/wiki/Repositories#fedora[_fedora_], https://fedoraproject.org/wiki/Repositories#updates[_updates_], https://fedoraproject.org/wiki/Repositories#updates-testing[_updates-testing_]	Repositórios disponíveis: link:https://fedoraproject.org/wiki/Repositories#fedora[_fedora_], link:https://fedoraproject.org/wiki/Repositories#updates-testing[_updates-testing_]
	All updates still go to link:https://fedoraproject.org/wiki/Repositories#updates-testing[_updates-testing_].
	Once the link:https://fedoraproject.org/wiki/Repositories#updates[_updates_] repository is available, builds marked as _stable_ will go there instead of to https://fedoraproject.org/wiki/Repositories#fedora[_fedora_].	Repositórios disponíveis: link:https://fedoraproject.org/wiki/Repositories#fedora[_fedora_], link:https://fedoraproject.org/wiki/Repositories#updates-testing[_updates-testing_]
	Stable Releases
	Philosophy
	Releases of the Fedora distribution are like releases of the individual packages that compose it. A major version number reflects a more-or-less stable set of features and functionality. As a result, we should avoid major updates of packages within a stable release. Updates should aim to fix bugs, and not introduce features, particularly when those features would materially affect the user or developer experience. The update rate for any given release should drop off over time, approaching zero near release end-of-life; since updates are primarily bugfixes, fewer and fewer should be needed over time.
	This necessarily means that stable releases will not closely track the very latest upstream code for all packages. We have Rawhide for that.
	Updates should be carefully considered with respect to their dependencies. An update that required (or provided) a new Python ABI, for example, would almost certainly not be allowed. ABI changes in general are very strongly discouraged, they force larger update sets on users and they make life difficult for third-party packagers. Additionally, updates that convert resources or configuration one way (i.e., from older → newer) should be approached with extreme caution as there would be much less chance of backing out an update that did these things.
	Whenever possible packagers should work with upstream to come up with stable branch releases or common patches for older releases, particularly when updating would require large dependency chain updates.
	Repositories available: https://fedoraproject.org/wiki/Repositories#fedora[_fedora_] https://fedoraproject.org/wiki/Repositories#updates[_updates_] https://fedoraproject.org/wiki/Repositories#updates-testing[_updates-testing_]	Repositórios disponíveis: link:https://fedoraproject.org/wiki/Repositories#fedora[_fedora_], link:https://fedoraproject.org/wiki/Repositories#updates-testing[_updates-testing_]

Loading…

None

String added in the repository

English

Portuguese (Brazil) 176 characters edited Current translation Needs editing

7 months ago

None

Source string changed

English 83 characters edited Needs editing

7 months ago

Browse all string changes

Things to check

Mismatched full stop

Source and translation do not both end with a full stop

Reset

Glossary

English	Portuguese (Brazil)
No related strings found in the glossary.

18117015 String information

Source string description

type: Plain text

Source string location

pages/Updates_Policy.adoc:251

String age

7 months ago

Last updated

7 months ago

Source string age

7 months ago

Translation file

po/pt_BR/master/pages/Updates_Policy.po, string 51

Shortcut	Action
`?`	Open available keyboard shortcuts.
`Alt` + `Home`	Navigate to the first translation in the current search.
`Alt` + `End`	Navigate to the last translation in the current search.
`Alt` + `PageUp` or `Ctrl` + `↑` or `Alt` + `↑` or `Cmd` + `↑` or	Navigate to the last translation in the current search.
`Alt` + `PageDown` or `Ctrl` + `↓` or `Alt` + `↓` or `Cmd` + `↓` or	Navigate to the next translation in the current search.
`Ctrl` + `Enter` or `Cmd` + `Enter`	Submit current form; this works the same as pressing Save and continue while editing translation.
`Ctrl` + `Shift` + `Enter` or `Cmd` + `Shift` +`Enter`	Unmark translation as Needing edit and submit it.
`Alt` + `Enter` or `Option` + `Enter`	Submit the string as a suggestion; this works the same as pressing Suggest while editing translation.
`Ctrl` + `E` or `Cmd` + `E`	Focus on translation editor.
`Ctrl` + `U` or `Cmd` + `U`	Focus on comment editor.
`Ctrl` + `M` or `Cmd` + `M`	Shows Automatic suggestions tab.
`Ctrl` + `1` to `Ctrl` + `9` or `Cmd` + `1` to `Cmd` + `9`	Copies placeable of a given number from source string.
`Ctrl` + `M` followed by `1` to `9` or `Cmd` + `M` followed by `1` to `9`	Copy the machine translation of a given number to current translation.
`Ctrl` + `I` followed by `1` to `9` or `Cmd` + `I` followed by `1` to `9`	Ignore one item in the list of failing checks.
`Ctrl` + `J` or `Cmd` + `J`	Shows the Nearby strings tab.
`Ctrl` + `S` or `Cmd` + `S`	Focus on search field.
`Ctrl` + `O` or `Cmd` + `O`	Copy the source string.
`Ctrl` + `Y` or `Cmd` + `Y`	Toggle the Needs editing checkbox.
`→`	Browse the next translation string.
`←`	Browse the previous translation string.