Sid Boyce schreef:
My changes are not as drastic as they once were, then I kept a local log of all changes as typically a problem will surface may be a week or two after a change is made. The large IT mainframe shops going way back all have had a Change Control department that documented all proposed and actual changes which were thoroughly discussed in minute detail for possible impact. As a vendor, we were also subjected to the same process and I have had to travel up to 175 miles to explain and discuss any changes we proposed. We found however that the typical Solaris shops were not too good at it and on one occasion a programmer made a change over a weekend and on Monday the system croaked, but it was not until the Tuesday when he came back to work that they discovered the change had been made, he backed it out and the system came up. To demonstrate the thinking, the same customer attended their first Amdahl Share meeting in Copenhagen and on their return they were making fun of how paranoid mainframe customers were. Perhaps the culture has changed as many mainframe shops are now heavily into "Open" systems and staff migrate across the cultures. Regards Sid.
Maybe they misunderstood the responsibility that came with it, and confused it with paranoia...;) Nowadays there seem to be too much agendas. Too many things changing at the same time, will make control on the consequenses more difficult, as you discribe out of reality here. The timeframe and order to change fundamental stuf, is important, to keep grip on the situation. I understand deadlines, but i also understand reality, and haste does not fit in there... What i am trying to say is that time to achieve 'real' changes, may spread 3 GM versions. When major changes might jepperdize a version, try to spread them over 3. There is no need to rush, because others do. Keep sanity. to create a thrustworthy distribution. New, but stable. Like we ourselves want to have it, and not how someone thinks, unexisting, might be newbies, might want to have it, if they would choose... A good distro is. (To Be, or Not To Be.) What does not function, has to be fixed or replaced. What is it we do not like about openSuSE now, that has to change?, exept what doesn't work? -- Enjoy your time around, Oddball (Now or never...) Besturingssysteem: Linux 2.6.25-rc5-git2-5-default x86_64 Current user: oddball@AMD64x2-sfn1 System: openSUSE 11.0 (x86_64) Alpha3 KDE: 4.00.66 (KDE 4.0.66 >= 20080313) "release 6.1" --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org