>>>>> "B" == Buchan Milne <[EMAIL PROTECTED]> writes:
B> That's why we have snapshots, betas, and pre-releases.
So you're saying once it's cut, it's perfect? That's a bit much to
believe. Let's just agree to disagree: I want Mandrake's distros to
be maximally consistent and bug-free, and that means addressing
overlooked bugs just as much as the one's a few dozen people might
find.
IBM reports that they find two orders of magnitude more bugs in an OS
release within 30 days of a public release than in the /entire/
development QA period. That observation doesn't really fit your
snapshot/beta/pre model.
B> But it could also mean it was fixed upstream before 6.1 was
B> released, and it may take too much effort for someone else to
B> replicate the problem, only to discover it is fixed.
No one says it has to be checked. If only one person reports it, the
maintainer might keep an eye on the situation, if two people report
it, it's almost certainly at least a documentation bug.
Every bug report is an opportunity, but we're volunteers here, we are
under no obligation to open the door -- but I don't think we should
shoo them away.
B> There is an issue with drakboot automatically setting ACPI on
B> *after* installation, if the user doesn't watch closely. I am
B> not sure if this is fixed in cooker ..
Ah ... so it _is_ a cooker question after all :)
B> And the current determination is that it was not a bug.
Didn't you contradict that determination one paragraph back when you
asked me to file a bug report if the problem known to be in the cooker
is still there?
B> No, the correct answer is "don't use binary rpms from cooker on
B> a stable release". Doing so is asking for trouble.
Don't agree. If I agreed, I'd use RH -- cooker is /transparent/
technology, it just has to be repeated (and has been repeated) that
"if you mix your versions, you take your chances"
But it's still good testing -- we've caught many RPMs where the
dependency message was to the exact lib instead of the actual package,
so when people come in asking for the lib by name, we know the RPM had
a bug.
B> It may work just after a stable release, but if it doesn't
B> work, please don't waste the maintainers time filing a bug
B> report, until you have either rebuilt the source package, or
B> tried full cooker.
You you don't want anyone but experienced developers debugging the
distro? Ok ...
--
Gary Lawrence Murphy <[EMAIL PROTECTED]>: office voice/fax: 01 519 4222723
Business Advantage through Community Software - http://teledyn.com
"what I need is a job that doesn't interfere with my work" -gary murphy
