On Wed, Sep 30, 2009 at 4:15 PM, Tom Horsley <[email protected]> wrote: > On Wed, 30 Sep 2009 15:51:52 +0200 > Michael Schwendt wrote: > >> Skipping the updates-testing repo and pushing updates directly into the >> updates repo is frowned upon. > > I still can't understand why the repo update process isn't automated > at least to the extent of testing updates on a virtual machine > which has all optional packages installed to see if the updates > install correctly and the system still boots after the updates. > > If it makes it through that elementary test, then go ahead and make > the repo public. A test run like that would be quick and easy and > catch somewhere around 99% of the problems like this that keep > sneaking into the updates.
There are some smart engineers in Fedora and Red Hat camps, it is not a easy nut to crack, but it they had enough encouragement and time they would make a solution. I hope they do. Cheers! -- pratite me na twitteru - www.twitter.com/valentt http://kernelreloaded.blog385.com/ linux, blog, anime, spirituality, windsurf, wireless registered as user #367004 with the Linux Counter, http://counter.li.org. ICQ: 2125241, Skype: valent.turkovic, msn: [email protected] -- fedora-list mailing list [email protected] To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
