Re: [SLE] Suse 9.2 Pro
From: Sid Boyce (sboyce_at_blueyonder.co.uk)
Date: 07/21/04
- Previous message: Marek Libra: "Re: [SLE] [solved] SuSE 9.1: Interface name too long"
- In reply to: James Knott: "Re: [SLE] Suse 9.2 Pro"
- Next in thread: Hartmut Meyer: "Re: [SLE] Suse 9.2 Pro"
- Reply: Hartmut Meyer: "Re: [SLE] Suse 9.2 Pro"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 21 Jul 2004 14:02:56 +0100 To: suse-linux-e@suse.com
James Knott wrote:
> Scott Leighton wrote:
>
>> On Tuesday 20 July 2004 6:50 am, James Knott wrote:
>>
>>> Given the problems I've seen in both 9.0 and 9.1, I'd have to question
>>> how much testing they actually do. For example, given known problems
>>> with the Kmenu editor in 9.0, how did they manage to pass 9.1, which
>>> had
>>> the same problem? Why didn't Kppp work, without having to create a
>>> file?
>>>
>>
>>
>> I'm fairly new to Linux, but I have to say I don't understand your
>> viewpoint
>> at all here. Bugs in KDE are bugs that need to be fixed by the KDE
>> folks,
>> not SuSE. The distro includes hundreds of packages, to suggest that
>> the company (SuSe or otherwise) putting the distro together should
>> chase down and fix the bugs in all of those packages is unrealistic
>> IMHO.
>
>
> As I mentioned in another note, I used to do integration testing. If
> the testing revealed a problem with an application, which we couldn't
> fix or work around, that app was not to be included, until the problem
> resolved. If SuSE has a problem with KDE, they should work with KDE
> to resolve it, or stick with an earlier version that works. The
> problem with Kmenuedit was in SuSE 9.0 and corrected with an update.
> Why, given that previous experience, was the same problem in 9.1, with
> the same fix? Also, according to a presentation I attended at the
> Real World Linux conference in Toronto, SuSE works very closely with
> KDE and is the main contributor, so there should have been a lot of
> dialog, regarding any problems found.
>
> Incidentally, a few minutes ago, I had to fix the hotplug problem,
> caused by a recent update. How'd something like that get out, if
> proper testing was done?
>
>
As an aside, bugs.kde.org has been a site that has some really good
stuff, if someone has found an error, there is usually a fix available.
I've found them to be right on the ball, they will have fixes for SuSE
that never appear from SuSE, though it's possible that SuSE people may
have helped fixing the problem. I think that SuSE should open up Beta
testing to all, what if they get a thousand emails saying exactly the
same thing, may be one or two useful pointers to the problem may appear
in those 1000 bug reports. It's sure to lessen the need to retro fix
simple errors. Limited testing is useful if you are only interested in
fixing serious bugs - perhaps that is the sole objective - fix anything
that's considered minor in the next release, standard industry practice.
Regards
Sid.
-- Sid Boyce .... Hamradio G3VBV and keen Flyer =====LINUX ONLY USED HERE===== -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
- Previous message: Marek Libra: "Re: [SLE] [solved] SuSE 9.1: Interface name too long"
- In reply to: James Knott: "Re: [SLE] Suse 9.2 Pro"
- Next in thread: Hartmut Meyer: "Re: [SLE] Suse 9.2 Pro"
- Reply: Hartmut Meyer: "Re: [SLE] Suse 9.2 Pro"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
