On Wed, 2010-04-21 at 10:13 -0400, Kamil Paral wrote: > Hello, > this is a final call for comments to our Package Update > Acceptance Test Plan [1]. This test plan is tightly related > to Package Update Acceptance Criteria [2] approved by FESCo. > It basically says how we, the QA team, will decide whether > a package update should be accepted or rejected. It also > tries to map the requirements of the policy into an actionable > test plan. > > If you have any comments about the test plan, please post > them now, so we can include them in the document. > > I'm a bit concerned about the test environment part. We have already determined in the work that WWoods is doing for depcheck, that we do need to consider all the pending updates when testing a particular pending update. It would make sense to me to follow the same logic here. As far as Responsibilities and Permissions, as others have said we could collapse the QA and Releng into the proventesters group. Also we should add the bodhi ticket author, as the person who owns the package, the person who did the build, and the person who submitted the update can all be different people. As far as Schedule we should make it clear at what phase the test runs. I think we want it to run post-update-submission, and must be completed before the request to push to either -testing or stable is "accepted". We talked with Luke a bit about this and how to handle it within koji/bodhi and have a game plan. -- Jesse Keating Fedora -- Freedom² is a feature! identi.ca: http://identi.ca/jkeating
Attachment:
signature.asc
Description: This is a digitally signed message part
-- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
