Development to release quality
Clyde E. Kunkel
clydekunkel7734 at cox.net
Mon Sep 12 14:35:36 UTC 2011
On 09/12/2011 10:17 AM, Jakub Jelinek wrote:
> Sure, we need QA, but for rawhide the development shouldn't be totally
> stalled as it is already in F16 right now, where updates for critpath
> packages, even when they have several hundred thousands of tests
> performed already during package building, just sit in bodhi for 2-3 weeks,
> often with first proventester karma after 12 or 14 days.
I think I used too much hyperbole in my original rant on this subject.
We certainly don't want rawhide packages to sit anywhere for a period of
time. We just want some system that assures us that the package got
some kind of testing before it was released to rawhide. And not every
package--just the critical core packages (what those are would be
another long thread).
For 99% of the packages, I am sure they have been tested by the
developer/maintainer. It is the package that just doesn't work that
causes the angst, when a simple install or update and run would have
shown a problem.
Anyway, the problem as it relates to rawhide is really too small to
spend any more energy on.
More information about the devel