On 05/07/2009 08:32 PM, Jeff Spaleta wrote:
On Thu, May 7, 2009 at 12:21 PM, Tom Lane <tgl@xxxxxxxxxx> wrote:
Well, as you just pointed out yourself, F11 testing is nonfunctional as
yet. But the bigger problem is that putting stuff into -testing seldom
accomplishes anything, at least for my packages. I think I might
possibly have gotten one bodhi comment across all the times I let stuff
sit in -testing until nagged; I have certainly *never* seen anything
pushed by the karma mechanism. If maintainers decide it's a waste of
time, there is not a lot you can say against them.
I eat testing religiously. I eat so much testing in fact, that I
can't easily sort through all the associated bug reports that I could
be testing for all the packages that I don't commonly "actively" use.
To know what is currently from testing on my system I have to run my
own yum/repoqueries with testing disabled looking for packages not
from regular updates. That's a real pain..and it still doesn't help me
figure out what I should be testing and reporting back on
specifically. So basically I end up reporting regressions if
anything.
What I need to be more helpful is a way for my system to inform me of
the current testing packages I have installed...and the specific
things I should be testing with regard to them. I todo list of sorts.
Agreed But...
Given the experience from maintainers that give change log entries like
"Update to" "Upstream release" etc.. which leave's testers with ?
I'm not seeing those maintainers being able to fill in what to
specifically check or test
( Good change log entries usually gives us a good hint what to look for
or test )
JBG
--
Viking-Ice
One of my gods has a hammer your's was nailed to a cross
You do the math!
|
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
