On Mon, 2007-06-04 at 02:20 -0400, Luke Macken wrote: > On Fri, Jun 01, 2007 at 04:55:29PM +0200, Hans de Goede wrote: > > Will Woods wrote: > > > Let's be a little more clear here - what the QA team actually does for > > > packages in updates-testing is *verification*. Check package sanity, > > > make sure programs don't segfault on startup, etc. I'm not expecting all > > > testers to understand the functions of the > > > packages as well as their maintainers. But anyone can tell if you missed > > > some deps or your package doesn't start on x86_64. > > > > 1) I already verify my packages on x86_64 myself > > That's great. I don't. > > > 2) starting libs is kinda hard > > Agreed. Matthias Clasen mentioned on fedora-maintainers how the > RHEL errata tool has a field where the engineer is supposed to > fill in QA test instructions, which might be a very useful thing for > bodhi to have. > Actually, having a concrete enough comment will already give quite a few hints for testing, even for a library. Like: "This update of libfoo fixes a problem that could lead to crashes of application bar, as reported in bug 123456." -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
