Hi, On Sun, 25 Dec 2016 13:41:29 +0100 Agostino Sarubbo wrote: > Runtime testing required (which is not mandatory) needs to be filled in the > following way: > - Yes, you are asking to run a package after have compiled/installed it. > - No, you don't need runtime testing (e.g. packages that install only some > files).
What is a recommended way to describe how runtime testing should be done? Some packages are quite complex and it is desired not only to run them, but to run with some args or do some actions. Some ideas: - copying description from one stablereq to another doesn't seem very practical to me; - adding comment inside ebuild is possible, but likely be missed during testing, especially for large ebuilds; also it looks like somewhat misused of ebuild; - maybe add new metadata tag like: <testing> Description how to test this package... </testing> ? Another question: do we steel need to set STABLEREQ keyword for stabilization bugs? Since we now have a dedicated Stabilization component, STABLEREQ looks redundant. And thank you all for an awesome change :) Best regards, Andrew Savchenko
pgpBnFfwq4Pc1.pgp
Description: PGP signature
