Re: Proposals for the Updates Testing Procedure
Michael Schwendt <[email protected]> Fri, 14 Nov 2003 18:21:30 +0100
| Newsgroups | gmane.linux.redhat.rhl.devel,gmane.linux.redhat.fedora.devel |
|---|---|
| Message-ID | <[email protected]> |
--Signature=_Fri__14_Nov_2003_18_21_30_+0100_7/OQar9mGD+c5ZCh Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: 7bit On Thu, 13 Nov 2003 16:35:17 -0500, Jakub Jelinek wrote: > It would be good to know how many people actually tested it though, > if there are problems, they will likely show up in bugzilla, but > if there are no reports, it is unclear if this is because nobody > bothered to test or because it works for everybody. In Test Update announcements, would it be possible to give hints on what to test in particular or what features to check for changed behaviour? Else I assume that simply installing a test update is not of any help other than catching obvious regression. Because if I haven't been caught by a bug in the previous package revision, I'm unlikely to notice whether the test update fixes the bug. Or is the testing process solely a quantity based thing? -- --Signature=_Fri__14_Nov_2003_18_21_30_+0100_7/OQar9mGD+c5ZCh Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/tQ8a0iMVcrivHFQRAvz+AJ9g1qdSkoI2uQoHjFORsRBBVkzJHwCeMV2J Z9dbv4rJzQHDkOr9BGwxLUk= =gsVP -----END PGP SIGNATURE----- --Signature=_Fri__14_Nov_2003_18_21_30_+0100_7/OQar9mGD+c5ZCh-- -- fedora-devel-list mailing list [email protected] http://www.redhat.com/mailman/listinfo/fedora-devel-list