fedora-docs-l10n/program_management/master/pages/pgm_guide/sop/changes-process — English @ Fedora Weblate: Bugzilla requires an email address to exist in the system …

Zen

Source string Source string

English

Bugzilla requires an email address to exist in the system in order to add it to a bug.  If an email address listed on a wiki page does not exist in Bugzilla, that address will not be CCed on the bug.  If no address listed exists in Bugzilla, the bug will remain assigned to the Change Wrangler.  In that case you should try and find an address for a Change owner that does exist in Bugzilla and re-assign it, or ask the Change owner(s) to register in Bugzilla.

Needs editing

The string is read only.

Skip

	English	Actions
	Add yourself to the _cc_ field
	Set the bug to block the `F<NN>Changes` tracking bug
	Set the bug status to `ASSIGNED`
	When appropriate (see below), create a Release Notes issue with the https://gitlab.com/fedora/docs/fedora-linux-documentation/release-notes/-/issues/new?issuable_template=Change[Change template].
	Use `Change: <title>` as the issue title
	Replace `URL HERE` with the wiki URL
	Set the _Milestone_ appropriately
	Add the Bugzilla and Release Notes links to the wiki page
	Update the xref:pgm_guide/sop/fridays_fedora_facts.adoc[Friday's Fedora Facts] entry
	Update the ChangeSet page
	In the scripts directory, run:
	`make clean`
	`make version=<NN> type=<SystemWide\|SelfContained> build` to regenerate the content
	Copy the contents of _ChangesList_ and paste into the appropriate section of the ChangeSet page
	If the Change involves a new Spin, add it to the xref:releases::index.adoc[Releases docs].
	Bugzilla requires an email address to exist in the system in order to add it to a bug. If an email address listed on a wiki page does not exist in Bugzilla, that address will not be CCed on the bug. If no address listed exists in Bugzilla, the bug will remain assigned to the Change Wrangler. In that case you should try and find an address for a Change owner that does exist in Bugzilla and re-assign it, or ask the Change owner(s) to register in Bugzilla.
	If the Change involves creating a new Spin, send the owners the xref:releases::spins/creating.adoc[Creating a Spin docs]. Otherwise, the coordination with Websites et al will probably be overlooked.
	RELEASE NOTES: most Changes should be considered for release notes, but sometimes this does not make sense. When a Change will not result in any notable impact on end users that can comprehensibly be explained to them, a release note is not necessary. An example of such a Change is https://fedoraproject.org/wiki/Changes/PortingToModernC : this is a highly technical Change that is only of consequence and interest to Fedora maintainers, not end users. When it does not make sense for a Change to have release notes, put "Release Notes tracker: N/A" in the "Current status" section of the Change page.
	Rejected proposals
	If a Change proposal is rejected by FESCo:
	Add `{{Change_Rejected_Banner}}` to the proposal's wiki page below the title
	Update the wiki page category to `Category:ChangePageIncomplete`
	If a tracking bug was pre-created, close it with Status _CLOSED -> DEFERRED_.

Loading…

None

String updated in the repository

English

Bugzilla requires an email address to exist in the system in order to add it to a bug. If an email address listed on a wiki page does not exist in Bugzilla, that address will not be CCed on the bug. If no address listed exists in Bugzilla, the bug will remain assigned to the Change Wrangler. In that case you should try and find an address for a Change owner that does exist in Bugzilla and re-assign it, or ask the Change owner(s) to register in Bugzilla.

English 460 characters edited Current translation Read only

a year ago

Browse all string changes

Things to check

Unpluralised

The string is used as plural, but not using plural forms

Reset

Glossary

English	English
No related strings found in the glossary.

15232210 String information

Source string description

type: Plain text

Flags

read-only

Source string location

./pages/pgm_guide/sop/changes-process.adoc:43

String age

a year ago

Last updated

a year ago

Source string age

a year ago

Translation file

pot/master/pages/pgm_guide/sop/changes-process.pot, string 31

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.