fedora-docs-l10n/rawhide-gating/master/pages/index — Spanish @ Fedora Weblate: Fedora Rawhide Gating

Zen

Translation

English type: Title =

Spanish

Needs editing

Skip

	English	Spanish	Actions
	Fedora Rawhide Gating
	The following pages document the recently enabled gating mechanism in Fedora Rawhide.
	The aim of this initiative is to set up the infrastructure so that packages can be gated based on test results before they are allowed into Fedora Rawhide. This will reduce the amount of broken dependencies, uninstallable packages, and broken composes, and will ultimately lead to a more stable Rawhide. As an added benefit, this framework will also lessen the burden on the infrastructure and release engineering teams that ensure composes keep working.
	Reasons for Gating
	The basic principle of this proposal is to provide an environment in which packages can be built and tested without affecting other packages.
	When looking at how Rawhide package updates are gated on test results, we need to consider two workflows: single build updates, in which the contained build is only loosely coupled to other builds, and multi-build updates, in which the builds are tightly coupled.
	For a xref:single-builds.adoc[single build], the easiest solution is to provide a dedicated Koji tag in which these packages are built, and where they wait for their tests to pass before they can enter the buildroot.
	For xref:multi-builds.adoc[multiple builds], the solution is to rely on “side-tags” in Koji. These side-tags are basically tags created by the packager and available to them to do their work, in this case rebuild all the packages desired. The side-tag can then be sent to the test system as one unit of change.
	To use a now well-known analogy, a single build update is like sending a commit to a mailing list: it waits there to be reviewed and tested before being merged into the main repository. Multi-build updates are more similar to pull-requests: they can contain one or more builds which are reviewed and tested together as one change before being merged.
	Rawhide is a unique place in the Fedora ecosystem: It is the only place where large changes and rebuilds can be done. In stable Fedora releases, rebuilding large sets of packages is discouraged by the packaging guidelines, so the ratio of single- vs. multi-build updates in Bodhi (95% to 5%) is not reflective of the realities of the Rawhide ecosystem.
	The aim of Rawhide Gating is to build the infrastructure allowing to gate packages in Rawhide. The idea is for packages to go through Bodhi, be tested, and land in the Rawhide buildroot as they do today if the tests pass. In the simplest case, the packager workflow will not be impacted by this proposal; more complicated situations will require adjustements to the packager workflow. However, these adjustments are minimal.
	No tests are being made mandatory as this framework is introduced. It is up to the community (and xref:fesco::index.adoc[FESCo]) to decide if any, and if yes, which rules should be enforced for all packages.
	Additional Reading
	xref:faq.adoc[Frequently Asked Questions] provides answers to frequently asked questions about Rawhide gating.
	xref:ci::index.adoc[Fedora CI Documentation] has information about continuous integration in Fedora.
	xref:ci::quick-start-guide.adoc[Fedora CI Quick Start Guide] gives you basic information about Fedora CI in one place.

Loading…

mt:weblate-translation-memory

Suggestion added

English

Spanish 21 characters edited

a year ago

None

String updated in the repository

English

Spanish 0 characters edited Current translation Empty

a year ago

Browse all string changes

Things to check

Suggestions

There is 1 suggestion for this string.

View

Inconsistent

This string has more than one translation in this project or is untranslated in some components.

Reset

Glossary

English	Spanish
No related strings found in the glossary.

16783527 String information

Source string description

type: Title =

Flags

no-wrap

Source string location

./pages/index.adoc:2

String age

a year ago

Last updated

a year ago

Source string age

4 years ago

Translation file

po/es/master/pages/index.po, string 1

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.