Difference between revisions of "SPR720 Package Review Lab"

From CDOT Wiki
Jump to: navigation, search
(New page: '''Resources:''' * Fedora Package Review Process * Fedora Package Review Guidelines * [[:fedora:Packaging/NamingGu...)
 
 
Line 9: Line 9:
 
# Ensure that you have a [https://admin.fedoraproject.org/accounts/ FAS2] and [http://bugzilla.redhat.com Bugzilla] account
 
# Ensure that you have a [https://admin.fedoraproject.org/accounts/ FAS2] and [http://bugzilla.redhat.com Bugzilla] account
 
# Select a package to review from this list: http://fedoraproject.org/PackageReviewStatus/NEW.html
 
# Select a package to review from this list: http://fedoraproject.org/PackageReviewStatus/NEW.html
# Follow the Fedora Package Review Process, but '''DO NOT''' assign the bug to yourself for review and '''DO NOT''' change the bug status. Instead, put the results of your review in a comment on the review request (bug). Add a small note saying something to the effect that this is an unofficial review.
+
# Follow the full Fedora Package Review Process, but '''DO NOT''' assign the bug to yourself for review and '''DO NOT''' change the bug status. Instead, put the results of your review in a comment on the review request (bug). Add a small note saying something to the effect that this is an unofficial review.
 
# Blog about your experience, and include a link to the review request (bug) in your blog posting.
 
# Blog about your experience, and include a link to the review request (bug) in your blog posting.

Latest revision as of 15:30, 30 October 2008

Resources:


Steps:

  1. Ensure that you have a FAS2 and Bugzilla account
  2. Select a package to review from this list: http://fedoraproject.org/PackageReviewStatus/NEW.html
  3. Follow the full Fedora Package Review Process, but DO NOT assign the bug to yourself for review and DO NOT change the bug status. Instead, put the results of your review in a comment on the review request (bug). Add a small note saying something to the effect that this is an unofficial review.
  4. Blog about your experience, and include a link to the review request (bug) in your blog posting.