On Wed, 20 Aug 2003 17:12:42 +0200 cobaco <[EMAIL PROTECTED]> wrote: > KDE is not mission critical in the sense that when a user's KDE-instance > crashes the KDE-instances of the other users will continue to run. Just > like when -in that same organization with some thousands of X terminals- > 1 X terminal has a hardware problem this is not a mission critical > problem (for the organization, it may be considered a mission critical > problem for the user of that particular terminal).
No. There's no reason an end user should be considered a second-class user that gets buggy software simply because he's not at some large organization. There's no reason why it's OK for there to be a mission critical problem for ANY user, even if it's just one user. The end user should not find packages that may have persistent, repeated bugs that impair his ability to do what he wants with his system. The end user should not find packages that cause data loss or have security bugs because they were only tested for a couple weeks (on the 11 architectures and with the other elements of the system). To the best of the developers' ability, the stable releases of Debian are supposed to be STABLE, for all packages, for all architectures, for all users, and for all known purposes. This is not Debian: The Server Operating System. And of course, don't forget that there can always exist bugs that will cause the KDE instances of all of the users at this example organization. If the users at the organization happen to use the same application software for the same purposes, or are working on similar projects, then the mission critical problems that occur for one individual user would repeatedly occur for all users, and would impede or make impossible the successful completion of whatever projects that organization is working on. - Chris Hagar Chris Hagar
