From Fedora Project Wiki

(→‎Contributor: updates for git transition)
No edit summary
Line 5: Line 5:
'''Initial Draft:''' 2007-03-12<BR>
'''Initial Draft:''' 2007-03-12<BR>
'''Last Revised:''' 2010-06-30<BR>
'''Last Revised:''' 2010-06-30<BR>
{{lang|es|page=Proceso de Revisión de Paquetes}}

Revision as of 12:24, 17 August 2010

Author: Tom 'spot' Callaway and others
Revision: 0.06
Initial Draft: 2007-03-12
Last Revised: 2010-06-30

Review Purpose

In order for a new package to be added to Fedora, the package must first undertake a formal review. The purpose of this formal review is to try to ensure that the package meets the quality control requirements for Fedora. This does not mean that the package (or the software being packaged) is perfect, but it should meet baseline minimum requirements for quality.

Reviews are currently done for totally new packages, package renames, and packages merged from the old Fedora Core repository.

Review Process

There are two roles in the review process, that of the contributor and that of the reviewer. In this document, we'll present both perspectives.


A Contributor is defined as someone who wants to submit (and maintain) a new package in Fedora. To become a contributor, you must follow the detailed instructions to Join the package collection maintainers.

As a Contributor, you should have already made a package which adheres to the Package Naming Guidelines and Packaging Guidelines. There are also some packages that cannot be included in Fedora, to check if your package applies, check if it contains any Forbidden items.

When you're happy with your spec file, you should then submit that SRPM to a package review. Currently, this is done by following these steps:

  1. Put your spec file and SRPM somewhere on the Internet.
  2. Fill out a request for review in bugzilla. This is what a sample bugzilla request for review looks like: File:PackageReviewProcess review.png
  3. If you do not have any package already in Fedora, this means you need a sponsor and to add FE-NEEDSPONSOR to the bugs being blocked by your review request. For more information read the How to get sponsored into the packager group wiki page.
  4. 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.
Review Swaps
If nobody comments on your review request, you might want to mail to a mailing list (, for example) asking 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.
  1. 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 remove it from the Whiteboard
  2. A reviewer takes on the task of reviewing your package. They will set the fedora-review flag to ?
  3. 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.
  4. At this point, you need to request for your newly approved package an SCM admin request
  5. When this are complete, you can import your package into the SCM.
  6. Checkout the package using "fedpkg clone <package-name>" do a final check of spec file tags, etc, and run "make tag".
  7. Request a build by running "fedpkg build".
  8. Repeat the process for other branches you may have requested.
  9. Request updates for Fedora release branches, if necessary, using "fedpkg update" or another Bodhi interface as detailed in Bodhi Guide.
  10. 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, or 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.


The Reviewer is the person who chooses to review a package.

Comments by other people
Other people are encouraged to comment on the review request as well. Especially people searching for sponsorship should comment other review requests to show, that they know the Packaging Guidelines.

The Reviewer can be any Fedora account holder, who is a member of the packager group. There is one exception: If it is the first package of a Contributor, the Reviewer must be a Sponsor. You can check if a Contributor has already been sponsored by looking the e-mail address up in the packager group of the account system.

  1. Search for a review request that needs a reviewer: (fedora-review flag is blank or the bug is assigned to
  2. 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.
  3. if you want to formally review the package, set the fedora-review flag to ? and assign the bug to yourself.
Stepping back from a Review
If you want to step back from the review for any reason, reset the fedora-review flag to be blank and reassign the bug to the default owner of the component, which is
  1. Review the package.
  2. Take one of the following actions:
    • ACCEPT: If the package is good, set the fedora-review flag to +
      1. If the Reviewer is also acting as Sponsor for the Contributor, then this is the time to sponsor the Contributor in the account system .
    • FAIL, LEGAL: If the package is legally risky for whatever reason (known patent or copyright infringement, trademark concerns) close the bug WONTFIX and leave an appropriate comment (i.e. we don't ship mp3, so stop submitting it). Set the fedora-review flag to -, and have the review ticket block FE-Legal.
    • FAIL, OTHER: If the package is just way off or unsuitable for some other reason, and there is no simple fix, then close the bug WONTFIX and leave an appropriate comment (i.e. we don't package pornography for redistribution, sorry. Or, this isn't a specfile, it's a McDonald's menu, sorry.) Set the fedora-review flag to -.
    • NEEDSWORK: Anything that isn't explicitly failed should be left open while the submitter and reviewer work together to fix any potential issues. Mark the bug as NEEDINFO while waiting for the reviewer to respond to improvement requests; this makes it easier for reviewers to find open reviews which require their input.
  3. Once a package is flagged as fedora-review + (or -), the Reviewer's job is done although they may be called upon to assist the Contributor with the import/build/update process and to sure that the Contributor closes the ticket out when the process is complete.

Definitions for fedora-review Flag Settings

fedora-review (BLANK) Package Needs Review
fedora-review ? Package Under Review
fedora-review - Package Failed Review, dropped for legal or other issues.
fedora-review + Package Approved

Special blocker tickets

There are a few tickets which can be placed in the "Blocks" field to indicate specific ticket statuses:

FE-NEEDSPONSOR The submitter requires a sponsor; the review should only be done by a sponsor.
FE-DEADREVIEW The review has been closed out because the submitter has left; users looking for packages to submit may find some possibilities in these dead tickets.
FE-Legal The package is currently awaiting review by the legal team.

The Whiteboard

To save time for reviewers, the page at will hide certain tickets which are not reviewable. The Whiteboard field can be used to mark a ticket with various additional bits of status which will cause it to be hidden or displayed differently.

NotReady The package is not yet ready for review. It is possible to open a review ticket, mark it as NotReady, and continue to work on it until it's ready to be seen by a reviewer.
BuildFails The package fails to build.

Tracking of Package Requests