fedora-docs-l10n/package-maintainers/master/pages/Package_Review_Process

Zen

Source string Source string

English

fedpkg clone

Needs editing

The string is read-only.

Skip

	English	Actions
	If nobody comments on your review request, you might want to mail to a mailing list (for example, devel) or the https://discussion.fedoraproject.org/c/workflows/pkg-review-swap/91[Package Review Swaps category] on Fedora Discussion to ask for a "review swap". This is an offer to do a review of someone else's package in exchange for them reviewing your package. This is usually one-for-one, or can be some other private arrangement depending on the difficulty of the respective packages.
	If you are not member of the https://accounts.fedoraproject.org/group/packager/[packager] group, you need a sponsor. Add https://bugzilla.redhat.com/show_bug.cgi?id=FE-NEEDSPONSOR[FE-NEEDSPONSOR] to the bugs being blocked by your review request. For more information read xref:How_to_Get_Sponsored_into_the_Packager_Group.adoc[How to Get Sponsored into the Packager Group].
	If this is a "re-review" request needed to xref:Package_Retirement_Process.adoc#claiming[claim ownership] of a retired package, add `Unretirement` to the _Whiteboard_ field.
	Wait for someone to review your package! At this point in the process, the `fedora-review` flag is blank, meaning that no reviewer is assigned.
	There may be comments from people that are not formally reviewing the package, they may add `NotReady` to the _Whiteboard_ field, indication that the review request is not yet ready, because of some issues they report. After you have addressed them, please post the URLs to the updated SPEC and SRPM file and clear the Whiteboard. It is expected that you will respond to commentary, including updating your submission to address it; if you do not, your ticket will be closed.
	A reviewer takes on the task of reviewing your package. They will set the `fedora-review` flag to `?`.
	The reviewer will review your package. You should fix any blockers that the reviewer identifies. Once the reviewer is happy with the package, the `fedora-review` flag will be set to `+`, indicating that the package has passed review.
	If you have not yet been sponsored, request sponsorship by https://pagure.io/packager-sponsors/issues[raising an issue at packager-sponsors].
	When your package passes the review you should use `fedpkg` to request a Git repository for it. Before you can request a Git repository for the package, you will need a https://pagure.io/settings/token/new[pagure.io api token] with _Create a new ticket_ ACL added into `~/.config/rpkg/fedpkg.conf`:
	[fedpkg.pagure] token = <generated-code>
	Request a Git repository for the package. For example, if the package name is `my-package` and the bugzilla review ticket is 12345, :
	fedpkg request-repo my-package 12345
	Check that your review bug is valid. It must have the `fedora-review` set to `+`, and it must be assigned to your reviewer. Otherwise your repository request will be closed as invalid.
	If you want to add your package to more Fedora releases and not just Rawhide, see xref:Package_Maintenance_Guide.adoc#requesting_branches[Requesting branches].
	When https://pagure.io/releng/fedora-scm-requests/issues[fedora-scm-requests tickets] for the requested repository and branches are closed, checkout the package:
	fedpkg clone
	Now you can xref:New_Package_Process_for_New_Contributors.adoc#import_commit_and_build_your_package[import your SRPM package]. Do a final check of spec file tags, etc.
	Request a Koji build by running `fedpkg build`. (You will need to set up https://fedoraproject.org/wiki/Infrastructure/Kerberos[Kerberos for Fedora project])
	Repeat the process for other branches you may have requested above:
	Checkout given branch: `fedpkg switch-branch f{MAJOROSVER}`
	Let Koji build the package for this branch: `fedpkg build`
	Request updates for Fedora release branches, if necessary, using `fedpkg update` or another Bodhi interface as detailed in https://fedoraproject.org/wiki/Bodhi[Bodhi].
	If possible, add your package to xref:Upstream_Release_Monitoring.adoc[Upstream Release Monitoring].
	To be notified if your package stops building successfully when dependencies are updated in Fedora, you can enable https://fedoraproject.org/wiki/Koschei[Koschei].
	You should make sure the review ticket is closed. You are welcome to close it once the package has been built on the requested branches. If you built for one of the Fedora release branches you can ask Bodhi to close the ticket for you when it completes the process. If you close the ticket yourself, use `NEXTRELEASE` as the resolution.
	You do not need to go through the review process again for subsequent package changes, and should not reference the review ticket in subsequent updates you create in Bodhi.
	Reviewer
	The Reviewer is the person who chooses to review a package.
	The Reviewer can be any Fedora account holder who is a member of the https://accounts.fedoraproject.org/group/packager/[packager group]. (If the Contributor is not yet sponsored, the review can still proceed to completion but they will need to find a sponsor at some point.)
	Search https://fedoraproject.org/PackageReviewStatus/[Package Review Tracker] for a review request that needs a reviewer: `fedora-review` flag is blank or the bug is assigned to `nobody@fedoraproject.org`.
	If you notice some issues that need to be solved before you want to start a formal review, add these issues in a comment and set the _Whiteboard_ of the bug to contain `NotReady`. This helps other possible reviewers to notice that the review request is not yet ready for further review action.

Loading…

None

String updated in the repository

English

English 13 characters edited Current translation Read-only

a year ago

Browse all string changes

Things to check

Multiple failing checks

Following checks are failing:

Unchanged translation: Spanish, Portuguese (Brazil)

Reset

Glossary

English	English
No related strings found in the glossary.

16731702 String information

Source string description

type: delimited block .

Flags

no-wrap, placeholders:r"`[\w\d -_<>(){}\[\]@$;.\*+=]*`":r"(link:)?https?://[\w\d\-_#?&%=\./]*":r"xref:[\w\d\-_/]*\.adoc(#[\w\d\-_/]*)?", read-only

Source string location

./pages/Package_Review_Process.adoc:136

String age

a year ago

Last updated

6 months ago

Source string age

a year ago

Translation file

pot/master/pages/Package_Review_Process.pot, string 29

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.