From Fedora Project Wiki

< Env and Stacks

Revision as of 12:22, 28 February 2014 by Mmaslano (talk | contribs) (Created page with "<!-- Self Contained or System Wide Change Proposal? Use this guide to determine to which category your proposed change belongs to. Self Contained Changes are: * changes to is...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Automated packages review tools


Package reviews are taking too long, bugzilla is not the best tool for doing them. Let's create a server dedicated to reviews. The fedora-review tool can be used for validation of packages, but that's only a first part. We need to make approved packages automatically appearing in rawhide (or preferred branch).


  • Name: Your Name
  • Email: <your email address so we can contact you, invite you to meetings, etc.>
  • Release notes owner:

Current status

  • Targeted release: [[Releases/<number> | Fedora 22? ]]
  • Last updated: (DATE)
  • Tracker bug: <will be assigned by the Wrangler>

Detailed Description

Benefit to Fedora

Reviews of new packages could be on review for shorter time. Lot of work can be done automatically (licenses, run fedora-review, build in rawhide buildroot, check requirements).


Run reviews on server, close reviews in bugzilla, remove component review from bugzilla, change documentation on wiki pages about reviews, speak to FPC if they agree...

  • Proposal owners:

Feature owners have to make server working and then clean Fedora bugzilla from existing reviews.

  • Other developers: N/A (not a System Wide Change)
  • Release engineering: N/A (not a System Wide Change)

Packages from review server should be after approval automatically:

* added into dist-git
* build in rawhide
  • Policies and guidelines: N/A (not a System Wide Change)

All documents related to reviews must change.

Upgrade/compatibility impact

N/A (not a System Wide Change)

How To Test

N/A (not a System Wide Change)

User Experience

N/A (not a System Wide Change)


N/A (not a System Wide Change)

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? N/A (not a System Wide Change), Yes/No
  • Blocks product? product <-- Applicable for Changes that blocks specific product release/ -->


N/A (not a System Wide Change)

Release Notes