From Fedora Project Wiki

< Env and Stacks

Revision as of 13:54, 28 February 2014 by Pingou (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)


Automated packages review tools

Summary

Move the package review off bugzilla by created a dedicated application integrating git, pull-request mechanisms and fedora-review for early feed-back.


Owner

Current status

  • Targeted release: Fedora 22?
  • Last updated: 2014-02-28
  • Tracker bug: NA

Detailed Description

The Fedora Review server aims at moving package review off bugzilla. This would allow easy integration with git from the begining of the life of the package (including the review), easy integration with fedora-review to provide early feed-back to new packages submitted.

Eventually this application could become the new faces of pkgs.fedoraproject.org, seats on the top of the git repos where we have all our spec files and provide and support pull-requests allowing new contributors/packagers to help maintaining existing packages.

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).

Scope

  • Create a demo server/application
  • Speak to FPC if they agree
  • Run reviews on server
  • Move reviews from bugzilla
  • Remove component review from bugzilla
  • Update documentation
  • Proposal owners:

Feature owners have to make server working and run it by FPC and FESCo for approval.

  • 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: All documents related to reviews must updated.

Upgrade/compatibility impact

N/A (not a System Wide Change)

How To Test

Once the review server is created, create reviews :)


User Experience

Should make the review process a little faster: easier/earlier feedbacks for new packages submitted, easier

Dependencies

N/A (not a System Wide Change)

Contingency Plan

  • Contingency mechanism: Keep the reviews on the bugzilla.
  • Contingency deadline: N/A
  • Blocks release: No
  • Blocks product: No (although related to the Env & Stack WG)

Documentation

To come.

Release Notes