Marcus Meissner wrote: > On Sun, Nov 18, 2007 at 05:11:17PM +0100, Eberhard Roloff wrote: >> Richard Creighton wrote: >> >>>> >>> It's about time that the updater program and more generally Yast >>> installer provide the OPTION to backup any files it deletes to either >>> the trashcan or to a special directory for the purpose of providing the >>> ability to recover from the increasing number of bad updates, kernels >>> and other software that is currently just deleting what is often >>> perfectly good (read operating) software and replacing it with a 'fix' >>> that too often really 'fixes' things, to the point of being unable to >>> run. >>> >>> Kernel updates or other critical software like Yast modules, often well >>> intentioned updates will have unintended and sometimes fatal >>> consequences and it leaves you with no alternatives but to reinstall >>> from who knows where. >> Richard, >> >> I cannot agree more. >> >> Imho your suggestion to have a backup way of installing updates, is one >> step. >> The other essential thing I see necessary is quality control BEFORE an >> update is released to the public. > > The QA for box updates QA is limited. > > We however test them internally from our staging server. > > The problem is that this update was checked in and immediately released > afterwards, which should not have happened. > > If some days / the weekend had been inbetween checkin and release > (as is usual), our internal updates would have caught this and not the > general public. > > We have btw now publictesting update branches prepared for external > update testing too, but currently these are not staged yet to the outside. > > Ciao, Marcus > Thanks much Marcus. I appreciate that things are improving and, again, I understand that QA for box updates needs to be limited in comparison to QA for "paid support" products.
Thanks again and kind regards Eberhard -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
