On Sat, 26 Jul 2008, Paolo Campegiani wrote:
Wow! I thought I was the only one seeing such long times to resolve
support issues.
It takes one year to fix this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=250419
Patch requires to change a variable type from unsigned to signed
(1-line patch), in the meantime if root fills up the root partition,
at the next reboot /etc/fstab is wiped out. RH support found the bug
quickly, I appreciate that, but I cannot be satisfied that I have to
wait 365 days for the patch to be merged.
Not that I disagree with you, but there are only 2 windows per year to
patch this if it is not a security-issue (or no security issue is found in
that package).
So the best that could be done is roughly 183 (6 months) if a problem is
found only just after a release and it is not a security issue :-/
I hate it too, but the only way to improve this with the given rules, is
to test Beta releases for existing bugs and escalate (somehow). I think
Beta's should be promoted/tested more to reduce regressions.
--
Another best practice for Red Hat Support/QA could be to create a
framework where reproducable problems are stored as procedures against a
clean system. Then regressions can be tested in an automated fashion for
each (Beta) release.
Even better would be if customers/users could contribute these 'minimal'
procedures into the framework as part of the support process.
--
-- dag wieers, [EMAIL PROTECTED], http://dag.wieers.com/ --
[Any errors in spelling, tact or fact are transmission errors]
_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list
