Will Woods (wwoods@xxxxxxxxxx) said: > So. Does that define The QA Problem? Or are there other issues I'm > forgetting? If we're going to support 'always being able to upgrade in the devel stream to stable, and vice versa', we need to eliminate things that break upgrades. This involves: 1) automated post-build testing. Find broken packages before they go anywhere. Which means we need to find all the things that could break the repository, and write tests for them. 2) non-automated post-build testing before packages are pushed. Includes: - smoke testing - %post/%preun/%etc auditing Presumably more stuff that I'm missing here. Bill _______________________________________________ fedora-advisory-board mailing list fedora-advisory-board@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-advisory-board _______________________________________________ fedora-advisory-board-readonly mailing list fedora-advisory-board-readonly@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-advisory-board-readonly
